Look beyond the visible application
A product may include background services, plug-ins, virtual devices or hardware drivers as well as its main window. Its interface might work while establishing a network connection, recording audio or printing still fails. Each component can have different support requirements.
Start by describing which step succeeds and which fails. Opening an installer, signing into an app and producing output from a device are separate results. Keeping them separate makes the missing support easier to identify than a report that simply says the software does not work.
App emulation does not replace an ARM64 driver
Microsoft's Windows on Arm FAQ requires native ARM64 binaries for kernel-mode drivers and user-mode print drivers. Windows 11's ability to emulate x86 and x64 applications is not a promise to support drivers built for those architectures.
Even when the main application runs through emulation, its driver needs a separate check. Renaming a package or repeatedly running an x64 installer cannot convert the driver into an ARM64 build. The supplier generally needs to provide appropriate components and an applicable installation method.
Use the exact model on the official support page
Record the computer model, Windows version, full peripheral model and hardware revision. Select that product on the manufacturer's support site and read the operating-system, architecture, version and release information. A Windows 11 label alone does not establish Windows on Arm support.
If the page is unclear, ask three specific questions: is an ARM64 driver available, how should it be installed, and which features are supported? If the answer is to use a driver included with Windows, check whether advanced functions still require separate software.
Separate printer setup from printer capability
Microsoft has dedicated guidance for adding printers on Arm PCs. Some manufacturer installers may not complete setup; Microsoft's alternative is the Windows printer-addition process, unless the manufacturer gives different instructions for that device.
That is a defined alternative route, not a guarantee that every printer is supported. Test the functions you actually need, including duplex output, paper settings and scanning. Printing one test page does not establish that a multifunction device's scanning application also works.
Inspect status, then complete a real task
After following the supported installation procedure and restarting, open Device Manager and check the relevant device's status, driver provider and version. Record warning icons or error codes. Avoid installing several unrelated driver packages together, which makes it difficult to identify what changed the result.
Next, run a repeatable test: print a fixed document, connect to a specified network, record sample audio or perform the device's main operation. Repeat after a restart or sleep-and-resume cycle so the check covers more than the moment immediately after installation.
Give support a small, useful evidence set
Include computer and device models, Windows and driver versions, the official installation source, device status and minimal reproduction steps. Explain differences between working and failing paths. For example, “direct connection works, but the dock connection fails after sleep” helps separate driver, connection and power factors.
If the supplier does not yet support your setup, retain a working device or an alternative workflow and follow its release notes. This is a driver-checking guide, not a source of unverified third-party downloads. Windows detecting a device is not proof that every feature has been validated.
Sources and verification
This article draws on published documentation and editorial guidance. Unless explicitly stated, it does not report our own hardware tests. Sources checked: September 27, 2026.