Full Windows 10 on ARM 64bit 10nm Qualcomm Snapdragon 835

Posted by juliusaugustus – June 2, 2017

Qualcomm demonstrates a full version of Windows 10 running every x86 application through emulation technology that Microsoft and Qualcomm have worked on very hardly to hopefully be able to show good performance running any x86 Windows app on ARM, as the Snapdragon 835 is the fastest ARM processor in the world, at least the fastest ever from Qualcomm. The marketing angle will also position every ARM Powered Windows 10 Laptop as being with built-in Gigabit LTE through an eSIM meaning you will be able to click and subscribe to any Data plan or with your telco agreeing add your Laptop simply to your existing LTE Smartphone package. Consumers will be able to expect amazingly fast LTE connectivity, very long battery life, always connected always standby functionality (checking emails etc in the background even while the Laptop is closed), compatibility with all x86 Windows apps (win32), it will be interesting to see if apps like GIMP, Adobe Photoshop, Sony Vegas, Adobe Premiere and other more demanding x86 Windows .exe apps if they can install and run with decent enough performance through this emulator. It will be interesting to see if Microsoft and Qualcomm are able to utilise all the hardware acceleration such as the GPU and all 8 cores of the Snapdragon 835 big.LITTLE "Built on Cortex Technology" platform to speed up the performance even of advanced apps and games to somehow magically perform well through the emulator. Possibly that Qualcomm even designed a specific area on the Snapdragon 835 SoC that is specifically designed to further accelerate the x86 Windows app emulation functionality? Windows 10 on ARM devices will hopefully start shipping at prices around $600-700 in extremely thin and light form factories to be made by Lenovo, HP and Asus and hopefully released worldwide before the end of the year.

  • Travis Siegel

    MS already has a version of windows that runs on arm (windows IOT). It wouldn’t be difficult for them to finish the job, and make windows run natively on arm, then provide arm as one of the executable types in it’s universal apps (much like apple with ppc, intel32, intel64, and so on). Eventually, most developers would provide arm versions of their programs because of demand. I see no reason to waste cpu cycles emulating something that is already (mostly) ported to native code version. This is a step in the wrong direction in my opinion.

  • davidlt

    They did what you explained. UWP applications now container target for multiple architectures (x86, x86_64, aarch64 (aka arm64). Supporting legacy applications are also required for many years until majority applications are built for multiple architectures. Note, that pure .NET based application had no troubles running even on Surface RT.

    Remember that first time you launch application it will be translated from x86 (and later x86_64) to aarch64 and result will be saved to the disk. Next time you are running the native code without emulating anything. They did also other things to make x86 on aarch64 run fast.

    E.g., Microsoft Office will be native once launched.