Fix Device Manager unknown hardware error code 10

Quick answer for advanced users

Open Device Manager, uninstall the unknown device, check 'Delete the driver software for this device', then scan for hardware changes. If that doesn't work, delete the corrupted driver files from C:\Windows\System32\DriverStore\FileRepository manually. Then reboot.

Why this happens

Error Code 10 in Device Manager means Windows can't start the device. The culprit here is almost always a corrupted driver or a driver conflict from a previous install. I've seen this happen after Windows updates, especially on Windows 10 22H2 and Windows 11 23H2. Another common trigger is plugging a device into a USB 3.0 port after using it on USB 2.0 — the driver hash gets misaligned. Don't bother with generic driver updates or third-party driver tools; they rarely help and often make things worse.

Fix steps

Step 1: Identify the unknown device

Open Device Manager (press Win + X, select Device Manager). Look for the yellow triangle. Right-click it and go to Properties. Under the Details tab, select 'Hardware Ids' from the dropdown. Copy the first value — something like USB\VID_8086&PID_1000. This tells us what the device actually is. Write it down.

Step 2: Uninstall the device with driver deletion

Right-click the unknown device, choose 'Uninstall device'. In the popup, check the box 'Delete the driver software for this device'. This is critical — skip this and the corrupted driver lingers. After that, click Action > Scan for hardware changes. If Windows finds the device and installs a clean driver, you're done. If not, move to step 3.

Step 3: Clean the driver store manually

When the automatic reinstall fails, the corrupted driver is still cached. Here's the blunt truth: Windows often keeps bad driver files even after uninstalling. You need to nuke them directly.

Open an elevated Command Prompt (Win + X, select Terminal (Admin)).
Run:
```
pnputil /enum-drivers
```
Look for drivers that match the hardware ID from step 1. They'll have a 'Published Name' like oem123.inf. Copy that name.

Delete the driver:

pnputil /delete-driver oem123.inf /uninstall /force

Then go to C:\Windows\System32\DriverStore\FileRepository and find the folder matching that driver. Delete the entire folder. You might need to take ownership first — right-click, Properties > Security > Advanced. But honestly, pnputil is safer.

Step 4: Reboot and let Windows re-detect

After deleting the driver files, reboot the machine. Let Windows boot fully. Then open Device Manager and click Action > Scan for hardware changes. Windows should now download a fresh driver from Windows Update or use a generic driver. If it still shows Code 10, the hardware itself might be dead — try it on another PC.

Alternative fix: Use DISM and SFC

If the driver store is corrupt beyond a single driver, system file corruption can cause Code 10. Run these in an admin command prompt:

DISM /Online /Cleanup-Image /RestoreHealth

sfc /scannow

This fixes the driver store itself. Then repeat step 2. It's a slow process but I've had it kill the error on stubborn machines.

Prevention tip

To avoid this in the future, never let Windows Update install driver updates automatically. Go to Settings > Windows Update > Advanced options > Additional options > Optional updates. Uncheck any driver updates you don't need. Better yet, use 'Show or hide updates' troubleshooter from Microsoft to block specific driver revisions. And always unplug USB devices before rebooting after a driver update — prevents the hash mismatch I mentioned earlier.