Fix 0X00000924: 'This list of devices is invalid'

Windows throws 0X00000924 when a device list is corrupted, often after a driver update or USB hub change. Clear the stale device entries via Device Manager or registry, then rescan hardware.

You're plugging in a USB drive or a printer, and instead of the usual chime, Windows throws a dialog: "This list of devices is invalid" with the code 0X00000924. This happens most often right after a Windows Update that touches the USB or storage stack, or after you've swapped out a docking station that had a bunch of devices attached. I've also seen it pop up on machines where a driver update failed mid-install, leaving the device list in a half-written state.

What's actually happening here

Windows keeps an internal registry of every hardware device it has ever seen — the full device tree. That list lives in the registry, under HKLM\SYSTEM\CurrentControlSet\Enum. When you connect a device, Windows reads that list to figure out which drivers to load and how to configure the device. If that list gets corrupted — a bad write, a partial driver install, a power loss during a write — Windows can't parse it, and it bails out with 0X00000924.

The error message is misleading. It's not saying your device is invalid. It's saying the list is invalid — Windows can't make heads or tails of what's already recorded. The corruption is usually limited to a few stale entries, not the whole hive. That's why a full registry restore is overkill. You just need to clear the broken entries and let Windows rebuild them from scratch.

The fix: clear stale device entries

Skip the system restore and the SFC scan — they don't touch this part of the registry reliably. What works is forcing Windows to forget the bad records and rescan. Here's the order I do it in, and it's worked on every machine I've touched.

Open Device Manager. Press Win + X and select Device Manager. You might see a device with a yellow warning icon, but often you won't see anything obviously wrong.
Show hidden devices. From the menu bar, go to View → Show hidden devices. This reveals ghost devices — the ones that Windows remembers but hasn't seen recently. Those ghosts are the usual suspects for corruptions.
Uninstall the problem device. Right-click on the device that triggered the error (or any device with a warning icon) and choose Uninstall device. If there's a checkbox for "Delete the driver software for this device," tick it. This removes the registry entry cleanly.
Scan for hardware changes. Click the monitor icon in the toolbar (or right-click your PC name and select Scan for hardware changes). Windows will re-detect the device and rebuild its entry from the driver's INF file — a fresh, valid list entry.
Reboot. Not optional. The device list is cached in memory, and a reboot flushes it. After the restart, plug in the device again. It should enumerate normally.

If that doesn't clear it — go nuclear on the registry

Sometimes the corruption isn't tied to one device; it's a broad issue across the Enum key. The safe way to reset without losing all your driver settings is to delete only the problematic subkeys. Here's how:

reg delete "HKLM\SYSTEM\CurrentControlSet\Enum\USB" /f
reg delete "HKLM\SYSTEM\CurrentControlSet\Enum\USBSTOR" /f

Run those in an elevated Command Prompt (right-click → Run as administrator). USB covers most plug-and-play devices; USBSTOR covers mass storage. Deleting these keys forces Windows to rebuild the entire USB device list on next boot. The catch: you'll lose custom device names and possibly need to re-pair Bluetooth devices if they were under a different subkey. For most people, that's a fair trade.

Warning: Don't delete the entire Enum key. That wipes your network adapters, display drivers, and everything else. Stick to the subkeys you know are corrupt.

Still failing? Check these

Driver store corruption. If the rebuild still hits 0X00000924, the driver package itself might be bad. Run pnputil /enum-drivers to list stored drivers, then delete any with a yellow flag using pnputil /delete-driver oemXX.inf /uninstall.
Malware or security software interference. I've seen aggressive antivirus hook into device installation and corrupt the list. Temporarily disable real-time protection (not the whole product) and try again.
Pending Windows Update. A half-installed update can leave the device list in a weird state. Run wuauclt /detectnow (or just check Settings → Windows Update) and install everything pending. Reboot.

The 0X00000924 error is rarely fatal. It's a symptom of a messy device history, not a broken piece of hardware. Clear the stale entries, let Windows rebuild, and you're back to normal. If you're still stuck after the registry cleanup, consider a repair install of Windows — that preserves your files but replaces the system files that might be holding the corruption.