“This device cannot start. (Code 10)” appears in Device Manager when Windows can’t load the driver for a device, usually a USB gadget, audio adapter or Wi-Fi card. A corrupted or outdated driver is the most common culprit, and most cases are fixable without touching the registry.
Before diving in, test the device on another PC if you can. If it fails there too, the hardware itself is likely dead. If it works fine elsewhere, the problem is on your machine so keep reading.

Fix #1: Restart Your PC
A simple reboot clears driver state glitches that survive sleep and hibernate cycles. Skip this if you’ve already restarted since the error appeared.
- Save any open work and click Start > Power > Restart.
- After the machine comes back up, reconnect the device and check Device Manager again.
If the yellow triangle is gone, you’re done. If it’s still there, move to Fix #2.
Fix #2: Disable and Re-enable the Device
Toggling the device in Device Manager forces Windows to reinitialize the driver without a full reboot.
- Right-click the Start button and select Device Manager.
- Find the device showing the yellow triangle, right-click it, and choose Disable device.
- Wait 10 seconds.
- Right-click the same device again and choose Enable device.

Check whether the Code 10 error is gone in the device’s Properties. If not, continue.
Fix #3: Uninstall and Reinstall the Driver
This is the fix that works for most people. Removing the driver completely lets Windows pull a clean copy on the next boot.
- Right-click Start and open Device Manager.
- Right-click the problem device and select Uninstall device.
- If you see a checkbox labeled Delete the driver software for this device (or Attempt to remove the driver for this device), check it.
- Click Uninstall to confirm.
- Restart your PC. Windows will automatically detect the device and reinstall its driver.

If Windows reinstalls a driver but the error comes back, the driver it’s pulling is still bad – update it manually in Fix #4.
Fix #4: Update the Driver from the Manufacturer’s Site
Windows Update sometimes installs a generic driver that doesn’t fully support your hardware. Grabbing the driver straight from the manufacturer usually fixes this.
- Identify the device make and model. If it’s a USB audio adapter, Wi-Fi card, or printer, check the box or the manufacturer’s label on the device.
- Go to the manufacturer’s support site (for example, Realtek for audio chips, Intel for network adapters, or your PC maker’s support page for bundled hardware) and download the latest driver for your Windows version.
- Run the installer, or if it’s a .zip file, extract it somewhere you’ll remember.
- Open Device Manager, right-click the problem device, and select Update driver.
- Choose Browse my computer for drivers and point it to the folder where you saved the download.
- Follow the prompts and restart when asked.

Fix #5: Roll Back the Driver
If Code 10 started after a Windows Update or a driver update, rolling back to the previous version often resolves it immediately.
- Open Device Manager, right-click the problem device, and select Properties.
- Click the Driver tab.
- Click Roll Back Driver. If the button is grayed out, there’s no previous driver to restore — skip to Fix #6.
- Select a reason when prompted and click Yes.
- Restart your PC.

Fix #6: Run the Hardware and Devices Troubleshooter
Windows includes a built-in diagnostic that scans for driver and configuration problems automatically. It’s worth running before touching the registry.
- Press
Windows + Rto open the Run dialog. - Type
msdt.exe -id DeviceDiagnosticand press Enter. - Click Next and let the troubleshooter scan.
- Apply any fixes it suggests, then restart.

You can also reach additional hardware troubleshooters via Settings > System > Troubleshoot > Other troubleshooters. See our guide on how to enable troubleshooting mode in Windows 11 for more detail.
Fix #7: Uninstall All USB Controllers (USB Devices Only)
If the problem device is USB-based and none of the above has worked, the USB controller stack on your machine may be corrupted. Clearing it out forces Windows to rebuild it cleanly.
- Open Device Manager and expand Universal Serial Bus controllers.
- Right-click the first entry and choose Uninstall device. Repeat for every entry under that section.
- Restart your PC. Windows will automatically reinstall all USB controllers.
- Reconnect your device and check Device Manager.

Fix #8: Delete UpperFilters and LowerFilters in the Registry (Advanced)
Corrupt registry filter entries left behind by old software installs can block a driver from loading entirely. This fix is more involved so back up your registry before making changes.
- Press
Windows + R, typeregedit, and press Enter. Click Yes if prompted by UAC. - Before changing anything, click File > Export and save a backup of the registry to your Desktop.
- Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class. - Find the subkey (GUID) that corresponds to your device class. For USB devices, look for
{36FC9E60-C465-11CF-8056-444553540000}. For other devices, check the Class value inside each subkey to match your device type. - Look for values named UpperFilters or LowerFilters in the right pane.
- If either exists, right-click it and choose Delete.
- Close Registry Editor and restart your PC.

When the Fixes Don’t Work
If all eight fixes fail and the device still shows Code 10, the hardware itself is probably faulty — especially if it also fails on a second PC. Contact the device manufacturer for a warranty replacement or try a different unit. In rare cases where the error appears on a built-in component (like an integrated audio chip or Wi-Fi card), a Windows repair install via Settings > System > Recovery > Reset this PC (keeping your files) can resolve deep driver corruption that nothing else touches.
Conclusion
Fix #3 (uninstalling and letting Windows reinstall the driver )clears the Code 10 error for the majority of cases. If the error came back right after a Windows Update, Fix #5 (rollback) is the faster path. The registry fix in Fix #8 is a genuine gem for stubborn cases where the driver reinstalls cleanly but Code 10 keeps returning on reboot — that pattern almost always points to leftover filter entries.