The update landed on a Tuesday, and by Tuesday night my interface was gone. Not dead, exactly. Device Manager said it was there. The DAW disagreed. No inputs, no outputs, and a driver panel that opened to an empty window. If you are reading this after a 24H2 update flattened your rig, you already know the feeling. Here is the order I worked through before I touched the rollback button, and what actually fixed it.
First: stop trusting Device Manager alone
Device Manager is a liar with a clean conscience. It will happily show your interface sitting there, named and undrivered, and call the situation fine. What matters is whether the audio service can see it.
Open Sound Settings and check the input and output device lists, not the control panel. If your interface vanished from those lists while showing up in Device Manager, the driver did not load against the current build. That is a driver-side problem, not a hardware failure. Your preamps and converters are almost certainly fine. The software handshake is what broke.
This is the first thing to establish, because it decides everything downstream. A device that has dropped off the audio stack can usually be recovered. A device that has dropped off the USB bus entirely is a different investigation.
Check the connection before you blame the OS
USB-C and Thunderbolt interfaces are compact and reversible, which is nice, but they are also fussy about what they are plugged into. The connection has to sustain low latency and high sample rates on a stable driver, and a flaky port or a tired hub will sabotage that even on a healthy Windows build.
So before any deeper surgery:
- Move the interface to a different USB port, ideally one on the motherboard rather than a hub.
- Swap the cable if you have a spare. Cheap USB-C cables fail quietly.
- Unplug every other USB device you do not strictly need, then reconnect the interface alone.
- If your interface is bus-powered, try a powered hub or its own supply if it has one.
If the device reappears in the audio stack after this, you never had a 24H2 bug. You had a port or a hub problem that happened to show up the same week. Frustrating, but cheap to fix.
The driver reinstall, done properly
A plain reinstall usually does nothing, because Windows keeps the broken driver package and just reinstalls the same mess. You need to remove it first, and removal means more than clicking uninstall in the driver panel.
What works, in order:
- Uninstall the interface driver through its own uninstaller, not just Device Manager.
- Open Device Manager, tick Show hidden devices, and delete any greyed-out entries for your interface under Audio inputs and outputs and under Sound, video and game controllers.
- Reboot with the interface unplugged.
- Install the latest driver from the manufacturer, pulled fresh rather than from your downloads folder, since 24H2 may need a newer build than the one you had.
- Plug the interface back in only when the installer asks for it.
Drivers are the whole game here. A good audio interface lives or dies on well-maintained drivers that keep working across OS updates, and a major Windows feature update is exactly the moment those drivers get stress-tested. If the manufacturer has not shipped a 24H2-ready build yet, no amount of reinstalling will help. Check their support page for a known-issues note before you spend an evening on it.
ASIO and the sample rate trap
Here is one that catches people who did everything right. The driver installs, the device shows up, audio plays, and then your DAW refuses to open the interface at all. Look at the sample rate.
Windows and your DAW can end up requesting different rates from the same device. If the Windows sound settings are pinned to one rate and your project is set to another, the ASIO driver may hand exclusive control to whichever asked first, and the other one gets nothing. Set both to the same value, typically 24-bit / 48kHz for most tracking and mixing work, and see if the conflict clears.
Higher rates are useful for sound design and classical recording, but they are rarely necessary for everyday production, and they multiply the chances of a mismatch after an update resets your audio settings. Start conservative. Get the device talking. Raise the rate later once things are stable.
The obvious fix nobody tries: roll back the update
You can roll back a feature update within a limited window after it installs. Settings, Windows Update, Update history, then Uninstall updates. If 24H2 is listed there and your rig is dead in the water, this gets you working again in minutes and buys you time to solve it properly.
Do it as a stopgap, not a lifestyle. The rollback window closes, and you will face the update again. Use the breathing room to check whether your interface maker has published a fixed driver. If they have, install it and re-take the update. If they have not, you now know exactly which vendor is dragging its feet.
A cheap insurance policy: image your system drive before any major Windows update. It turns a ruined session into a twenty-minute restore. I learned this the hard way, and I now do it every time Microsoft pushes a feature update.
When it is genuinely not your interface
Sometimes the device is fine and the rest of the chain is the problem. If your interface works but your DAW still stutters, watch your CPU and buffer settings. A 24H2 update can shuffle background services and power plans, and a power plan that throttles USB or the CPU mid-session will produce dropouts that look like a driver fault.
Set the power plan to high performance, disable USB selective suspend, and raise your buffer size one notch to see if the crackle disappears. If it does, you were chasing a latency and scheduling problem, not a dead interface. Nothing about your converters or preamps changed. The machine just got greedier about power management.
What I actually did
For the record: a clean driver removal, a fresh vendor build published two weeks after 24H2, and a matched 48kHz setting across Windows and the DAW. That was it. The interface came back and has been solid since. The rollback was never needed, but I kept it on the table until the new driver proved itself over a full tracking day.
If your device is still missing after all of this, stop reinstalling and start reading your manufacturer’s support page like it owes you money. The answer is usually there, in a changelog nobody reads, dated after the update that broke you.