Windows 11 on Snapdragon: What Still Doesn’t Run Under Emulation

31 Jul 2026

Windows laptops powered by Qualcomm Snapdragon processors have improved considerably.

Modern Windows 11 on Arm devices can run native Arm64 applications alongside many traditional x86 and x64 Windows programs. Microsoft’s Prism emulation layer translates older application code automatically, so users can often install familiar software without thinking about processor architecture.

However, emulation is not universal.

A conventional desktop application may run perfectly, while another program refuses to install because it depends on a driver, browser extension, security filter or specialist hardware component that cannot be emulated.

That distinction matters for businesses considering Snapdragon laptops for employees.

First: What Is Windows 11 Version 26H1?

Windows 11 version 26H1 is not a normal feature update for existing PCs.

Microsoft describes it as a specialised, hardware-optimised release designed for selected new devices and next-generation processors. The first supported devices use Qualcomm Snapdragon X2 Series processors. It is supplied preinstalled on qualifying hardware and is not offered as an in-place upgrade through Windows Update.

That means:

Your current Windows 11 laptop will not suddenly receive 26H1.
You cannot normally upgrade an existing 24H2 or 25H2 device to it.
Businesses will encounter 26H1 mainly when purchasing selected new hardware.
Windows 11 versions 24H2 and 25H2 remain Microsoft’s recommended releases for broader enterprise deployment.

Version 26H1 receives monthly servicing, but it uses a different Windows core from the mainstream annual releases. Microsoft says 26H1 devices will not move directly to the annual feature update arriving in the second half of 2026; they will receive an upgrade path through a later Windows release.

What Is Windows on Arm?

Most traditional Windows PCs use processors based on the x86-64 architecture from Intel or AMD.

Snapdragon Windows computers use Arm64 processors.

Software designed specifically for Arm64 runs natively. This normally provides the best combination of:

Performance
Battery life
Responsiveness
Reliability
Hardware integration

Windows 11 can also emulate many unmodified x86 and x64 applications. Microsoft says most conventional Windows applications can run this way, while native Arm64 versions remain preferable wherever they are available.

What Is Prism?

Prism is Microsoft’s current emulation technology for Windows on Arm.

It translates x86 and x64 application instructions so that they can run on Arm64 processors. Microsoft introduced Prism to improve the speed and efficiency of emulated software, particularly on Snapdragon X-series PCs.

For many ordinary applications, this process is almost invisible.

You download the installer, run the program and continue working.

Typical productivity applications are increasingly available in native Arm64 form, including Microsoft 365 applications, Teams, OneDrive, Chrome, Zoom, Slack, Spotify and other widely used products.

The difficulties usually begin when software needs to operate below the normal application layer.

The Most Important Limitation: Drivers Are Not Emulated

Prism can translate application code.

It cannot make an Intel or AMD kernel-mode driver work on Arm.

Drivers communicate directly with Windows and hardware. They must be built specifically for Windows on Arm. When an application depends on an unsupported x86 or x64 driver, the visible program may install partially, fail during setup or open without its core functionality.

Microsoft specifically warns that hardware, game and application drivers work only when designed for Windows 11 on Arm.

This is the main reason some software still does not run.

1. Older Printers, Scanners and Specialist Peripherals

Ordinary printers that use drivers included with Windows may work without difficulty.

Problems are more likely with:

Older multifunction printers
Label printers
Receipt printers
Specialist scanners
Plotters
Card printers
Signature pads
Measurement devices
Industrial USB equipment
Proprietary docking hardware

The manufacturer’s setup application may be x64 and capable of running under emulation, but the driver it tries to install may not support Arm64.

Microsoft has acknowledged that some manufacturer printer installers do not work on Arm PCs and recommends adding the printer through Windows where possible, or following Arm-specific instructions from the manufacturer.

What to Check

Before purchasing a Snapdragon device, confirm that the hardware manufacturer provides:

An Arm64 driver
Built-in Windows support
Mopria-compatible printing where relevant
An Arm-compatible management application
Support for your exact model, not merely the manufacturer’s current range

A printer being accessible over the network does not guarantee that advanced functions such as scanning, finishing, account codes or secure print release will work.

2. Applications That Install Virtual Hardware

Some applications create virtual devices or low-level network adapters.

Examples include:

Legacy VPN clients
Virtual audio cables
Virtual webcams
Disk-mounting software
USB redirection tools
Serial-port emulators
Hardware dongle managers
Virtual network switches
Specialist remote-access software

The application interface may run under emulation, but its virtual driver may not.

Typical symptoms include:

The program installs but cannot connect.
A virtual adapter never appears.
Windows reports an incompatible driver.
The application opens but cannot detect its service.
The installer rolls back near completion.

For business VPN software, verify the complete client—not merely the login application—is supported on Windows 11 Arm64.

3. Some Antivirus and Endpoint Security Products

Security applications commonly install deep system components such as:

File-system filters
Network inspection drivers
Behaviour-monitoring services
Browser protection modules
Device-control drivers
Exploit-prevention components

These components cannot simply be translated like an ordinary desktop application.

Microsoft states that some third-party antivirus products cannot be installed unless they have been created or updated for Arm-based Windows PCs. Windows Security itself is supported.

Businesses should verify compatibility for the exact versions of their:

Endpoint detection and response platform
Managed antivirus
Web filtering agent
Data-loss prevention software
Device-control platform
Security monitoring agent

A vendor offering an Arm-compatible dashboard does not necessarily mean every protection module has reached feature parity.

4. Games Using Unsupported Anti-Cheat Drivers

Many games run successfully under Windows on Arm, but anti-cheat technology remains a frequent obstacle.

Some multiplayer games install kernel-level anti-cheat drivers. When those drivers do not support Arm64, the game may:

Refuse to launch
Display an unsupported-platform message
Close after the loading screen
Prevent online multiplayer
Run only in an offline mode

Microsoft advises checking directly with the game publisher because applications relying on incompatible anti-cheat drivers may not work.

This means a game’s processor and graphics requirements are not the complete compatibility test.

You must also check:

The launcher
Copy-protection system
Anti-cheat platform
Controller driver
Modding framework
Required graphics features

5. Older VPN and Network-Filtering Clients

VPN software is a particularly important consideration for businesses.

Many VPN products rely on:

Virtual network adapters
Packet-filtering drivers
Credential providers
Endpoint-compliance modules
Device posture checks
Browser authentication components

An emulated VPN interface cannot compensate for an unsupported network driver.

Before issuing Snapdragon devices to remote employees, test:

VPN connection establishment
DNS resolution
Split tunnelling
Device certificates
Multi-factor authentication
Network-drive access
Endpoint-compliance checks
Sleep and resume
Switching between Wi-Fi and mobile data

A newer client version may support Arm even when the version currently deployed across your organisation does not.

6. Some Virtualisation Software

Virtualisation platforms depend heavily on processor architecture and low-level system features.

An x64 virtualisation application cannot necessarily run x64 virtual machines on an Arm PC merely because its management console opens.

Potential limitations include:

Unsupported hypervisor drivers
No x64 guest execution
Limited USB redirection
Incompatible networking modules
Missing nested virtualisation
Restricted legacy virtual machines

Native Windows features and Arm-compatible virtualisation tools may work, but businesses should not assume their existing x64 virtual-machine workflow will transfer unchanged.

This is especially relevant for:

Developers
IT administrators
Cybersecurity teams
Software testers
Employees running legacy line-of-business systems
Training environments that rely on local virtual labs

Where exact x64 compatibility is essential, a conventional Intel or AMD workstation—or a cloud-hosted x64 environment—may remain the safer choice.

7. Legacy Hardware Licence Dongles

Some professional software uses a physical USB licence key.

The application itself may run under emulation, but the dongle usually requires a proprietary driver or background service.

This can affect software used for:

Computer-aided design
Manufacturing
Surveying
Engineering
Broadcasting
Accounting
Laboratory work
Medical equipment
Specialist legal or financial systems

Ask the software vendor specifically whether both the application and its licence-management driver support Windows 11 Arm64.

Without the correct driver, the software may report that no licence is available.

8. Shell Extensions and Windows Customisation Tools

Applications that deeply modify the Windows experience may behave unpredictably.

Examples include:

File Explorer extensions
Alternative Start menus
Desktop customisation tools
Input method editors
Accessibility utilities
File-synchronisation overlays
Context-menu extensions
Screen-capture hooks
Window-management utilities

Microsoft warns that some applications that customise Windows may experience compatibility problems, including certain assistive technologies and cloud-storage applications.

An application may launch normally while a specific extension fails to appear inside File Explorer.

For example, you might lose:

Right-click menu commands
File-status icons
Preview handlers
PDF conversion options
Email attachment tools
Version-control overlays

9. Specialist Accessibility Software

Windows includes native accessibility features, but some third-party assistive technologies depend on close integration with the operating system.

Potential issues may affect:

Screen readers
Magnification software
Alternative input systems
Voice-control tools
Specialist keyboards
Braille devices
Eye-tracking equipment

Microsoft recommends checking with the assistive-technology provider because not every third-party product works as expected on Arm-based PCs.

Compatibility testing should be completed with the actual user and their complete hardware setup before replacing an existing device.

10. Older PDF, Printing and Document-Management Tools

Some PDF applications do more than open documents.

They may install:

Virtual PDF printers
Outlook add-ins
Scanner drivers
File Explorer extensions
Digital-signature hardware
Document-management connectors
Print-monitoring services

The main program may function under emulation while one of these integrations does not.

Check every required workflow, including:

Printing to PDF
Scanning directly into the application
Email conversion
Digital signatures
Document previews
SharePoint integration
Batch processing
Specialist fonts and print finishing

11. Obsolete 16-Bit and Very Old Software

Modern Windows no longer supports many historical application formats, regardless of whether the processor is Arm, Intel or AMD.

Windows on Arm does not provide a magic compatibility path for:

16-bit Windows applications
DOS programs requiring obsolete components
Old copy-protection drivers
Software tied to discontinued browser plug-ins
Applications requiring unsupported versions of Internet Explorer
Legacy hardware interfaces

These systems may require:

A retained legacy PC
A remote desktop environment
An x64 virtual machine hosted elsewhere
Application replacement
Vendor redevelopment

12. Applications With Architecture-Specific Installers

Sometimes the underlying program could work, but the installer blocks the process after detecting an Arm processor.

This may happen when:

The installer recognises only x86 and x64 systems.
Architecture checks are hard-coded.
A required dependency lacks an Arm64 version.
The installer bundles an incompatible driver.
The vendor has not validated the product on Arm.

Do not bypass the check automatically.

The installer may be preventing you from deploying a component that genuinely cannot run.

Contact the vendor and ask for a supported Arm64 or Arm64EC package.

Native, Emulated and Unsupported: The Practical Difference

Native Arm64

The application was built specifically for Arm-based Windows.

This normally offers the best:

Speed
Battery efficiency
Reliability
Hardware integration
Long-term support

Emulated x86 or x64

The ordinary desktop application is translated by Prism.

This is often suitable for:

Productivity tools
Utility software
Browsers
Communication applications
Traditional line-of-business applications without drivers

Performance can be very good, but results vary by workload.

Unsupported

The application depends on something Prism cannot translate, such as:

A kernel-mode driver
Unsupported virtual hardware
An incompatible anti-cheat system
A processor-specific component
A blocked installer
Unsupported low-level Windows integration

In that situation, changing compatibility mode usually will not solve the problem.

How to Check Whether an Application Is Native

Open Task Manager and select the Details tab.

Right-click a column heading, choose Select columns, and enable Architecture where available.

Applications may be shown as:

Arm64
x64
x86

You can also inspect the application’s documentation or download page.

When several installer versions are available, look for wording such as:

Windows on Arm
Arm64
AArch64
Snapdragon
Arm64EC

Do not assume “64-bit Windows” means Arm64. Many vendors use that phrase to mean x64 only.

Why Native Applications Are Still Better

Emulation has become impressively capable, but a native application normally remains preferable.

Native Arm64 software can offer:

Faster application startup
Lower processor usage
Better battery life
Reduced heat
Improved standby behaviour
Better integration with Arm drivers and hardware
Fewer compatibility variables

For occasional use, an emulated application may be perfectly acceptable.

For software used throughout the working day, native support should carry more weight in your purchasing decision.

A Business Compatibility Checklist

Before buying Snapdragon Windows laptops, create a list of everything each employee requires.

Check the following.

Core Applications

Microsoft 365
Web browsers
Teams and communication tools
Accounting software
CRM platforms
Document-management systems
Industry-specific applications

Security

Antivirus and EDR
DNS and web filtering
Data-loss prevention
Device control
Encryption management
Vulnerability scanning
Remote monitoring tools

Connectivity

VPN client
Wi-Fi authentication
Certificate deployment
Mobile broadband
Network drives
Remote Desktop
Zero-trust access software

Hardware

Printers
Scanners
Docks
External monitors
USB devices
Smartcard readers
Headsets
Specialist peripherals

Management

Microsoft Intune
Autopilot
Remote support
Asset management
Patch management
Backup agents
Software deployment

One unsupported component can make an otherwise excellent laptop unsuitable for a particular employee.

Test the Whole Workflow, Not Just the App

Do not stop after confirming that an application opens.

Test realistic tasks such as:

Opening and saving files
Printing
Scanning
Joining a video meeting
Connecting through the VPN
Accessing network drives
Using browser extensions
Installing updates
Signing documents
Connecting specialist hardware
Resuming after sleep
Working away from the office

The main executable may work while a supporting component fails.

Use a Pilot Group

Businesses should avoid replacing an entire laptop fleet without testing.

A safer process is:

Choose a small number of representative users.
Include employees with ordinary and specialist requirements.
Install the organisation’s full security and management stack.
Test office, home and mobile working.
Record unsupported applications and workarounds.
Confirm vendor support in writing where possible.
Expand deployment only after the pilot succeeds.

Snapdragon devices may be ideal for executives, mobile workers and employees whose workloads are primarily Microsoft 365 and browser-based.

They may be less suitable for users dependent on legacy peripherals, specialist drivers or local x64 virtual machines.

Do Not Confuse 26H1 With Improved Universal Compatibility

Windows 11 version 26H1 supports new hardware platforms, but its version number does not mean every compatibility gap has disappeared.

The limitations described above are primarily architectural and vendor-dependent.

An app needing an x64 kernel driver will not become compatible simply because the laptop ships with 26H1. The software or hardware vendor must provide a suitable Arm64 component.

The right question is therefore not:

Does this laptop run Windows 11 26H1?

It is:

Does every application, driver and peripheral required by this employee support Windows 11 on Arm?

What to Do When a Critical App Does Not Work

Possible options include:

Ask the vendor for an Arm64 release.
Use a supported web version.
Replace the peripheral with an Arm-compatible model.
Run the application on a remote x64 PC.
Use Windows 365 or another cloud desktop.
Retain an Intel or AMD device for that role.
Replace the legacy application.
Delay the Snapdragon deployment for affected users.

A mixed-device estate is often more sensible than forcing one processor architecture onto every workload.

How Hamilton Group Can Help

Windows on Snapdragon can provide excellent battery life, portability and performance, but compatibility must be assessed properly before deployment.

Hamilton Group can help businesses evaluate Arm-based Windows devices and identify risks before new hardware is purchased.

We can assist with:

Application compatibility testing
Snapdragon and Windows on Arm assessments
Hardware and peripheral reviews
Microsoft Intune and Autopilot
Security-agent validation
VPN testing
Printer and scanner compatibility
Pilot deployments
Device procurement
Windows lifecycle planning

Our team can match devices to the employees and workloads they are best suited to, rather than assuming one specification will work for everyone.

Most Apps Run—But Drivers Decide the Outcome

Windows 11 on Snapdragon now runs many x86 and x64 applications successfully through Prism.

The remaining problems are concentrated around software that depends on low-level components:

Drivers
Anti-cheat systems
VPN adapters
Security filters
Virtualisation platforms
Specialist peripherals
Windows customisation tools

Windows 11 version 26H1 arrives preinstalled on selected new devices and is not a general Windows Update upgrade for existing computers. Businesses considering those devices should test their full application, security and hardware stack before committing to a wider rollout.

For help assessing whether Snapdragon Windows devices are suitable for your business, contact Hamilton Group on 0330 043 0069 or book an appointment with one of our experts.

Previous Next