Fix Windows 11 USB Not Recognized Problem
When Windows 11 fails to recognize a USB device, the cause can range from a simple driver glitch to a power management setting or a hardware fault. This guide walks through the fixes in order, from the quickest to the most thorough, so you can get your device working again.
Start With the Quick Checks
Before diving into settings, rule out the obvious:
Read also: Windows 11 Best Settings for Gaming: FPS Boost Guide
- Try a different USB port, ideally one directly on the motherboard (rear ports on a desktop) rather than a front panel or hub.
- Test the device on another PC to confirm the device itself isn’t dead.
- Remove USB hubs and connect the device directly.
- Restart the PC with the device unplugged, then plug it in after Windows loads.
If the device works elsewhere but not on this PC, the problem is almost certainly software or driver related, which the steps below address.
Fix 1: Reinstall USB Drivers in Device Manager
A corrupted driver is the most common cause. Refresh it:
- Right-click Start and open Device Manager.
- Expand Universal Serial Bus controllers.
- Look for any device with a yellow warning triangle, or for “Unknown USB Device”.
- Right-click it and choose Uninstall device.
- Then click Action > Scan for hardware changes, or simply reboot. Windows reinstalls the driver automatically.
You can also right-click the entry and select Update driver to check for a newer version.
Fix 2: Disable USB Selective Suspend
Windows power management can switch off USB ports to save energy and then fail to wake them. Turn this off:
- Open Control Panel > Hardware and Sound > Power Options.
- Click Change plan settings next to your active plan, then Change advanced power settings.
- Expand USB settings > USB selective suspend setting and set it to Disabled.
- Apply and reboot.
Additionally, in Device Manager, open each USB Root Hub, go to the Power Management tab, and uncheck “Allow the computer to turn off this device to save power.”
Fix 3: Run the Hardware Troubleshooter and Check Disk Management
If the device is a storage drive that powers on but doesn’t appear in File Explorer, it may simply lack a drive letter. Open Disk Management (right-click Start), find the drive, and if it shows as healthy but unlettered, right-click it and choose Change Drive Letter and Paths to assign one. If it shows as “Unallocated,” the drive may need to be initialized or formatted (which erases data). You can also run the built-in troubleshooter from an elevated Command Prompt with msdt.exe -id DeviceDiagnostic.
Fix 4: Update Chipset Drivers and Windows
Outdated motherboard chipset drivers often cause USB issues after a Windows upgrade. Visit your PC or motherboard manufacturer’s support page and download the latest chipset and USB controller drivers for your exact model. Also install pending Windows updates via Settings > Windows Update, since Microsoft regularly ships USB stack fixes. As a final step, scanning for corrupted system files with sfc /scannow in an elevated Command Prompt can repair underlying issues that affect device detection.
Frequently Asked Questions
Why does my USB device work on another PC but not this one?
That points to a software or driver problem on your PC rather than a faulty device. Reinstall the USB drivers in Device Manager and disable USB selective suspend to resolve it.
My USB drive powers on but doesn’t show in File Explorer. Why?
It likely has no drive letter assigned or needs initializing. Open Disk Management; if the drive is healthy, assign a letter via Change Drive Letter and Paths. If it shows as unallocated, it may require formatting.
What is USB selective suspend and should I disable it?
It’s a power-saving feature that turns off idle USB ports and sometimes fails to wake them. Disabling it in Power Options often fixes devices that randomly disconnect or aren’t recognized.
How do I fix “Unknown USB Device” errors?
In Device Manager, uninstall the unknown device, then scan for hardware changes or reboot so Windows reinstalls the driver. Updating chipset drivers and running sfc /scannow helps if it persists.
