Releases

ASIO4ALL Version History and Release Notes

ASIO4ALL updates can change device detection, how a host controls the buffer, and which applications can load the driver. The publisher's changelog is the best starting point when an update fixes a specific problem or when a studio needs to keep an existing setup reproducible.

Three generations of audio interfaces and older and newer laptops neatly arranged on desk
In this guide

ASIO4ALL version history: the short answer

The current ASIO4ALL release is version 2.22, published on July 23, 2026, which adds native ARM64 and ARM64EC support for Windows on Arm. It follows 2.21 (June 10, 2026), 2.20 (April 27, 2026, with the corrected 2.20.1 build) and 2.19 (April 2026). The publisher officially supports Windows 10 and Windows 11.

This page traces the ASIO4ALL version history from 2.19 to 2.22 and explains what each release changed in practical terms. It also covers how to read release notes, how to record a baseline before updating a working studio PC, and when it makes sense to stay on an older build for a while.

ASIO4ALL releases 2.19 to 2.22 at a glance
VersionReleasedMain changes
2.22July 23, 2026Native ARM64 and ARM64EC support, fixes for certain audio dropouts, Qualcomm Aqstic mic array works with default settings
2.21June 10, 2026USB Audio Class 1 improvements at 44.1 kHz, simplified installer, offline settings enabled automatically
2.20April 27, 2026Tray action to pause host audio and release devices; crash in early builds corrected in 2.20.1
2.19April 2026Fixes for Bluetooth connection status, input distortion in some mixed device setups, a Studio One reset loop

The authoritative record is the publisher's ASIO4ALL version history. This expert summary is meant to help you decide whether an update is relevant to your setup, not to replace the official notes.

ASIO4ALL 2.22 and Windows on Arm

Version 2.22 arrived on July 23, 2026, and its headline change is native ARM64 and ARM64EC support. That matters for laptops and tablets running Windows on Arm, where the release brings native driver support for Arm-based hosts. If you produce on an Arm laptop, this is the version to look at first.

What the 2.22 release notes list

  • Native ARM64 and ARM64EC support on Windows on Arm.
  • Improved prevention of audio dropouts in certain cases.
  • Default settings that work with the Qualcomm Aqstic microphone array input.
  • Official support for Windows 10 and Windows 11.

The installer for this release is ASIO4ALL_2_22.exe, available from asio4all.org. The full notes are on the publisher's version 2.22 page.

Shared configuration on ARM64

Native ARM64 applications currently share a global configuration. In practice, changing the device setup in one host can affect what you see when you open another. If you use two native ARM64 hosts on the same machine, check the ASIO4ALL panel each time you switch between them rather than assuming each keeps its own settings.

Note: When you read an older forum post or guide about ASIO4ALL on Arm, compare its version number with the 2.22 release notes before applying a workaround. Advice written for earlier builds may no longer apply. Our ASIO4ALL on Windows ARM64 guide covers the current situation in more depth.

ASIO4ALL 2.21: USB Audio Class 1 improvements

Version 2.21, released on June 10, 2026, focused on USB Audio Class 1 devices. Many simple USB microphones, headsets and small interfaces use this class, so the change reaches a wide range of hardware commonly paired with ASIO4ALL.

What changed

The publisher describes improved handling of USB Audio Class 1 devices, with changes relevant to stability and round-trip latency at 44.1 kHz. If you record at 44.1 kHz with a class-compliant USB device and previously saw instability, this release is the one to check first.

To put that sample rate in perspective, a 256-sample buffer at 44.1 kHz lasts about 5.8 ms (256 ÷ 44,100 × 1000). Round-trip latency includes both input and output buffers plus device overhead, which is why a driver's handling of a specific device class can make an audible difference at the same nominal buffer.

Installer changes

Version 2.21 also simplified the installer. Optional component selection was removed and offline settings are enabled automatically. If you have older installation notes that mention choosing components, they describe the pre-2.21 installer. See the publisher's version 2.21 notes for the original wording.

ASIO4ALL 2.20 and the 2.20.1 correction

Version 2.20, released on April 27, 2026, added a new action in the system tray. It pauses DAW audio processing and releases the audio devices so another application can take over, without closing the host.

Why the tray pause is useful

ASIO4ALL works on top of the existing WDM drivers and opens the devices it uses. While a DAW holds them, other applications may not be able to play or record through the same hardware. The pause action gives you a quick way to hand the device to a browser, a video call or a media player and then return to your session.

  • Checking a reference track in a browser without closing the DAW.
  • Joining a short call on the same headset you record with.
  • Letting a system sound or notification play during a long editing session.

The 2.20.1 build

The publisher corrected a crash present in early 2.20 builds and identifies the corrected build as 2.20.1. If you are still running a 2.20 build and see crashes, check which exact build is installed. More details are on the version 2.20 release page.

Watch out: "Version 2.20" alone does not tell you whether you have the corrected build. Confirm the full version shown in the ASIO4ALL control panel before ruling the crash fix in or out.

ASIO4ALL 2.19: a fixes release

Version 2.19, also released in April 2026, was focused on fixes rather than new features. Its notes describe three specific problems, each tied to a particular kind of setup.

Issues addressed in 2.19

  • Bluetooth connection status: an incorrect connection status for Bluetooth devices.
  • Mixed device input distortion: input distortion in some configurations that combine different devices.
  • Studio One reset loop: a host reset loop observed in Studio One.

If any of those symptoms match yours and you are on an older build, updating is a reasonable first step. Combining several devices is covered in our guide to ASIO4ALL device aggregation, and the original notes are on the publisher's version 2.19 page.

How to read ASIO4ALL release notes

ASIO4ALL updates can change device detection, how a host controls the buffer, and which applications can load the driver. Release notes are brief, so it helps to read them with your own setup in mind.

Questions to ask about each entry

For every line in a changelog, ask whether it mentions your hardware type, your host, your Windows version or your sample rate. A fix for USB Audio Class 1 devices at 44.1 kHz is highly relevant to a podcaster with a USB mic at that rate and irrelevant to someone using only built-in audio at 48 kHz.

Also note the difference between a new feature and a fix. A fix may resolve a problem you have been working around, which means you can remove the workaround after updating. A new feature, such as the tray pause in 2.20, may change how you work but rarely changes existing behaviour.

Older versions

This summary covers releases from 2.19 onwards. For anything earlier, rely on the publisher's version history page, which is the reference for older releases. Use the publisher's download archive when you need to identify or retrieve an older release, and avoid third-party mirrors. Our ASIO4ALL download guide explains how to get the right file safely.

Record a baseline before you update

A repeatable baseline is more useful than comparing buffer numbers from memory. If your recording PC works today, a few minutes of notes make it much easier to judge whether a new ASIO4ALL version improves things or introduces a change you need to adjust for.

  1. Open the ASIO4ALL control panel and note the installed version.
  2. Write down the active inputs and outputs, including which device each belongs to.
  3. Record the sample rate and buffer size your sessions use.
  4. Save a small session in your DAW that you can reopen to check monitoring, recording and playback.
  5. Install the new version from asio4all.org.
  6. Run the same session with the same audio hardware and settings, and compare.

If the behaviour changes, confirm the new build in the control panel and check the release notes for the symptom. Change one variable at a time; updating the driver, the DAW and Windows on the same day makes it hard to know which one caused a difference.

Tip: Keep your baseline notes with the test session file. When a collaborator or a future you needs to reproduce the setup, the version number, sample rate and buffer are all in one place.

When to wait before updating

If you are in the middle of a project with a deadline and your current build is stable, it is reasonable to finish the project first. Update when you have time to run the baseline test, unless the release notes describe a problem you are actively experiencing.

Frequently asked questions

The latest release is ASIO4ALL 2.22, published on July 23, 2026. The installer is ASIO4ALL_2_22.exe from asio4all.org, and the publisher officially supports Windows 10 and Windows 11.

Yes. Version 2.22 adds native ARM64 and ARM64EC support. Native ARM64 applications currently share a global configuration, so a device change in one host can show up in another.

It is the corrected build of version 2.20. The publisher fixed a crash found in early 2.20 builds and identifies the corrected build as 2.20.1.

Use the publisher's download archive on asio4all.org. Before rolling back, record your current settings and check the version history to see whether the problem you are solving was addressed in a newer release.

Sources and further reading

ASIO4ALL Editorial Team

We write expert, hands-on guides for Windows musicians, podcasters and producers. Driver facts are checked against the publisher's manual and release notes; DAW steps against each vendor's documentation.