Your interface worked fine last night. You boot Windows, hear the USB disconnect chime, hear the reconnect chime, and then nothing. The DAW opens to a “no audio device” dialog. Device Manager is where this gets solved, and most people look in the wrong place first.
I’ve been through this dance more times than I’d like: after a cumulative update, after a feature update, after a chipset driver got silently rolled back. The fix is usually boring. The trick is reading Device Manager correctly instead of unplugging and replugging the cable for the fifth time.
First: confirm it’s a Windows problem, not a cable problem
Open Device Manager before you touch anything else. Win+X, then Device Manager, or type it into the Start menu.
Now plug the interface in and watch the tree. If the whole list flickers and refreshes, Windows sees something on the bus. If nothing moves at all, you’re looking at a dead cable, a dead port, or a powered hub that isn’t passing enough current. Bus-powered interfaces are notorious for this. A port that supplied 500mA yesterday can behave differently after a power management change.
Try a rear-panel USB port directly on the motherboard, not a front-panel header and definitely not an unpowered hub. USB-C, USB 3.0, and Thunderbolt all deliver stable performance when the connection is healthy, but a marginal cable will fail right when the driver stack is already confused by an update.
Reading the three places your interface can hide
After a Windows update, a missing interface shows up in one of three states. Each one points to a different fix.
1. It’s under “Audio inputs and outputs” but the DAW can’t see it
This is the most common and the least scary. Windows has the class driver loaded, so the device appears, but your ASIO driver isn’t talking to the DAW. On Windows, ASIO drivers are essential for low-latency work, and a Windows update can leave the vendor driver in a half-installed state even though the device enumerates fine.
Right-click the device, Properties, and check the Driver tab. If the driver provider says Microsoft and the date is recent, Windows swapped in its generic USB Audio driver and parked your vendor driver. Your DAW won’t see an ASIO device because there isn’t one loaded.
Fix: reinstall the interface’s own driver from the vendor’s site, reboot, then relaunch the DAW. Not a Windows restart from the Start menu while the DAW is still open. A real reboot.
2. It’s under “Universal Serial Bus controllers” with a yellow bang
That yellow triangle next to “Unknown USB Device (Device Descriptor Request Failed)” is the classic post-update signature. Windows can’t read the device descriptor, so it can’t match a driver.
Right-click, Properties, and read the error code. Code 43 (“Windows has stopped this device because it has reported problems”) and Code 10 (“This device cannot start”) both point at the same underlying mess: a stale USB stack, a bad power-management setting, or a driver that doesn’t match the new kernel.
What I do, in order:
- Uninstall the device in Device Manager, tick “Delete the driver software for this device,” then unplug and reboot.
- Reinstall the vendor driver before plugging the interface back in.
- Then connect it and let Windows finish enumerating.
If that doesn’t take, roll back the USB host controller driver. Right-click the controller under USB controllers, Properties, Driver tab, “Roll Back Driver.” This is greyed out unless Windows kept the previous version, which it usually does for a few days after an update.
3. It’s under “Other devices” with a generic name like “USB Audio”
Windows knows something is plugged in but has no driver association. This is often the least painful case: point it at the vendor driver manually via “Update driver,” “Browse my computer,” and select the extracted driver folder. Do not let Windows search online for it. Windows Update’s catalog lags behind vendors and will happily install a two-year-old driver that “works” right up until you need low latency.
The power management gremlin
Here’s the one that eats a whole afternoon. The device looks fine in Device Manager, the driver is correct, and the interface still drops out mid-session or doesn’t appear on boot.
Windows has a “USB selective suspend” setting that parks idle USB devices to save power. For a webcam that’s fine. For an audio interface it’s a disaster. Find it under Power Options, Advanced settings, USB settings, USB selective suspend setting, and set it to Disabled on both battery and plugged in.
Then go back to Device Manager. For each USB Root Hub, Properties, Power Management tab, and untick “Allow the computer to turn off this device to save power.” Tedious, but it stops the random dropouts.
While you’re there, check your interface’s own power management tab. Some vendor drivers expose it, some don’t. If it’s there, untick it.
Clean up the ghost drivers
Every time you reinstall a driver, Windows is happy to leave the old one behind as a hidden device. After a few update cycles your system is carrying duplicate entries and the wrong one can win the enumeration race.
Open Device Manager, go to View, then “Show hidden devices.” Look under “Audio inputs and outputs” and “Sound, video and game controllers” for greyed-out duplicates of your interface. Uninstall every one of them, then reboot and let the current driver load clean.
This is also where you find the reason your buffer size settings keep resetting. If Windows is loading a different driver instance than the one you configured, your ASIO buffer won’t persist between sessions. More on that in a moment.
When none of this works
If the interface is genuinely not enumerating on any port, in any USB state, the problem may not be software. Windows updates can coincide with a hard failure by pure bad luck. Test the interface on a second machine before you blame the OS.
Two things worth knowing before you buy a replacement:
- Driver quality varies enormously by brand. RME, MOTU, and Universal Audio are known for rock-solid Windows driver performance. Budget interfaces are more hit-and-miss, and a cheap unit is more likely to fall over on a major Windows release.
- USB-C is the standard now, but USB-C on a laptop is often a hub chip running multiple protocols. If you can, dedicate a USB-A port to the interface and keep it there.
Once it’s back, reset the buffer size deliberately. Windows updates sometimes nudge the default, and a 512-sample buffer that felt fine for tracking will feel sloppy once it drifts. Open your DAW’s audio preferences, confirm the vendor ASIO driver is selected (not ASIO4ALL, not Windows Audio), and set the buffer to something sensible for the session: 128 for tracking, 256 or 512 for mixing. Save the setting so the driver remembers it.
That covers the walkthrough end to end. Most of these are five-minute fixes once you know which of the three Device Manager states you’re looking at. The annoying part isn’t the fix. It’s remembering to check the power settings and hidden devices before you start reinstalling things at 11pm.