ASIO4ALL on Windows on Arm and ARM64 PCs
ASIO4ALL 2.22 adds native ARM64 and ARM64EC support for Windows on Arm. To check a Snapdragon or other Arm-based PC, first confirm the DAW runs on your system. Then check that Windows recognizes the audio hardware and that the DAW exposes the driver.

In this guide
Does ASIO4ALL work on Windows on Arm?
Yes. ASIO4ALL 2.22, released on July 23, 2026, adds native ARM64 and ARM64EC support, so ASIO4ALL on Windows on Arm PCs such as Snapdragon laptops is now a supported setup. To get it working, confirm your DAW runs on your Arm system, make sure Windows already recognizes the audio hardware, then select ASIO4ALL v2 in the DAW and enable your devices.
ASIO4ALL is a universal ASIO driver that sits on top of the existing WDM drivers in Windows. On an Arm PC that design matters: if Windows can see your audio device, ASIO4ALL has something to work with. This guide covers how to check your system, what version 2.22 changes and how to confirm a working playback and recording path.
What you need
- A Windows 10 or Windows 11 PC; Windows on Arm devices typically ship with Windows 11.
- ASIO4ALL 2.22 or later, installed with
ASIO4ALL_2_22.exefrom asio4all.org. - A DAW or audio host that runs on your system, natively or under emulation.
- An audio device Windows recognizes, such as built-in audio or a class compliant USB device.
Check Windows, the DAW and the interface
Before installing anything, confirm three things: that the PC really is Arm-based, how your DAW runs on it, and whether your audio hardware has the Windows support it needs.
Confirm the system type
In Windows, open Settings › System › About. Look for the system type under Device specifications. An Arm-based processor is listed there.
Check how your DAW runs
Check the DAW publisher's documentation for a native ARM64, ARM64EC, or supported emulated configuration for your edition. Windows 11 on Arm can emulate many x86 and x64 user applications, so a DAW without an Arm build may still run. Plug-ins matter too, since a host generally needs plug-ins that match how it runs.
Check the audio interface
Hardware drivers still have to meet the platform's requirements, and that is a separate question from whether applications are emulated. An audio interface may work through a Windows USB Audio Class driver, while a vendor control app or hardware feature may require separate Arm support. Check the interface maker's documentation for the features you rely on.
Note: ASIO4ALL does not replace a hardware driver. It needs a working Windows audio device underneath it, so a device that is missing from Windows will also be missing from ASIO4ALL.
Native ARM64, ARM64EC and emulated hosts
Windows on Arm can run applications in more than one way. ARM64 applications are built specifically for Arm processors. ARM64EC is a Microsoft approach that allows Arm-native code to work alongside x64 code running under emulation. ASIO4ALL 2.22 provides native ARM64 and ARM64EC support, which covers both kinds of host.
| Host type | What it means | What to check |
|---|---|---|
| Native ARM64 DAW | Built for Arm processors | The DAW's Arm build and its plug-in support |
| ARM64EC-based host | Mixes Arm-native and emulated x64 code | The publisher's statement about supported configurations |
| Emulated x64 or x86 DAW | Runs through Windows emulation | Whether the publisher supports that configuration |
Whichever type you use, the practical test is the same: does ASIO4ALL v2 appear in the host's driver list, and does audio pass in both directions?
Plug-ins and instruments
Your DAW is only part of the picture. Virtual instruments and effects are separate pieces of software, and each one has its own architecture. A native Arm host may not load plug-ins built only for x64, and an emulated host may behave differently from the same host on an Intel or AMD machine. Check the plug-in makers' documentation for the instruments and effects your sessions depend on.
Performance expectations
Emulation adds work for the processor. If a session that ran comfortably on an older x64 laptop crackles under emulation, try a larger buffer before assuming the driver is at fault. Where your DAW offers a native Arm build, it is usually the better place to start, provided the plug-ins you need are supported there too.
What ASIO4ALL version 2.22 changes on Arm
The version 2.22 release notes describe native ARM64 and ARM64EC support and specifically mention older USB Audio Class compliant devices. A class compliant device that Windows already sees is a practical starting point. Check it in Windows Sound before opening an ASIO session.
Highlights of 2.22
- Native ARM64 and ARM64EC support on Windows on Arm.
- Improved dropout prevention in certain cases.
- Default settings that work with Qualcomm Aqstic mic array input.
- One shared configuration for native ARM64 applications.
The Qualcomm Aqstic mic array
The 2.22 notes say the Qualcomm Aqstic mic array now works with defaults. Older instructions for that mic may refer to a previous version, so start with the default settings before following any older workaround.
Earlier releases worth knowing
Version 2.21 (June 10, 2026) brought USB Audio Class 1 improvements at 44.1 kHz, and 2.20 (April 27, 2026) added an option to pause host audio from the system tray. The version history guide lists the changes in order.
Install ASIO4ALL 2.22 on an Arm PC
Installation follows the same pattern as on any Windows PC. Download ASIO4ALL_2_22.exe from the publisher at asio4all.org, run the installer and restart your audio application so it picks up the driver. The installation guide covers the process in more detail.
Shared settings across native ARM64 apps
The release notes describe one shared configuration for native ARM64 applications. If you use two DAWs with different devices or buffer settings, check the settings when you switch. A buffer that suits a music session in one host may be wrong for a podcast in another.
Tip: Keep a short note of the devices and buffer size you use in each host. When you switch DAWs, a quick look at the ASIO4ALL control panel against that note avoids surprises.
Choose a buffer to start with
Buffer time is samples divided by sample rate, multiplied by 1000. At 48 kHz, 256 samples is about 5.3 ms and 512 samples about 10.7 ms. Starting at 256 or 512 and lowering it once everything works is a calm way to find a stable low latency setting; see the buffer size guide.
Confirm a playback and recording path
Work through one route at a time. A device that is missing from Windows points first to the connection, hardware mode, or Windows driver. An output that appears in ASIO4ALL but is silent points first to the output selected in your host and the connected headphones or speakers.
- Install 2.22 from the ASIO4ALL publisher and restart the audio application.
- Select ASIO4ALL v2 in the host, open its control panel, and enable one Windows audio output.
- Play a short clip through that output, then enable and assign one input in a new recording track.
- Record a short sample and play it back before moving an existing session to the new setup.
The publisher's device selection documentation explains how the device list in the control panel works.
Where to find the driver setting in common DAWs
- FL Studio:
Options › Audio settings - Ableton Live:
Options › Settings › Audio - Cubase:
Studio › Studio Setup › Audio System - REAPER:
Options › Preferences › Audio › Device
Troubleshooting ASIO4ALL on Windows on Arm
Most problems on Arm PCs come down to the layers beneath ASIO4ALL: the DAW's architecture, the hardware driver or a vendor tool. Work from the bottom up.
Quick checks
- ASIO4ALL v2 not listed: confirm 2.22 is installed and restart the host.
- Device missing: check that it appears in Windows Sound first.
- USB microphone not recording: enable its input in the control panel and assign it to a track; the USB microphone guide has more detail.
- Settings changed unexpectedly: remember native ARM64 apps share one configuration.
- Vendor features unavailable: the interface's control app may need its own Arm support.
Isolate the layer causing the problem
If audio works in Windows Sound but not in the DAW, the issue sits between the host and ASIO4ALL: check the driver selection, the enabled devices in the control panel and the track routing. If audio fails in Windows Sound as well, ASIO4ALL cannot fix it, and the connection, cable or hardware driver needs attention first. Testing a simple built-in output alongside your USB device is a quick way to see which side the problem is on.
Watch out: Do not move an important session to a new Arm PC on the day of a recording. Test playback, recording and your usual plug-ins first, so any gap in Arm support shows up before it matters.
Frequently asked questions
Version 2.22, released on July 23, 2026, adds native ARM64 and ARM64EC support. Install it from asio4all.org with the ASIO4ALL_2_22.exe installer.
If Windows recognizes it, for example through the USB Audio Class driver, ASIO4ALL can usually use it. Vendor control apps or special features may need separate Arm support from the manufacturer.
Windows 11 on Arm can emulate many x86 and x64 applications, and ASIO4ALL 2.22 includes ARM64EC support. Check the DAW publisher's documentation for the configurations it supports.
The 2.22 release notes describe one shared configuration for native ARM64 applications. Check the device list and buffer each time you switch hosts.


