USB device not recognized is one of those errors where the problem can be almost anything — the cable, the port, the device, the driver, Windows power management — and the error message itself gives you nothing useful to work with. The yellow exclamation mark in Device Manager or the “USB device not recognized” balloon in the taskbar appears regardless of which specific thing is wrong. For a broader walkthrough, our Complete Guide to Fixing Windows, Browser, and Software Errors is a good next read.
Start with the two-minute physical tests before touching any settings. Try a different USB port on the machine. Try a different USB cable if possible. Try the device on a completely different computer if you have one available. These three tests together tell you within minutes whether the problem is the device itself, the cable, this specific port, or something about Windows on this machine. The answer narrows down the remaining fixes dramatically.
The Physical Tests (Do These First)
Different USB port: Move the device to a different port on the machine — ideally a rear port on a desktop (which connects directly to the motherboard and has more stable power delivery than front panel ports) or a different physical port on a laptop. Some ports fail or become unreliable over time, and swapping the port immediately tells you whether the port is the issue.
Different cable: USB cables fail more often than people expect. Internal wire breaks, loose connectors, and damage from being bent repeatedly all produce “USB device not recognized” without any visible damage. If you have another cable that fits, swap it. This is especially relevant for USB-C and micro-USB connections that get plugged and unplugged frequently.
Different computer: If the device works on another computer, the problem is Windows or the driver on this machine. If it doesn’t work on any computer, the device itself is likely faulty.
Fix 1: Reset the USB Hub in Device Manager
USB hubs — the controller chips that manage groups of ports — can get stuck in an error state where they stop recognizing newly connected devices. Restarting the hub without rebooting the machine often resolves this:
Device Manager (right-click Start → Device Manager) → expand “Universal Serial Bus controllers” → right-click “USB Root Hub” → Disable device → wait 10 seconds → right-click → Enable device. Do this for each Root Hub entry if there are multiple. Reconnect the device after re-enabling.
Alternatively: unplug the device, wait 30 seconds, plug it back in. This forces the port to go through a fresh enumeration cycle without needing Device Manager. Sounds too simple, but it fixes a surprising number of USB not recognized errors caused by the port getting into a bad state during a previous connection attempt.
Fix 2: Update the USB Controller Driver
The USB controller driver handles communication between Windows and all USB ports. An outdated or corrupted driver causes recognition failures across multiple devices and ports. This is especially common after Windows updates that replace the manufacturer’s USB driver with a generic Microsoft version.
Device Manager → Universal Serial Bus controllers → right-click each USB controller entry (there may be several: xHCI Host Controller, USB Host Controller, etc.) → Update driver → Search automatically. If Windows finds nothing useful, check your motherboard or laptop manufacturer’s support page for USB driver downloads specific to your model.
For a complete driver reinstall when updating doesn’t help: right-click the USB controller → Uninstall device → tick “Delete the driver software for this device” → Uninstall → restart. Windows installs a fresh driver automatically on boot.
Fix 3: Disable USB Selective Suspend
Windows power management can cut power to USB ports to save energy — a feature called USB selective suspend. The problem: when the device is connected and Windows decides to suspend the port, the device loses power and Windows may not successfully re-enumerate it when power is restored. The result is a device that works when first connected but disappears after a period of inactivity, or a device that’s never recognized because the port was already suspended when it was connected.
Disable USB selective suspend: Control Panel → Power Options → your current plan → Change plan settings → Change advanced power settings → USB settings → USB selective suspend setting → change to Disabled. Apply and OK.
Also disable it at the device level: Device Manager → Universal Serial Bus controllers → right-click each USB Root Hub → Properties → Power Management → uncheck “Allow the computer to turn off this device to save power.”
Fix 4: Windows Fast Startup Causing the Problem
Windows Fast Startup saves the system state during shutdown to speed up the next boot. The USB device state from the previous session is preserved in that saved state. When Windows resumes, it expects the same USB devices to be present — a device that wasn’t connected when the state was saved, or one that was power-cycled, can trigger USB not recognized because Windows is working from stale connection information.
The test: try a Restart (not Shutdown) before connecting the device. A true restart bypasses Fast Startup and starts fresh. If the device is recognized after a restart but not after a shutdown-then-start, Fast Startup is the cause.
To disable Fast Startup permanently: Control Panel → Power Options → Choose what the power buttons do → Change settings that are currently unavailable → untick “Turn on fast startup” → Save changes. Shutdowns now do a full power cycle rather than a hybrid sleep, and USB state conflicts stop recurring.
Fix 5: Power Delivery for External Drives
USB-powered external hard drives require more current than flash drives or other small peripherals. USB 2.0 ports supply 500mA; USB 3.0 provides 900mA. An external hard drive that’s drawing more power than the port provides — especially as the drive ages and its motor requires more current to spin up — produces USB not recognized or appears briefly then disappears.
Tests: plug the drive into a USB 3.0 port (blue connector inside, or labeled SS) rather than USB 2.0. Try rear ports on a desktop which have more stable power delivery. Use the Y-cable that came with the drive if it has one (draws power from two ports simultaneously). Use a powered USB hub instead of a direct connection. If any of these work when the direct connection doesn’t, power delivery was the issue.
Fix 6: Check Device Manager for Error Codes
When the device appears in Device Manager with a yellow triangle, the specific error code in the device’s Properties tells you exactly what kind of failure occurred — which points directly to the right fix:
| Code | Meaning | Fix |
|---|---|---|
| Code 10 | Device failed to start | Update or reinstall device driver |
| Code 28 | Drivers not installed | Install manufacturer driver manually |
| Code 43 | Device reported a problem (hardware) | Try different port; test on another PC |
| Code 52 | Driver signature verification failed | Check Secure Boot settings; get signed driver |
Code 43 specifically often indicates the device itself has failed rather than a driver or Windows problem — particularly if multiple ports and cables have been tested. Code 52 appears when the driver isn’t digitally signed in a way Windows accepts with Secure Boot enabled.
Fix 7: Check USB 3.0 vs 2.0 Compatibility
USB 3.0 ports are designed to be backward compatible with USB 2.0 devices, but some older devices — particularly those manufactured before USB 3.0 existed — don’t handle the USB 3.0 handshake gracefully. They connect, fail, and produce “USB device not recognized” on 3.0 ports while working fine on 2.0 ports.
If your machine has both USB 2.0 and 3.0 ports (2.0 ports are black inside; 3.0 are blue), try the USB 2.0 port for older devices. Some motherboards also allow disabling USB 3.0 in BIOS for specific controllers if all ports are 3.0 and you need backward compatibility for legacy hardware.
Driver Signature Enforcement and Older Devices
Older industrial peripherals, legacy audio interfaces, and specialty hardware often use drivers written before Microsoft mandated driver signing. On Windows 11 with Secure Boot active, unsigned drivers can’t load — the device appears as unrecognized with error code 52 or 43 and no amount of reinstalling helps because Windows is actively refusing to load the driver.
Options: check whether the manufacturer has released an updated, signed driver (many vendors updated their driver packages specifically for Windows 11). If no signed driver exists, the device may simply not be usable on Windows 11 with Secure Boot without compromising security settings. Test Mode in Windows (which disables driver signature enforcement) is an option for specialist scenarios but isn’t recommended for everyday use.
Our guide on Windows 11 USB recognition generally covers the newer USB-C and Thunderbolt device cases alongside the standard USB-A issues covered here. For external drives specifically that aren’t showing up, our hard drive not showing up guide covers the Disk Management side of drive recognition beyond the driver layer. Microsoft’s USB troubleshooting documentation covers the Device Manager error code reference for all USB-related codes and the USB Diagnostics tool available through the hardware troubleshooter.
USB Debugging With USBView and USBDeview
When standard Device Manager doesn’t show enough detail to diagnose the problem, two free tools provide much more granular USB diagnostics:
USBView (from Microsoft, available as part of Windows SDK or directly downloadable) shows the complete USB device tree including devices that failed enumeration. It shows which USB host controller each port belongs to, what was connected, and what happened during the connection attempt — including error codes from the USB protocol layer that don’t appear in Device Manager.
USBDeview (from NirSoft) lists every USB device ever connected to the machine, including ones currently disconnected. It shows the VID (Vendor ID) and PID (Product ID) for each device, which you can search for driver downloads even when Windows can’t identify the device. If a device is connected but showing as unknown, USBDeview often still captures its identifiers and can help find the correct driver.
Both tools are particularly useful when the standard troubleshooting steps don’t resolve the issue and you need to understand exactly what Windows sees when the device is connected. The VID/PID from USBDeview can be entered directly into the Windows Update Hardware Search tool or searched on the driver manufacturer’s site to find the correct driver for an unknown device.
USB Hub vs Direct Connection
USB hubs — including the hub chips built into laptop docking stations, monitors with built-in USB ports, and keyboard USB pass-through ports — add an additional device management layer between the physical device and Windows. When a device isn’t recognized through a hub but works when connected directly to the laptop, the hub is failing to properly enumerate the device.
Unpowered USB hubs are particularly problematic for power-hungry devices. An unpowered hub draws power from the laptop’s USB port and distributes it among multiple connected devices — with enough devices connected, each gets insufficient power. Powered USB hubs (with their own power adapter) eliminate this by providing full current to each port independently. For docking station USB ports specifically, the docking station firmware sometimes has known bugs with specific device types that are fixed in firmware updates — checking the docking station manufacturer’s support page for firmware updates is worth doing if recognition failures happen consistently through the dock but not directly.
USB Device Not Recognized After Wake from Sleep
Devices that work when the computer starts but stop being recognized after the computer wakes from sleep are experiencing a USB resume failure. Windows has to re-enumerate all USB devices when waking from sleep, and some devices or controllers don’t handle this correctly — particularly when USB selective suspend has put the controller in a deep sleep state.
The fix combines disabling USB selective suspend (Fix 3 above) with also checking the power management settings on the USB root hubs in Device Manager. More specifically, some root hubs have a separate setting for “Allow the computer to turn off this device to save power” that persists even after the global USB selective suspend setting is changed. Go through each USB Root Hub in Device Manager → Properties → Power Management → verify all have the auto-power-off unchecked, not just some of them. Missing even one hub leaves a path for sleep-related recognition failures to recur.
When the Device Appears Briefly Then Disappears
The notification sound occurs, Windows briefly shows the device in Device Manager, then the device disappears within a few seconds — this specific pattern points to either a power delivery failure (the device gets enough power to identify itself but not enough to stay connected) or a driver initialisation failure (the driver loads, encounters an error, and unloads the device).
For power: use a powered hub or try a rear port on a desktop. For driver initialisation: check Event Viewer (Windows Logs → System) immediately after the device disappears. The event log captures the exact error that caused the device to be removed, including the specific driver component that failed, which provides a more direct path to the fix than working through all possibilities systematically. If this sounds familiar, USB Device Keeps Disconnecting is worth a look.
