Parallels worked with Microsoft to bring Windows 10 to the new Apple M1 Macbooks

[Karlston]

Parallels worked with Microsoft to bring Windows 10 to the new Apple M1 Macbooks

 

 

We already know Windows 10 on ARM runs well on the Apple M1, but that is using a hacked virtual machine. Recently however Windows emulation company Parallels have started beta testing Parallels Desktop for Mac with Apple M1 chip.

 

The currently available versions of Parallels Desktop for Mac cannot run virtual machines on Mac with the M1 chip. The new version of Parallels Desktop for Mac that can run on Mac with the M1 chip is however already in active development.

 

Parallels say they switched Parallels Desktop to universal binary and optimized its virtualization code.  The big stumbling block, however, was that Microsoft did not release a boxed version of Windows 10 on ARM, which is normally only release tied to specific hardware.

 

The good news appears to be that Microsoft did offer a version to Parallels, according to a tweet by Omar Shahine, Vice President of OneDrive.

 

 

The software should eventually be delivered to those with a subscription of Parallels Desktop. Those interested in trying out the Technical Preview early can sign up at Parallels here.

 

 

Parallels worked with Microsoft to bring Windows 10 to the new Apple M1 Macbooks

[jamesDDI]

But what in future to use a standard windows 10 on parallels on m1? It will be possible?

On windows 10 arm is possible to use x86/64 software?

 

I always used windows on parallels to use some x86 software, not arm software. So what's the purpose to use windows 10 arm in parallels if i can not use standard windows software?

[zanderthunder]

If they want to release a specialized Windows 10 ARM for Parallels, I hope they can tackle current issues on that OS.
 

Spoiler

Before getting to that, let’s review what I see as the three key problems with WOA, two of which are fatal. Listened in reverse order of importance, they are:

 

Driver compatibility. WOA-based PCs cannot take advantage of any x86/x64-based drivers, like those that hardware makers ship with scanners, printers, mice, keyboards, and so on. I describe this as the least problematic WOA problem because the platform does come with what Microsoft calls class drivers, so most peripherals will still work. They just won’t give you any of the custom capabilities that the manufacturer might provide. So for some, this could be hugely problematic. But for most people, it’s probably not a huge issue.

 

Performance. WOA systems have struggled since the beginning, and after what I’ll call 3.5 generations of Qualcomm chipsets, performance has definitely improved, just not enough: Even the most modern WOA-based PCs, like the Flex 5G, are sluggish. The good news? This is a solvable problem, and while I can’t accurately predict when some combination of hardware and software improvements finally puts WOA over the top, at least for mainstream users, that will definitely happen. Hopefully sooner rather than later.

 

Application compatibility. This is WOA’s Achilles Heel. When this platform first launched, WOA could run 32-bit x86 applications in emulation, but very slowly, and ARM32 applications natively, though there were none to few available. Over time, Microsoft added 64-bit ARM64 support to the platform, and this year it finally admitted that it was working to add 64-bit x64 emulation to WOA. That’s what we’re looking at today: The ability of this ARM-based platform to install and run 64-bit Intel-type applications.

Source: https://www.thurrott.com/windows/windows-10/244997/hands-on-with-windows-10-on-arm-x64-emulation