The answer is to not use an ASIO driver until you need to. Use Band-in-a-Box's MME or WAS audio setting instead of ASIO.

Generally, an ASIO driver is created by an equipment manufacturer to minimize recording latency. Record latency is the amount of time the audio interface, your computer and the recording program requires to record your performance. As Byron pointed out ASIO4All is not an ASIO driver and it has its own set of issues.

Most ASIO drivers suffer from the same issue. They allow only one program at a time to access the driver. Some programs aggravate the issue because they do not release the driver even when they are no longer using the driver.

Microsoft is aware of the issues surrounding ASIO drivers and introduced WASPI or WAS as an alternative that does not depend on an equipment manufacturer. The Windows Audio Session API (WASAPI or WAS) enables programs to manage the flow of audio data between the program and an audio endpoint.

So, when you are recording, if you are using an audio interface to record and the audio interface manufacturer provides an ASIO driver, use the equipment specific driver while recording.

Attached Files (Click to download or enlarge) (Only available when you are logged in)
Clipboard01.jpg (74.52 KB, 85 downloads)
Audio Driver Settings

Jim Fogle - 2025 BiaB (Build 1128) RB (Build 5) - Ultra+ PAK
DAWs: Cakewalk Sonar - Standalone: Zoom MRS-8
Laptop: i3 Win 10, 8GB ram 500GB HDD
Desktop: i7 Win 11, 12GB ram 256GB SSD, 4 TB HDD
Music at: https://fogle622.wix.com/fogle622-audio-home