Today at Microsoft’s WinHEC event in Shenzhen, China, the company announced that it’s working with Qualcomm to bring the full Windows 10 experience to future devices powered by Snapdragon processors. Terry Myerson, executive vice president of the Windows and Devices Group at Microsoft, is “excited to bring Windows 10 to the ARM ecosystem” and looks forward to bringing “Windows 10 to life with a range of thin, light, power-efficient and always-connected devices,” which may include anything from smartphones to tablets to ultraportable laptops to servers. These new Snapdragon-powered devices should support all things Microsoft, including Microsoft Office, Windows Hello, Windows Pen, and the Edge browser, alongside third-party Universal Windows Platform (UWP) apps and, most interestingly, x86 (32-bit) Win32 apps. They should even be able to play Crysis 2.

This announcement fits nicely with Microsoft’s “Windows Everywhere” doctrine and should come as no surprise. It’s not even the first time we’ve seen Windows running on ARM processors. Microsoft’s failed Windows RT operating system was a modified version of Windows 8 that targeted the ARMv7-A 32-bit architecture. It grew from Microsoft’s MinWin effort to make Windows more modular by reorganizing the operating system and cleaning up API dependencies.

This work first surfaced in Windows Server 2008, which could be installed with a stripped-down, command-line only interface that did not include components such as Internet Explorer that were not necessary for specific server roles. Windows RT also leveraged the newer Windows Runtime (WinRT) API that offered several new features such as digitally signed app packages distributed through the centralized Windows Store and the ability to run apps within a sandbox. It also made it easier for software developers to target multiple CPU architectures. However, Microsoft’s rework of Windows was not yet complete, leaving Windows RT with a bunch of legacy Win32 code that went unused. It also could not run Win32 desktop apps, severely limiting the number of available apps to only those using WinRT and distributed through the Windows Store.

MinWin and its derivatives have continued to evolve over the past few years after getting a major boost in 2013 when Microsoft reorganized its disparate software platforms into the singular Operating Systems Engineering Group. The end result is Windows 10, a modular OS that can run on anything from low-powered IoT devices to high-performing workstations and servers. Its foundation is OneCore, MinWin’s direct descendant, that includes only the operating system kernel and components essential for any hardware platform. OneCore UAP (Universal App Platform) is another major module for Windows 10 whose groundwork was laid during the creation of Windows Phone and Windows RT. It provides support for Universal Windows Apps and Drivers, along with more advanced features such as the Edge browser and DirectX. On top of these modules, Microsoft can add modules that target specific device families (desktop, mobile, Xbox, HoloLens, etc.) that provide specialized features and shells.

Also included in OneCore UAP is Universal Windows Platform (UWP). An extension of the WinRT API used in Windows 8, it allows developers to create universal apps that are CPU architecture agnostic and can run on multiple devices, seamlessly adapting their user interface and input methods to the hardware they’re running on. With UWP, the architecutre independence is achieved by having pre-compiled versions for each platform available from the Store, which will then download and install the correct version for the individual device. The major change with today's announcement over Windows RT and UWP is that x86 apps will be able to run on Qualcomm's ARM-based SoCs, along with support for all of the peripherals that are already supported with Windows 10. This alone is a huge change from Windows RT, which would only work with a small subset of peripherals.

Microsoft is also focusing on having these devices always connected through cellular, which is something that is not available for many PCs at the moment. Support will be available for eSIM to avoid having to find room in a cramped design to accomodate a physical SIM, and Microsoft is going so far as to call these "cellular PCs" meaning they are expecting broad support for this class of computer, rather than the handful available now with cellular connectivity.

The ability to run x86 Win32 apps on ARM will come through emulation, and to demonstrate the performance Microsoft has released a video of an ARM PC running Photoshop.

This of course raises several questions, few-if-any of which Microsoft is willing to answer. Intel has long exerted strong control over the x86 ISA, limiting or outright preventing competitors like NVIDIA from implementing x86 support. So how Microsoft and Qualcomm are able to (for lack of a better way to put it) get away with this is a big question. Certainly there's no indication right now that this has Intel's formal blessing.

The key points here are that this is a form of software emulation - Microsoft even calls it as much - and that only 32-bit x86 support is being offered. On the former, this means that there's no hardware execution of x86 instructions taking place - though Microsoft and Qualcomm are certainly lining up instructions as best they can - which avoids many of the obvious patent pitfalls of doing x86 in hardware, and puts it in the same category as other x86 emulation mechanisms like DOSBox and QEMU. Meanwhile only supporting 32-bit x86 code further rolls back the clock, as the most important of those instructions are by now quite old, x86 having made the jump to 64-bit x86-64 back in 2003. So it may very well be that it's easier to avoid any potential legal issues by sticking with 32-bit code, though that's supposition on our part. In any case it will be interesting to see what instructions Microsoft's emulator supports, and whether newer instructions and instruction set extensions (e.g SSE2) are supported in some fashion.

Of course, the performance of this solution remains to be seen. x86 is not easy or cheap to emulate, and an "emulator" as opposed to a Denver-like instruction translation makes that all the harder. On the other hand, while maximizing x86 compatibility is great for Microsoft and Qualcomm, what they really need x86 for is legacy applications, which broadly speaking aren't performance-critical. So while x86 on a phone/tablet ARM SoC may not be fast, it need only be "good enough."

In any case, Windows 10’s ability to scale and adapt to essentially any hardware platform is a remarkable feat of engineering, and it’s what makes today’s joint announcement with Qualcomm possible. The first devices with Snapdragon SoCs running the full Windows 10 experience should be available in the second half of 2017.

It will be interesting to see what shape these devices take and which companies produce them. Some new lower-cost, full-featured Windows 10 tablets would be a welcome addition, and Qualcomm has its eyes on the low-powered server market too with its Centriq product family. A Windows 10 smartphone with a Snapdragon SoC is also likely, but with Windows Phone 8 holding less than 1% global market share, according to Gartner, Microsoft is essentially starting from scratch. Will the benefits of universal apps be enough to lure software developers and users of other Windows products away from Android and iOS? Can Windows 10 reestablish Microsoft as a major player in the smartphone market, or is the hole it has dug over the past decade too deep?

POST A COMMENT

121 Comments

View All Comments

  • mxnerd - Wednesday, December 07, 2016 - link

    Very good news. Just wondering how good can Win32/Win64 apps actually run on ARM platforms? Reply
  • boskone - Wednesday, December 07, 2016 - link

    I don't believe it supports 64-bit x86 emulation, just 32-bit. I think most Windows software (including games) is still 32-bit, though, so that shouldn't be a huge issue (assuming the emulation runs tolerably in the first place). Reply
  • BillyONeal - Thursday, December 08, 2016 - link

    Based on.... ? Wouldn't amd64 be easier to implement on aarch64 since the bitnesses match? Reply
  • basroil - Thursday, December 08, 2016 - link

    "Based on.... ? Wouldn't amd64 be easier to implement on aarch64 since the bitnesses match?"

    Actually it's far more difficult since you would need to add in BOTH 64 and 32bit instruction emulation rather than just 32bit. ARM doesn't play nicely with mixed bit situations
    Reply
  • BillyONeal - Thursday, December 08, 2016 - link

    >you would need to add in BOTH 64 and 32bit instruction emulation

    Why would you have to do that? Windows does not allow 32 bit code in a 64 bit process or vice versa. They would need only to implement support for long mode.
    Reply
  • kuttan - Thursday, December 08, 2016 - link

    ARM64 is not much different to AMD64 regarding the implementation of 64 bit support. Both architecture supports 64 bit as an extension to 32 bit support. Reply
  • Senti - Thursday, December 08, 2016 - link

    > Windows does not allow 32 bit code in a 64 bit process or vice versa.
    It's completely false. Actually there are only 64 bit processes on 64 bit Windows and all of them have 64 bit ntdll.dll. "32 bit" processes then load WOW subsystem that creates appropriate 32 bit environment and translation layers. So you can use 64 bit code in "32 bit" processes if you know what you are doing.
    Reply
  • Samus - Thursday, December 08, 2016 - link

    I suspect the obvious reason for sticking with 32-bit x86 over x86-64 is for legacy 16-bit execution compatibility. As the article emphasized, this move is a purely legacy-focused one where performance is not the key metric, compatibility is. 64-bit windows environments can not run 16-bit code, and presumably emulated 64-bit windows environments have the same restriction.

    This is actually the ONLY reason why Microsoft still even has a 32-bit SKU. Virtually every 32-bit program and piece of hardware from the last decade supports x86-64 windows environments, but 16-bit programs that were still being written as late as 2010, do not.
    Reply
  • inighthawki - Friday, December 09, 2016 - link

    Or, far more likely - time. It takes time to implement a feature like this, and x64 adds a lot to the ISA. Given that 95% of applications (and 99.99% of legacy business applications) are still 32-bit or have 32-bit versions, they probably decided to start with that. I'd bet good money that x64 support will come some time after first launch. Reply
  • npz - Thursday, December 08, 2016 - link

    > The key points here are that this is a form of software emulation - Microsoft even calls it as much - and that only 32-bit x86 support is being offered. On the former, this means that there's no hardware execution of x86 instructions taking place - though Microsoft and Qualcomm are certainly lining up instructions as best they can - which avoids many of the obvious patent pitfalls of doing x86 in hardware

    -- There you go.
    Reply

Log in

Don't have an account? Sign up now