Windows 11 on Snapdragon: What Still Doesn’t Run Under Emulation?
Windows 11 on Snapdragon is no longer the compatibility gamble it once was.
Modern Windows-on-Arm PCs can run:
native Arm64 applications
32-bit x86 applications
64-bit x64 applications
and Windows 11 24H2 introduced Microsoft’s Prism emulation engine to improve the performance and efficiency of x86/x64 software running on Arm processors.
By 2026, many mainstream applications also have native Arm64 versions, including Microsoft 365 applications, Teams, Chrome, Zoom, Spotify, WhatsApp, Blender, Affinity and DaVinci Resolve.
So the old question:
“Will normal Windows software run?”
has largely become:
“Does this particular application depend on something Prism cannot emulate?”
That distinction matters before deploying Snapdragon PCs into a business.
What Prism Actually Does
Prism translates x86 and x64 application instructions so they can run on an Arm64 processor.
This happens automatically.
You do not normally need to:
install an emulator
configure compatibility software
choose an Arm mode
Microsoft says Windows 11 on Arm transparently supports both x86 and x64 user-mode applications under emulation.
For ordinary applications, that means an old x64 .exe may simply install and run.
That is why many users can move to a Snapdragon laptop and continue using legacy Windows software without even knowing which applications are native Arm64 and which are being translated.
Prism Has Improved Significantly
One historical limitation was software that expected modern x86 CPU instruction sets such as AVX.
That has changed.
Microsoft expanded Prism support to include:
AVX
AVX2
BMI
FMA
F16C
and other commonly expected x86 extensions. Microsoft says this has materially expanded compatibility for modern games and other x64 applications.
That removes a category of compatibility problems that affected some earlier Windows-on-Arm systems.
So an older article that implies:
“Applications requiring AVX will not run on Snapdragon”
would now be outdated.
The Big Limitation: Drivers Are Not Emulated
This remains the most important Windows-on-Arm limitation.
Prism emulates user-mode application code.
It does not emulate Windows drivers.
Microsoft is explicit:
> Kernel-mode components must be compiled for Arm64.
That means an application may look like an ordinary x64 program but still fail because it depends on an x64-only driver.
This is the question I would ask before buying an Arm laptop for specialist business use:
Does the application install a driver?
If yes, check for official Windows-on-Arm support.
What Kind of Software Depends on Drivers?
More than people realise.
Examples can include:
VPN software
endpoint security
specialist USB hardware
print/PDF software
virtualisation tools
hardware licensing dongles
industrial equipment
assistive technology
specialist scanners
low-level monitoring software
Microsoft specifically identifies antivirus, printing/PDF software, assistive technologies, CD/DVD utilities and virtualisation software as categories where driver compatibility can matter.
So:
Application runs under x64 emulation
does not guarantee:
every feature of the application works.
If one feature depends on a kernel driver, that part needs native Arm64 support.
Printers: Usually Fine, but Check Older Models
Printer compatibility is much better than many people expect.
Microsoft says Windows 11 Arm PCs support most printers, including models using the Mopria printing standard.
The problem tends to be older or specialised printers whose manufacturer installer depends on an x64 driver package.
Microsoft even recommends adding printers through:
Settings > Bluetooth & devices > Printers & scanners
rather than relying on an old manufacturer installer if the installer itself is incompatible.
Before deploying Snapdragon PCs into an office with:
label printers
receipt printers
plotters
specialist multifunction devices
check the exact model.
“HP printer” is not specific enough.
Scanners and Specialist USB Devices Need More Caution
This is where I would be more conservative.
A standard mouse, keyboard, webcam or USB storage device will usually use drivers already present in Windows.
A specialist device may require its own vendor driver.
Examples include:
document scanners
laboratory equipment
CNC interfaces
measurement devices
programming tools
legacy serial/USB adapters
If the vendor only publishes an x64 driver, Prism cannot rescue it.
The hardware may simply not work.
Gaming Has Improved — but Is Still Not Universal
Gaming compatibility has improved substantially.
Microsoft reported in late 2025 that Prism’s AVX/AVX2 support expanded compatibility with modern games, while anti-cheat vendors including Easy Anti-Cheat, BattlEye, Denuvo and XIGNCODE3 had added Windows-on-Arm support in various contexts.
Microsoft also brought the Xbox app to Arm-based Windows 11 PCs in January 2026.
That means it is no longer accurate to say:
“Anti-cheat games generally don’t work on Arm.”
But Microsoft still warns that certain games can fail where their particular anti-cheat or other required driver has not been updated for Arm64.
So check the exact game.
Do not assume:
Steam runs = every Steam game runs.
The launcher and the game are separate compatibility questions.
Antivirus and Endpoint Security
Some third-party antivirus products still cannot install unless their required components and drivers support Arm64.
Microsoft explicitly lists this as a Windows-on-Arm limitation.
For a business, this is more important than whether one old desktop application runs.
Before deploying Arm PCs, verify your:
EDR
antivirus
device-control software
web-filtering agent
vulnerability scanner
RMM software
supports Windows on Arm.
If your MSP or security platform depends on an x64-only kernel driver, that can block deployment entirely.
VPN Software
VPN clients deserve the same check.
A VPN application may have a normal x64 interface that Prism could run perfectly well.
But the actual tunnel may depend on:
network filter driver
virtual network adapter
low-level security component
Those need Arm64 support.
Do not test only whether:
the VPN application opens.
Test whether it:
connects
routes correctly
resolves internal DNS
survives sleep/wake
works with Conditional Access
supports your security stack
Virtualisation Is Still a Specialist Area
Virtualisation is another area where architecture matters.
Microsoft says kernel drivers must be native Arm64 and specifically identifies virtualisation as one of the areas affected by that limitation.
An Arm Windows host also cannot simply boot an ordinary x64 Windows ISO in Hyper-V as though it were an Intel/AMD computer.
For native virtualisation, guest architecture matters.
That makes Arm PCs less suitable for some IT professionals who routinely run:
old x64 Windows VMs
legacy server labs
specialist hypervisors
unusual kernel-debug environments
before verifying their exact tooling.
Android Development Has a Notable Limitation
Developers also need to check their toolchain.
Microsoft’s current .NET MAUI guidance says the Android Emulator still requires x64 architecture and is not supported on Windows Arm devices.
Alternatives include:
physical Android device
remote/cloud development
other supported testing workflows
So Visual Studio itself may run natively on Arm, while one component of your development workflow still does not.
This illustrates the real Windows-on-Arm problem perfectly:
the main application may be compatible while one dependency is not.
Visual Studio Is Now Native Arm
The situation for development overall is much better than it used to be.
Microsoft provides Arm-native Visual Studio and Visual Studio Code support.
So Windows-on-Arm can be an excellent development platform for:
.NET
web development
many modern application stacks
But developers using specialised:
emulators
debuggers
drivers
containers
virtual machines
should validate their full toolchain.
Windows Customisation Tools Can Still Be Problematic
Microsoft also warns that applications that deeply customise Windows may not work correctly unless they explicitly support Arm64.
Examples can include:
shell modifications
unusual input methods
accessibility software
filesystem extensions
low-level cloud-storage clients
Anything that hooks deeply into Windows deserves more scrutiny than a conventional productivity application.
Some Accessibility Software Needs Verification
Built-in Windows accessibility functionality is available, but third-party assistive technologies should be checked individually.
Microsoft says not all assistive-technology applications work as expected on Arm, although support continues to improve; for example, NVDA has now been updated for Arm compatibility.
For somebody who depends on assistive software to work, compatibility should be verified before purchasing the laptop, not afterwards.
What Usually Works Very Well?
For a typical business user running:
Microsoft 365
Outlook
Teams
OneDrive
SharePoint
Chrome/Edge
web applications
Zoom
PDF reading
mainstream printers
Windows-on-Arm is now a much easier recommendation than it was several years ago.
Microsoft provides native Arm64 versions of the core Microsoft 365 applications, and many mainstream third-party applications now have native builds as well.
That means an employee whose workload is primarily:
browser + Microsoft 365 + Teams
may barely notice they are using an Arm processor.
Native Arm64 Is Still Better Than Emulation
Prism is impressive.
But if both versions exist, choose:
Arm64 native
over:
x64 emulated
where practical.
Microsoft notes that native Arm applications normally provide the best:
performance
responsiveness
power efficiency
battery life.
That battery-efficiency advantage is one of the reasons Snapdragon laptops are attractive in the first place.
Running everything through translation unnecessarily reduces some of that benefit.
How to Tell Whether an Application Is Emulated
Open:
Task Manager
Go to:
Details
You can add the:
Architecture
column where available.
Depending on the application, you may see architectures such as:
ARM64
x64
x86
That can help when troubleshooting unexpectedly poor performance.
But do not treat emulation itself as a fault.
Many x64 applications now run extremely well through Prism.
Don't Judge Compatibility From the Installer Alone
This is particularly important for businesses.
A program may:
install successfully
and:
launch successfully
while one crucial feature does not work.
Example:
Accounting application opens.
But its:
USB smart-card reader
requires an unsupported x64 driver.
Or:
VPN client opens.
But its network driver cannot install.
Or:
CAD program launches.
But the hardware licence dongle is unavailable.
So compatibility testing must reproduce the real workflow.
The Business Deployment Checklist
Before buying Snapdragon PCs for a business, test:
1. Microsoft 365 applications.
2. Line-of-business software.
3. VPN.
4. Endpoint security/EDR.
5. RMM and remote-support agent.
6. Printers.
7. Scanners.
8. USB devices and licence dongles.
9. Browser extensions.
10. Microsoft 365 add-ins.
11. Finance/payroll applications.
12. Any virtual machines or development tools.
And don't simply ask vendors:
“Does your app run on Windows 11?”
Ask:
“Is this supported on Windows 11 Arm64/Snapdragon?”
Those are different questions.
When I Would Choose Snapdragon
Windows on Arm is particularly attractive when the user values:
long battery life
quiet operation
mobility
Microsoft 365
web applications
Teams/video calling
modern mainstream applications
For those workloads, the compatibility difference between modern Snapdragon PCs and traditional x64 PCs is now relatively small.
When I Would Still Choose Intel or AMD
I would be more cautious where the user depends on:
old hardware
specialist USB equipment
legacy printers/scanners
obscure VPN/security software
x64-only kernel drivers
intensive virtualisation
specialist development emulators
specific unsupported games
In those cases, x64 Windows remains the safer compatibility choice unless testing proves otherwise.
The Key 2026 Rule
The old rule was:
“Check whether your Windows app has an Arm version.”
The better 2026 rule is:
“Check whether the application relies on anything Prism cannot emulate.”
Normal x86/x64 application code is increasingly unlikely to be the problem.
Drivers and low-level dependencies remain the real compatibility boundary.
How Hamilton Group Can Help
Hamilton Group can help businesses decide whether Snapdragon Windows devices are suitable before deploying them across an organisation.
We can help test:
Windows 11 on Arm
Snapdragon business laptops
Microsoft 365
line-of-business applications
printer and scanner compatibility
VPN clients
endpoint security
RMM tools
legacy applications
hardware peripherals
device deployment
The best approach is not to assume Arm is incompatible—or assume Prism solves everything.
Test the actual business workflow, especially anything that installs a driver.
Visit hgmssp.com or call 0330 043 0069 to discuss Windows device selection and business IT support.