The sad demise of the Windows Phone now official.
Of course we’ll continue to support the platform.. bug fixes, security updates, etc. But building new features/hw aren’t the focus. 😟 https://t.co/0CH9TZdIFu
— Joe Belfiore (@joebelfiore) October 8, 2017
During the weekend, Microsoft’s Joe Belfiore tweeted confirmation of something that has been suspected for many months: Microsoft is no longer developing new features or new hardware for Windows Mobile. Existing supported phones will receive bug fixes and security updates, but the platform is essentially now in maintenance mode.
Microsoft’s difficulties in the mobile market are no secret, but for a time the company looked as if it was keeping Windows Mobile as a going concern regardless. Through 2016, Microsoft produced new builds for the Windows Insider program and added new features to Windows Mobile. At around the time of release of the Windows 10 Creators Update in April this year, that development largely ground to a halt. Windows Mobile, which already lacked certain features that were delivered to Windows on the PC, had its development forked. PC Windows development continued on the “Redstone 3” branch (which will culminate in the release of the Fall Creators Update later this month); Windows Mobile languished on a branch named “feature2.”
But in spite of this, until Belfiore’s tweets at the weekend, Microsoft never actually said what its plans for Windows Mobile were or how it would be developed going forward.
We have tried VERY HARD to incent app devs. Paid money.. wrote apps 4 them.. but volume of users is too low for most companies to invest. ☹️ https://t.co/ePsySxR3LB
— Joe Belfiore (@joebelfiore) October 8, 2017
Answering another question on Twitter, Belfiore explained that Microsoft never got over the app incentive hurdle, with a user volume too low to justify the investment from app developers. In late 2017, with the platform all but extinct, that’s not tremendously surprising. Over the last year, sales of Windows Mobile devices collapsed. Two to three years ago, annual sales of Windows Phones numbered in the tens of millions; now, they’re close to zero.
For fans of the platform—and I’m one—the statement… the admission… is just confirmation of what we’ve long suspected but hoped to avoid. The Windows Phone design, with its bold Live Tiles, white-on-black theme, and crisp design, is still the mobile platform that I find most pleasant to use. It’s clean and attractive and thoughtful in a way that the competition just isn’t. We wanted it to succeed because we liked the product.
An inauspicious start
What makes Microsoft’s position particularly disappointing, at least for this writer, is a continued sense that it didn’t have to be this way. In developing Windows Phone and Windows Mobile, Microsoft made a number of fumbles.
The company was too slow to grasp the importance of capacitive screens and finger-first user interfaces. Instead of seeing the iPhone and immediately starting development on Windows Phone, the company first tried to graft some basic finger-friendly interface features to the (old) Windows Mobile—an operating system that remained fundamentally stylus-oriented—with miniature replicas of mouse interfaces.
When Windows Phone 7 hit the market in 2010, it was clear that Redmond did, in fact, know how to put together a high-quality, finger-based user interface and build an operating system around that interface. This initial release held promise, but it was feature poor—it didn’t even have copy and paste at first, in a strange mirroring of the iPhone’s early feature deficits—and perhaps more fundamentally, Microsoft was sticking to its traditional business model of charging hardware companies for software licenses.
On one level, this decision was understandable, because it’s a model that had proven hugely successful for Windows and modestly successful for Windows Mobile in the pre-iPhone era. But on another level, it was clearly a mistake: the head-to-head competition in this market wasn’t iOS (because Apple doesn’t license iOS to third parties) but Google’s Android. And while there were (and are) licensing complexities around the Google Apps and Google Play Store, the core Android operating system was and is zero cost for hardware companies. Anyone can throw some parts into a phone-shaped box and slap Android onto it without paying Google a penny.
Microsoft then subjected users of this nascent platform to a painful transition. Windows Phone 7 was derived from the old Windows Mobile software. Windows Phone 8, released in late 2012, was not; it was a sibling to the desktop Windows operating system using the Windows NT kernel. Strategically, this was the right thing to do. Microsoft unified its Windows development using a common operating system kernel and, increasingly, developer APIs across phones, tablets, laptops, desktop PCs, servers, and even the Xbox and HoloLens.
But the move was not without pain. Windows Phone 7 devices couldn’t be upgraded to Windows Phone 8, leaving early adopters with phones that were prematurely end-of-lifed and a bad taste in their mouths. Moreover, the mere work of moving to the common kernel and APIs was such a huge undertaking that it didn’t give Microsoft much time to actually work on features and capabilities. Windows Phone 7 had a feature deficit relative to Android and iOS, and Windows Phone 8, rather than closing this feature deficit, was instead focused on updating and replacing the operating system’s core.
A company that had more immediately recognized both the threat and the opportunity the iPhone represented, as well as the business transformation that Android made inevitable, might well have avoided these problems. Quicker adoption of true touch interfaces, a decision to use a common NT kernel platform from the outset, a move to a store-based revenue model rather than operating system licensing; in hindsight, Microsoft could have made better decisions and made them sooner. Doing so might well have made Windows Phone a more successful platform.
Green shoots of success
In spite of all of this, there was some cause for optimism. The first generation of Windows Phone 8 handsets from Nokia were well received. Nokia had a good selection of phones from the flagship Lumia 920 down to the cheap and cheerful Lumia 520. Strong cameras became something of a Lumia trademark, and Windows Phone-specific design elements—such as a dedicated camera button with half-press autofocus—provided thoughtful differentiation. The enormous Windows Phone 8.1 update added a range of useful features, including a best-in-class swipe-based keyboard.
As much as the platform had struggled since its 2010 launch, the wave of 2012 and 2013 hardware and software releases appeared to put it on a surer footing. At the low end, devices like the Lumia 520 offered a true smartphone experience that Android struggled to match. Comparably priced Android hardware wasn’t as good: the software felt slower; the hardware felt less carefully constructed. And at the high end, the attractive software and high-end cameras were enough to pique interest. Per Kantar Worldpanel, Windows Phone hit a 12-percent market share in the UK in August 2013; 12.9 percent in France in November 2013; 17.1 percent in Italy in December 2013; 10.5 percent in Germany even as late as August 2015. The domestic story was never as good; Windows Phone barely cracked 5 percent in the US, which for an American company was always awkward.
These numbers still left Windows Phone in third place (or, occasionally, second place in markets with particularly weak iPhone penetration). But the trajectory was upwards, with a platform and product mix that was suitable for a wide range of audiences. In September 2013, Microsoft announced plans to buy Nokia’s phone business in a deal that cost $7.1 billion and wouldn’t close until April 2014. The future felt promising: keep the same product mix, keep making the platform better, and Windows Phone looked well positioned to, at the very least, stake out a solid third place and perhaps make a challenge for second place.
Stumble after stumble
But then things faltered. That product mix fell apart. Instead of annual updates to its phones offering incremental improvement—the model proven by, among others, Apple and Samsung—Nokia’s replacements for the Lumia 520 were worse in virtually every regard, and its high-end successor never even made it to market at all. Nokia’s product pipeline was deeply flawed, and the momentum of 2012 and 2013 was squandered.
Compounding this, Microsoft was making a second platform transition. Windows Phone 8 moved to the NT kernel and some shared APIs between phone and desktop; Windows Mobile 10 greatly increased the compatibility between phone and desktop, with Microsoft’s Universal Windows Platform (UWP) representing a common set of APIs for application that spanned both form factors. As before, this was a strategically important move to make, but, as before, it came at a high price: many Windows Phone 8 devices did not receive an official upgrade to Windows Mobile 10, and Windows Mobile 10 did relatively little to improve the actual end-user appeal of the operating system. Instead of a series of Windows Phone 8.1 and 8.2 updates to strengthen gaps and build a better platform for end-users, there was a period of stagnation.
Indeed, some aspects, such as the swipe keyboard, were widely regarded as being worse in Mobile 10 than in Phone 8. Windows Mobile 10 also had strange feature regressions: it didn’t support CDMA networks, so when few flagships were finally released in late 2015, they wouldn’t work on the Verizon or Sprint networks in the US.
As if the hardware and software missteps were not enough, public displays of “no confidence” were the final nail in the coffin of the platform. In July 2015, Microsoft’s new CEO, Satya Nadella, announced that 7,800 employees, primarily from the company’s hardware division, were to be laid off, while the near-$8 billion value of the Nokia business was to be written down. Sources close to the matter tell us that these layoffs are the reason, for example, for the lack of CDMA support in Windows Mobile 10: the people with the relevant technical expertise were simply let go.
We’ve also heard of consequences beyond that; people within the company have told us that Microsoft’s tardiness at updating the Surface Pro, for example, was fallout of these hardware layoffs. Microsoft didn’t (and perhaps still doesn’t) have enough personnel to develop the Xbox One S, Xbox One X, and Surface Studio and revise the Surface Pro and Surface Book at the same time.
In its stronger markets, Windows Phone just about held steady over 2014 before declining sharply in 2015 and 2016. The lack of desirable hardware, the lack of progress in the software, and the lack of management support meant that, instead of building on the successes of 2012 and 2013, Windows on phones was allowed to die.
We’ve heard from people within the company that a choice had to be made; developing a decent hardware pipeline would have required further investment in the Nokia phone business, perhaps of the order of a billion dollars. The alternative was to not make that investment and scale things back. That’s the decision that was taken, and Belfiore’s tweets over the weekend are the ultimate consequence of that decision.
We might well wonder why Microsoft didn’t say so sooner and instead strung along not only the platform’s fans but even OEM partners; it’s hard to imagine that HP would have built its Elite x3 phone had Microsoft been clearer about mobile.
Even with this announcement, there’s still speculation that Microsoft is going to bring out a new device—something phone-like but not a phone—that’ll compete, somehow, in the mobile space. For all the rumors about a “Surface Phone,” though, it’s unclear precisely what this device would do that is meaningfully different from anything else on the market or if it will be compelling enough to reverse the company’s mobile fortunes. For now, all we can do is mourn: the best mobile platform isn’t under active development any more, and the prospects of new hardware to run it on are slim to non-existent.
As for me, I switched to an iPhone more than a year ago. Every day, I’m struck at how the main user interface is basically that of Windows 3.1’s Program Manager, and iOS 11 has been fantastically unstable for me. I don’t enjoy iOS in the way I enjoyed Windows Phone. But it’s actively developed, and third-party developers love it, and, ultimately, those factors both win out over Windows Mobile’s good looks and comfortable developer platform.
It seems that MS are jumping out of a sinking industry. Getting us users to move from one sinking ship to another and announcing it as great news. How long can Spotify exist with being over 600 million in debt and not making a profit? Just how have they survived so long?
With MS killing of its hardware side, as those in the know have just announced they expect the Surface range to die next year. Could only make people wonder, just how long has the XBox got?
Microsoft is giving every impression of a shrinking company, the average consumer may come to forget who they are. This in turn may affect enterprise customers thinking. Seeing Microsoft retreating into a virtual world where nobody cares about it.
Their competitors have streaked past them in the consumer market to be companies that everybody knows and recognises. Even those companies know that they can use their vast resources and pockets to prop up a side of the business that in turn makes their other products look good. People will become those that only use Microsoft products in the office. A competitor could see just how Microsoft has become and decide then they want that business. By then Microsoft would simply be too small to have the resources to fight back effectively.
Update: So when I wrote this I was extremely pissed off at losing such a good service that I love and use all the time. And will continue to do so until December 31st anyway. But seeing as the Spotify app for Windows Phone is so bad and its the only device I would use, I also hate paying for something so poor and buggy. Don’t you just hate it when good things come to an end.
I’ve had my ups and downs with Microsoft as a company. This has just kicked off one of those down periods. Lets hope they do something good soon to turn that around.
We highlighted Paul Vreeland’s System Rescue Toolkit a few months ago, but now he’s built a new, “lite” version that packs most of the same tools and can automatically run against and repair common Windows problems for you. If you liked the original, you’ll love this.
The beauty of the original was that it offered a number of great utilities to help you troubleshoot your system if you had PC problems, without a whole bunch of trial versions, bloated utilities, or “we found X errors now call me to fix your computer” demos. The Lite version dials some of those tools back and makes the scan and repair process automatic, so you can use the toolkit, walk away and grab a bite to eat, and, hopefully, come back to a repaired and functioning Windows system—or at least some more information about what you should do next if the toolkit couldn’t fix your problems. He notes:
The Lite version of my toolkit runs all of the autoFIX steps from “Automatic Mode” found in the full version. You do not have to be a techie to use it! No technical expertise is necessary because all the repair tasks are run automatically! These repair steps include:
- CPU/Cooling Test
- Memory Test
- Hard Drive Test
- Windows Security Centre Check
- Anti-Virus and Anti-Malware Scans
- Reset Windows Networking
- System File Checker
- Disk Cleanup and Defrag
Best of all, it’s completely free (although Paul does accept donations to maintain the project.) Hit the link below to try it out yourself.
AiO-SRT Lite | Paul Bryan Vreeland
Desktop App Converter tool (Project Centennial) is now available for download from Microsoft. This new tool allows developers to convert their desktop app to a Universal Windows Platform (UWP) app. It converts a desktop Windows installer such as MSI or exe to an AppX package that can be deployed to a Windows 10 desktop.
Some of the benefits of converting your classic desktop app.
- Your app’s installation experience is much smoother for your customers. You can deploy it to computers using sideloading (see Sideload LOB apps in Windows 10), and it leaves no trace behind after being uninstalled. Longer term, you’ll also be able to publish your app to the Windows Store.
- Because your converted app has package identity, you can call more UWP APIs, even from the full-trust partition, than you could before.
- At your own pace, you can add UWP features to your app’s package, like a XAML user-interface, live tile updates, UWP background tasks, app services, and many more. All of the functionality available to any other UWP app is available to your app.
- If you choose to move all of your app’s functionality out of the full-trust partition of the app and into the app container partition, then your app will be able to run on any Windows 10 device.
- As a UWP app, your app is able to do the things it could do as a classic desktop app. It interacts with a virtualized view of the registry and file system that’s indistinguishable from the actual registry and file system.
- Your app can participate in the Windows Store’s built-in licensing and automatic update facilities. Automatic update is a highly reliable and efficient mechanism, because only the changed parts of files are downloaded.
- Download it here from Microsoft. Read the MSDN documentation about this tool here.
Windows 10 is rolling out today in several countries across the globe in a phased roll out. If you’re one of those users who reserved it on Windows 7 or Windows 8/8.1, and don’t see the update notification, there’s a good news for you. You can manually start the download by following a few simple steps (via Windows Central). As a disclaimer, this trigger should start the update but may not.,
Before you kick off, make sure you’re ready to install the Windows 10 upgrade. You can check out our guide on how to prepare your system for Windows 10. Next, make sure your system can automatically download and install Windows Update. After you’ve enabled automatic Windows Update, open Command Prompt as an administrator and type “wuauclt.exe /updatenow”. This should start the Windows 10 download on your system.
So are you ready yet to upgrade. Personally I can’t wait but I will be cautious about upgrading my work PC. Of course that’s a company decision. But I will be upgrading the laptops at home. Just have to pry them out of the hands of the owners first.
Of course I will promise them that I won’t break it with the upgrade. Please Microsoft don’t let me down I will never hear the end of it. At least there is a rollback option but a time limit of 30 days. Why a time limit at all. Guess Microsoft doesn’t want you to go back and I’m pretty sure that I will stick with Windows 10. The preview has been very interesting and much more like the windows that people are used to but with a lot more added bells and whistles.
Should be fun trying to convince the family. But you never know they may want to upgrade anyway. Hopefully.
Trend Micro researcher Jay Yaneza says Point of Sales malware has begun using Microsoft .NET, following its release as open source last year.
Yaneza found the new so-called GamaPoS malware being distributed to US organisations including credit unions, developers, and pet care businesses through the resurgent Andromeda botnet. He says the use of .NET as a platform to build point of sales malware is unique and likely to be adopted by the criminal underground.
“GamaPoS holds the distinction of being a .NET scraper — something unseen in prior PoS threats,” Yaneza says .
“We can attribute this development to the fact that it is easier to create malware in the .NET platform and, now that Microsoft made it available as an open-source platform, more developers are expected to use it for their applications.
“This makes .NET a viable platform to use for attacks.”
Yaneza says GamaPoS uses Andromeda’s backdoors to spread in a shotgun fashion further infecting about four percent of the botnet’s existing victims.
The malware combines two malicious features including PsExec, which hackers used to help pop retailer Target last year, and the Mimikatz hack tool that is considered one of the best vacuumers of Windows credentials.
That combination grants attackers a high degree of capability to move laterally inside breached networks.
Victims are targeted using phishing scams that masquerade as would-be guidance on Payment Card Industry Data Security Standard (PCI DSS) or as information on installing Oracle’s MICROS, a popular payment operating system which it can also compromise.
GamaPoS will siphon Visa and Discover cards to its command and control servers over HTTPS.
The attack campaign organisers are thought to be also spreading the NitLovePoS payment operating system malware found in May.
“Using an old botnet as a shotgun method to cast a wide net for targets has its merits,” Yaneza says.
“Using spam and exploit kits to establish a large mass of bots enables operators to steal information from specific targets, some of which can be resold to other threat actors.”
The calls are starting to come in, as I, like you, Dear Reader, am the head of IT Support for my friends and family. You’d think my cell phone was an IT helpline, and my email is filled with Word documents with pasted in screenshots along with subject lines like “Is this safe?!?!?”
Anyway, Window 10 is coming soon, and this little icon (the Windows icon) is stating to show up in folks’ taskbars. For the techies, it’s called GWX (Get Windows 10) and it’s there to prep your machine and possible download Windows 10 if you want to reserve a spot. It’s added by KB3035583.
If you click it, you’ll get this screen where you can add your email and when July comes around your system will start downloading Windows 10 automatically.
You may also see this in Windows Update if you run Windows Update manually as I do.
You get to decide when you want to install it, it’s not automatic.
The important part you and your non-technical friend should know and explore is the “Check your PC” section. Click the “hamburger” menu in the upper left corner, then click “Check your PC.” Here’s mine. Looks like I need to update or uninstall one program that isn’t yet compatible, but my devices (video, usb stuff, etc) are cool.
There’s a great FAQ (Frequently Asked Questions) on Windows 10 here that you should check out.
Here’s my personal translation/take on the most important parts:
- Windows 10 upgrades start July 29th and you can choose to upgrade for free until July 29, 2016 so no rush. If you want wait and see, you can.
- The upgrade is free for that period (July 29th 2015 until 2016, a year later). Upgrading after July 29th, 2016 will cost something.
- You can upgrade machines running 7 and 8.1.
- You machine should have these specs, which are pretty low and reasonable. Most anyone with a running PC can upgrade.
- Yes, Solitaire and Minesweeper and Hearts will be removed BUT you can download the new versions of Solitaire and Minesweeper free in the Windows Store. They are pretty nice versions.
- You’ll move to either Windows 10 Home or Windows 10 Pro, according to this table:
- You apps will keep running. I’m running all sorts of apps, many quite old, on Windows 10 and I have had no issue. The Compatibility Wizard still exists, though, so you can “lie” to really old apps and tell them they are running on Windows 95, or whatever. Just right-click the App that isn’t working and click “Troubleshoot Compatibility,” or right-click, Properties, then Compatibility. I haven’t had to do this myself, yet, so consider this a rare thing.
So far it’s been pretty interesting and I think that if non-technical friend liked Windows 7 and tolerated Windows 8 that they will like Windows 10. I’ve been doing “Windows 10 Build to Build” upgrade videos over at my YouTube and I would love it if you’d subscribe to my YouTube as well.
It’s amazing that Windows 7 users and Windows 8 users will all be able to upgrade and come forward to a single version of Windows. As a developer (both web and apps) it’ll be nice to have people on an “evergreen” Windows where I can do things like Feature Detection and not think as much about versioning.
Windows 10 is different. While Microsoft aggressively tracked down leaked builds of Windows Vista and Windows 7, the software giant has opened its doors to let anyone test Windows 10 through a process that’s not normally public. It’s a change that has allowed everyone to judge and critique Windows 10 before it’s even ready. We’ve seen the good and the bad, and now we’re about to witness the final result on July 29th. With Microsoft now committing to a Windows 10 release in less than two months, is it really ready?
Windows 10 has progressed well over its relatively short development period. If you compare preview builds from two months ago to today, there are many changes and improvements, but still a lot of bugs. While it’s two months until release date, Microsoft will still complete a process known as release to manufacturing (RTM) later this month. Windows might be switching to a servicing model with regular updates, but there’s still a final point needed for PC makers to start loading their own images to ship devices in time for the back to school period and the holidays. That RTM phase means Microsoft only has a few weeks to get Windows 10 ready before it has to rely on patches and hotfixes that can be distributed automatically to machines once they’re upgraded.
WINDOWS 10 FEELS NEARLY FINISHED, BUT THERE’S STILL SOME GLARING BUGS
A few weeks doesn’t seem like enough time right now, especially given the current state of Windows 10. The latest build (10130) looks almost finished and polished, but then there are continued issues with the Start Menu not opening or crashing and driver problems that are slightly alarming at this stage of development. Perhaps the biggest issue I have encountered is the upgrade process between builds. Microsoft has been testing this vigorously, as it’s a key part of getting Windows 7 and Windows 8 users to Windows 10 for free. If an upgrade fails then it’s one less machine running the latest operating system. I’ve had a variety of upgrade failures, even with the recent builds that Microsoft has distributed. Please note this is the author’s experience. I haven’t had a problem with any update upto and including 10130. (BJ)
These could all be fairly minor bugs, but they’ve been consistent and present throughout the Windows 10 development period, which suggests there have been some issues that have prevented Microsoft addressing them fully. Fortunately, Microsoft is now in a period of code completion. Additions to the core of Windows 10 will be locked soon, and Microsoft is now focused on improving the built-in apps and crushing bugs. Like any version of Windows, Microsoft has a number of tests and processes to check off before it declares Windows 10 is ready. The overall bug count will have to drop, and the company will decide which bugs can wait for launch day patches and prioritize accordingly.
Windows 10 will of course be ready for July 29th, but how complete and stable it will be could vary depending on your hardware and usage. I have some machines that work well, and others that are crashing or the display drivers and audio drivers don’t work correctly. At this stage I would like to be using a release candidate on my machines that feels like the final version of Windows 10, but we’re not quite there yet. Microsoft will start preloading the final bits on PCs that have opted in for the Windows 10 upgrade, with patches and updates to follow once it launches on July 29th.
WINDOWS 10 IS GOING TO HAVE A BUNCH OF UPDATES ON DAY ONE
Windows 8 launched with a number of day one patches, and I expect Windows 10 will have plenty. Microsoft has been regularly patching Windows 10 preview builds to address bigger problems, and receive additional feedback to help shape changes. The dedicated feedback app will ship with the final version of Windows 10 so that Microsoft can continue to receive input from users. It’s really Microsoft’s method of using the general public for its own testing. With recent headcount reductions on the testing teams for Windows, public feedback and beta testing has helped Microsoft change the way it’s building Windows.
Microsoft is very close to getting Windows 10 ready, but the Windows team has a lot of sleepless nights ahead throughout June and July to ensure the quality is high across the vast amount of PCs out there. Microsoft can’t afford to make any bad impressions with Windows 10 after the mixed reception to both Vista and Windows 8. Providing the driver issues are cleared up, the company can easily avoid the problems associated with the early days of Windows Vista. Windows 10 is really shaping up to be the next great successor to Windows 7 and Windows XP, and Microsoft wants to ensure everyone upgrades. Windows 10 will never really be ready thanks to continuous new features and updates coming for the rest of the year and beyond. The road could be a little bumpy to start, but it’ll only get smoother and smoother over time.
Source: Is Windows 10 ready? | The Verge