Why Drivers Are Different on Windows on ARM
On traditional x86/x64 Windows PCs, device drivers are compiled for the x64 architecture. On Windows on ARM, kernel-mode drivers must be native ARM64 — unlike regular applications, drivers cannot run under emulation. This is a fundamental Windows security and stability requirement.
User-mode drivers and software components can run under emulation, but the core kernel driver must be ARM64-compiled. This means that if a hardware manufacturer hasn't released an ARM64 driver, the device simply won't work on WoA — full stop.
How to Check for Missing Drivers
The first step is to identify what's missing or flagged. Here's how:
- Right-click the Start button and select Device Manager
- Look for any entries with a yellow exclamation mark — these indicate driver problems
- Right-click a flagged device and choose Properties to see the error code
- Common codes: Code 28 (no driver installed), Code 10 (device failed to start), Code 52 (unsigned driver blocked)
Method 1: Windows Update (Best First Step)
Microsoft has significantly expanded driver delivery through Windows Update for WoA devices. Many OEM ARM64 drivers are delivered automatically:
- Go to Settings → Windows Update → Advanced options → Optional updates
- Expand the Driver updates section
- Select all available driver updates and click Download & install
- Restart when prompted
This method is the safest and most reliable — Microsoft tests and signs these drivers for ARM64 compatibility.
Method 2: Manufacturer's Website
For peripherals and components not covered by Windows Update:
- Visit the device manufacturer's support page and look for ARM64 or "Windows on ARM" driver downloads
- Search specifically for terms like "ARM64", "Snapdragon", or "Windows on ARM" in the driver section
- Check the driver release notes to confirm ARM64 support before downloading
Tip: Printer and scanner manufacturers (HP, Epson, Canon) have been steadily releasing ARM64 drivers for current product lines. Older devices may be permanently unsupported.
Method 3: OEM Support Apps
If your WoA device came from a major OEM, their support application is often the most targeted way to get device-specific drivers:
- Lenovo Vantage — surfaces Snapdragon-specific driver and firmware updates
- HP Support Assistant — includes ARM64 driver packages for HP devices
- Samsung Update — delivers Galaxy Book ARM driver updates
- Microsoft Surface app — manages Surface-specific firmware and driver updates
Method 4: Manually Updating via Device Manager
If you have an ARM64 driver file (.inf package) but Windows hasn't installed it automatically:
- Open Device Manager
- Right-click the device needing the driver
- Choose Update driver → Browse my computer for drivers
- Navigate to the folder containing the extracted driver files
- Check "Include subfolders" and click Next
Common Driver Problems and Solutions
| Issue | Likely Cause | Solution |
|---|---|---|
| Device not recognized at all | No ARM64 driver exists | Check manufacturer for ARM64 support roadmap |
| Code 52 error | Unsigned or x64-only driver blocked | Find ARM64-signed driver; do not disable Secure Boot |
| Audio crackling or drop-outs | Outdated audio driver | Check Windows Update optional drivers or OEM app |
| Wi-Fi disconnects randomly | Qualcomm Wi-Fi driver bug | Install latest Qualcomm Wi-Fi driver via Windows Update |
| USB device not working | Missing USB controller or device driver | Try Windows Update; check device manager for flags |
A Word on Driver Security
Only install drivers from trusted, official sources. Windows on ARM enforces Secure Boot and driver signing requirements. Never disable these protections to install an unsigned driver — doing so undermines the security model that makes WoA devices particularly resistant to low-level malware. If a driver requires you to disable Secure Boot, treat it as a serious red flag.