
By Saif Khan | TechFix Radar | Updated: July 2026 | 12 min read
You plug in a phone to charge and Windows answers with a pop-up: “USB device not recognized.” The cable light stays on, but nothing appears in File Explorer. A flash drive gives the same message. So does a mouse that worked yesterday. The good news is that the data on those devices is untouched — the failure is on the PC side. What you need is a diagnosis first, not a guess about which port or driver is to blame.
This error has four common root causes, and each one has a different fix:
- A driver that broke after a Windows update — the USB root hub or host controller driver stops responding. Go to Fix 4.
- Windows power saving cutting the bus — USB Selective Suspend switches ports off and the device never wakes. Go to Fix 5.
- A corrupted USB stack — leftover filter drivers block enumeration entirely. Go to Fix 6.
- Physical damage — a bent pin, a worn port or a failing cable. Go to Fix 7.
💡 Reality check: your files are safe. Windows has lost the connection to the device, not the data on it. The usual suspects are a flaky port, an outdated or corrupted driver, power saving killing the bus, or a damaged USB stack. Match the fix to the symptom instead of trying everything.
⚡ TL;DR — top 3 quick actions
- Unplug the device, wait five seconds, and replug it firmly into a different port — directly on the machine, not through a hub.
- Open Device Manager and look for the yellow exclamation mark under
Universal Serial Bus controllers. Write down the exact error code. - Run the built-in Windows hardware troubleshooter.
Diagnose the failure before you fix it
Windows tells two distinct stories when a USB device is not recognized. In the first, Device Manager shows an Unknown USB Device (Device Descriptor Request Failed) entry under Universal Serial Bus controllers with a yellow exclamation mark. That points to a driver or handshake failure on the PC side. In the second, the device icon flickers in the system tray or File Explorer while it stays plugged in — that is usually a power or enumeration glitch rather than a missing driver.
Open Device Manager with Win + X and expand Universal Serial Bus controllers. Look for a yellow exclamation mark, a greyed-out entry with no drive letter, or a generic USB Mass Storage Device showing This device cannot start. (Code 43) on its Properties tab. If you see an error code, that code is your diagnosis. If the device simply appears and vanishes, the problem is power or the port itself.
🔍 Device Manager shows an error code
Code 43— Windows stopped the device after a controller fault.Code 10— the driver failed to load.Code 28— no driver is installed for the device.Device Descriptor Request Failed— the handshake never completed.- Start at Fix 2.
Table of contents
- Re-plug the cable or switch ports
- Identify the exact error code in Device Manager
- Run the built-in Windows hardware troubleshooter
- Update or reinstall the USB controller drivers
- Disable USB Selective Suspend
- Clear corrupted USB filter drivers
- Check for hardware damage and test on another PC
- Quick reference — all 7 fixes
- Symptom to fix map
- What each error code really means
- The 60-second triage
- Frequently asked questions
The 7 fixes, in the order that works
1. Re-plug the cable or switch ports
HIGH IMPACT3 minNO DATA LOSSIf the device icon flickers, or nothing appears while the cable light is on, the plug may not be seating properly or the port may be delivering uneven power. A clean reseat often restores enumeration without touching a single driver.
Steps
- Unplug the device and wait five seconds.
- Shine a flashlight into both the plug and the port. Look for lint, dust or bent pins. Clear debris with a wooden toothpick — never metal, and never while the machine is on.
- Plug the device firmly into a different port. On a desktop, use a rear port wired directly to the motherboard. On a laptop, use a port on the chassis itself.
- Bypass any hub or dock. Many inexpensive hubs cut power during enumeration. If the device works on a direct port, the hub is your answer.
- Try a different cable. Charge-only cables carry no data lines at all, and a worn cable is one of the most common causes of this error.
Note: port colour matters. A blue port is USB 3.x, a black one is usually USB 2.0. Some drives need the extra power a 3.x port supplies and will fail silently on a 2.0 port.
✅ Verify it worked: the device appears in File Explorer with a drive letter, or as a working input device, and stays connected for a full minute without flickering. If it still drops, go to Fix 2.
2. Identify the exact error code in Device Manager
HIGH IMPACT3 minNO DATA LOSSThis step does not fix anything on its own — it tells you which of the remaining fixes to run. Guessing wastes far more time than three minutes in Device Manager.
Steps
- Press
Win + Xand choose Device Manager. - Expand
Universal Serial Bus controllers. Also checkDisk drivesandOther devices. - Find the entry with a yellow exclamation mark. Common names are Unknown USB Device, USB Mass Storage Device, and USB Input Device.
- Right-click it, choose Properties, and read the Device status box on the General tab. Write down the exact wording and code number.
- If the entry is greyed out, right-click and choose Enable device — a device disabled earlier will produce exactly this symptom.
- Unplug the device and watch the list. The entry that disappears is yours.
Note: if no new entry appears at all when you plug the device in, Windows is not detecting it electrically. That points at the port, the cable or the device — skip ahead to Fix 7.
✅ Verify it worked: you now have a specific code. Use the code table below to pick the right fix.
3. Run the built-in Windows hardware troubleshooter
MEDIUM IMPACT5 minNO DATA LOSSThe hardware troubleshooter can reset the USB hub, reload the driver stack and re-enumerate devices without any manual editing. It regularly clears transient failures that look like driver corruption.
Steps
- Press
Win + R, typemsdt.exe -id DeviceDiagnosticand press Enter. On Windows 11 the Hardware and Devices troubleshooter is no longer listed in Settings, so this command is the reliable way to reach it. - Click Advanced and tick Apply repairs automatically, then click Next.
- Let the scan finish. If it offers a fix, apply it.
- Reboot if prompted, then reconnect the device.
- If nothing is found, open Settings → Windows Update → Advanced options → Optional updates and install any driver updates listed there.
Note: the troubleshooter cannot repair firmware-level faults or physically damaged ports. If it reports that it could not identify the problem, move on to Fix 4.
✅ Verify it worked: the device appears normally and survives a reboot. If the error returns after sleep, the cause is power saving — go to Fix 5.
4. Update or reinstall the USB controller drivers
HIGH IMPACT10 minNO DATA LOSSWhen Device Manager reports Code 43 or Device Descriptor Request Failed, a corrupted host controller or root hub driver is the most likely cause. Reinstalling the stack lets Windows rebuild it cleanly on the next boot.
Steps
- Safely eject anything you are still using, then open Device Manager.
- Expand
Universal Serial Bus controllers. You will see entries such as USB Root Hub, Generic USB Hub and a host controller named after your chipset. - Right-click the faulty entry and choose Update driver → Search automatically for drivers first. This is the safest option.
- If that changes nothing, right-click the same entry and choose Uninstall device. Do not tick “delete the driver software” unless the automatic reinstall has already failed once.
- Reboot. Windows re-detects the controller and installs its default driver automatically.
- Still failing? Download the chipset driver package directly from your laptop or motherboard manufacturer's own support page, using your exact model number. Avoid third-party driver-updater tools entirely.
⚠️ Warning: uninstalling a USB controller disconnects everything on that bus — including your keyboard and mouse if they are USB. Have a PS/2 keyboard or a laptop's built-in keyboard available, and make sure no file transfer is in progress.
✅ Verify it worked: the yellow mark is gone, the device is listed under Disk drives or Human Interface Devices, and it survives a sleep cycle. If the mark returns after every reboot, continue to Fix 6.
5. Disable USB Selective Suspend
MEDIUM IMPACT5 minNO DATA LOSSWindows powers down idle USB ports to save battery. On some machines it powers them down too aggressively, and a device that was working drops into an unrecognised state. This is the classic cause when the failure only happens on battery, or only after the laptop wakes from sleep.
Steps
- Press
Win + R, typepowercfg.cpland press Enter. - Next to your active plan, click Change plan settings → Change advanced power settings.
- Expand USB settings → USB selective suspend setting and set both On battery and Plugged in to Disabled. Click Apply.
- Now stop the driver doing the same thing: in Device Manager, open each USB Root Hub, go to the Power Management tab, and untick Allow the computer to turn off this device to save power. Repeat for every root hub.
- Restart and reconnect the device.
⚠️ Warning: keeping USB ports powered continuously increases battery drain and runs the laptop slightly warmer. If the device that was dropping is no longer connected, it is worth switching these settings back on.
✅ Verify it worked: leave the device connected and let the machine sleep, then wake it. If the device is still present and the yellow mark has not returned, selective suspend was the cause.
6. Clear corrupted USB filter drivers
HIGH IMPACT10 minRISK — BACK UP FIRSTBurner software, old phone suites and virtual-drive tools leave behind filter drivers that sit between Windows and every USB storage device. When one of them breaks, drives stop mounting no matter how many times you reinstall the controller. Removing those two registry values is the standard repair — and it is far more surgical than the “delete everything” advice that circulates online.
⚠️ Warning: registry editing can break Windows. Export a backup before you change anything, and change only the two values named below. Do not delete the parent key, and do not delete other values inside it. Ignore any guide that tells you to remove every key under a GUID, or to run a bulk driver-removal command — that strips unrelated drivers such as Wi-Fi, graphics and printers.
Steps
- Press
Win + R, typeregeditand press Enter. - Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000} - Right-click that key, choose Export, and save a backup to your Desktop.
- In the right-hand pane, look for values named UpperFilters and LowerFilters. If either exists, delete only those two. If neither exists, this is not your problem — close the editor and go to Fix 7.
- Close the editor and restart the PC. Windows rebuilds the filter chain during boot.
- Optional, and safer than registry work: open PowerShell as Administrator and run
sfc /scannow, thenDISM /Online /Cleanup-Image /RestoreHealthto repair damaged system files.
✅ Verify it worked: the device mounts and stays mounted through a reboot. Copy a small test file to and from it before trusting it with anything important.
7. Check for hardware damage and test on another PC
LAST RESORT10 minNO DATA LOSSIf the software fixes have all failed, the fault is physical. The goal here is not to repair anything — it is to work out which of the three parts is broken: the port, the cable, or the device.
Steps
- Test the device elsewhere. Plug it into a completely different computer. If it works there, your PC's port or driver stack is the problem.
- Test a different device in the same port. If that one also fails, the port is at fault.
- Swap the cable. Use a cable you know carries data, not a charge-only cable.
- Inspect the port. With the machine off, look for a bent or flattened centre tongue, discolouration, or debris packed at the back.
- Work out what is worth fixing. If only one port is dead and the others work, a cheap powered hub is usually the sensible answer. A soldered-port repair is rarely worth it on an older laptop.
⚠️ Warning: never force a plug. A bent pin inside a laptop port can turn a five-minute annoyance into a board-level repair. If the plug does not slide in easily, it is oriented wrong or the port is already damaged.
✅ Verify it worked: the device works on the second machine — confirming your PC as the fault — or it fails everywhere, confirming the device itself. Either way you now know what to replace.
Quick reference — all 7 fixes
| # | Fix | Impact | Time | Best for |
|---|---|---|---|---|
| 1 | Re-plug or switch ports | High | 3 min | Nothing detected, or the device flickers |
| 2 | Identify the error code | High | 3 min | A yellow exclamation mark is showing |
| 3 | Hardware troubleshooter | Medium | 5 min | Detection problems with no clear code |
| 4 | Reinstall USB drivers | High | 10 min | Code 43, or failure after a Windows update |
| 5 | Disable Selective Suspend | Medium | 5 min | Drops on battery or after sleep |
| 6 | Clear USB filter drivers | High | 10 min | No drive mounts at all, on any port |
| 7 | Hardware check | Last resort | 10 min | Fails across multiple ports or machines |
Symptom to fix map
| What you see | Most likely cause | Matching fix |
|---|---|---|
| Error appeared right after a Windows update | Host controller driver replaced with a faulty version | Fix 4 |
| Device drops every few minutes on battery | USB Selective Suspend cutting bus power | Fix 5 |
| No USB storage mounts on any port | Corrupted upper or lower filter drivers | Fix 6 |
| Works on one port, dead on another | Failed port or an underpowered hub | Fix 1, then Fix 7 |
| Device light is on, but Explorer shows nothing | Drive is online but has no letter assigned | See the note below |
| Fails on every computer you try | The device or its cable has failed | Fix 7 |
The missing drive letter trap: if the device powers up but never shows in File Explorer, press Win + R, run diskmgmt.msc, and look for the disk there. If it appears as Offline, right-click and choose Online. If it has no letter, right-click the partition and choose Change Drive Letter and Paths. Neither action erases data. Never accept a Windows prompt to format the drive if the files still matter to you.
What each error code really means
Underneath, this error is a failed handshake between three layers: the device, the host controller on your motherboard, and Windows' USB driver stack. Most people blame the device, but the controller can lock up after a driver crash or a power glitch, and once it stops acknowledging the device's descriptors Windows reports a generic failure with no useful detail.
Power budget is the other frequent culprit. Every USB port supplies a limited amount of current, and a bus-powered drive that needs more than the port can deliver will brown out during startup — the drive spins, the light comes on, but the handshake never completes. That is why the same drive can work on one machine and fail on another, and why an externally powered hub often solves a problem that no amount of driver work will.
| Code | What it means | Where to go |
|---|---|---|
Code 10 | The driver failed to load, or the device firmware is not responding. | Fix 4 |
Code 28 | No driver is installed for this device. | Fix 4 |
Code 31 | Generic failure, often a power delivery mismatch. | Fix 5 |
Code 43 | Windows stopped the device after the controller reported a fault. | Fix 4, then Fix 6 |
Descriptor Request Failed | The device never completed its introduction to Windows. | Fix 1, then Fix 4 |
One more place to look: in Device Manager, open View → Show hidden devices. Greyed-out duplicate controller entries are remnants of devices that were removed badly. Uninstalling the greyed-out duplicates and rebooting sometimes clears a fault that nothing else touches.
Stopping it from coming back
Three habits prevent most repeat failures. Keep your chipset and BIOS updated through the manufacturer's own support tool rather than a third-party updater. Always eject removable drives properly instead of pulling them out mid-write — an interrupted write is a common route to a corrupted partition table. And if you rely on a hub, use a powered one; the cheapest bus-powered hubs cause more USB faults than any driver ever will.
The 60-second triage
- Does anything at all appear in Device Manager when you plug it in? No — go to Fix 7. Yes — continue.
- Read the error code.
Code 43orCode 10→ Fix 4.Code 31→ Fix 5. - Does it show in Disk Management but not File Explorer? Bring it online or assign a drive letter — the port is fine.
- Does it only fail on battery or after sleep? Go straight to Fix 5.
- Does no USB storage work at all, on any port? Go to Fix 6.
Frequently asked questions
Will any of this erase the data on my drive?
No. Fixes 1 to 5 and 7 do not touch the contents of the device at all. Fix 6 changes Windows' own settings, not your files. The only real danger is accepting a Windows prompt that offers to format the drive — always decline that if the files matter.
Why does my phone charge but never appear as a drive?
Android phones default to charge-only mode. Unlock the phone, pull down the notification shade, tap the USB notification, and choose File transfer. On an iPhone, unlock it and tap Trust when prompted.
Why does the same flash drive work on one PC but not another?
Usually the port. A USB 2.0 port supplies less current than a USB 3.x port, and a drive near the edge of its power budget will fail on the weaker one. Try a blue port, a shorter cable, or a powered hub.
Should I use a driver updater tool?
No. They frequently install drivers that do not match your hardware and make USB problems worse. Use Windows Update and your manufacturer's own support page instead.
Is it safe to delete registry keys to fix USB?
Only the two named in Fix 6, and only after exporting a backup. Guides that tell you to delete everything under a GUID key, or to bulk-remove drivers with a single command, can leave you without Wi-Fi, sound or graphics. Do not follow them.
My USB hub stopped working after I plugged in an external drive. Why?
The drive is drawing more current than the hub can supply, which browns out every port on it. Use a hub with its own power adapter, or connect the drive directly to the computer.
📌 Still stuck?
TechFix Radar has step-by-step fixes for Windows, laptops, Android and iPhone — written to be followed, not skimmed.
Start here Free tools