“USB device not recognized” is Windows telling you that something plugged into a port failed to identify itself. That something could be the device, the cable, the port, the port’s power, or the driver stack — and the error message won’t tell you which. The fix is a process of elimination, and the order matters: test the cheap, external variables first, because reinstalling USB controller drivers for a dead cable wastes an afternoon.

Keep one principle in mind: change one thing at a time and retest. If you swap the cable, change ports, and reinstall drivers all at once, you’ll never know what actually fixed it — and you’ll be helpless the next time it happens. Work through the sections below in sequence.

Why this happens

  • Faulty or charge-only cable: The cable lacks data lines or has a broken data wire, so the device can’t complete enumeration.
  • Underpowered port: The device draws more current than the port provides, especially on unpowered hubs or with multiple devices attached.
  • USB Selective Suspend: Windows suspends the port to save power and the device fails to wake, appearing as unrecognized.
  • Corrupted USB controller drivers: The USB host controller or root hub driver is damaged, breaking enumeration for every device on that controller.
  • Device firmware fault: The peripheral itself fails to present its descriptor, often after a bad firmware update on the device.
  • Dirty or damaged port: Lint, bent pins, or corrosion in the port prevent proper contact on the data pins.
  • Windows fast startup state: A corrupted USB stack persists across hybrid shutdowns, so the error survives reboots.
  • Conflicting filter drivers: Old phone-sync tools, virtualization USB filters, or security software intercept USB traffic and break enumeration.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Isolate the device, cable, and port

Plug the device into a different USB port on the laptop — try both USB-A and USB-C if available, and try a port on the opposite side of the chassis (they often sit on different controllers). Then swap the cable for a known-good data cable. Finally, test the device on a different computer. If it works elsewhere, your laptop is the problem; if it fails everywhere, the device or its cable is dead and no driver fix will help.

  1. Try a different USB port, ideally on the other side of the laptop.
  2. Swap in a known-good cable that supports data.
  3. Test the device on a second computer.
  4. Try a different device in the suspect port.
  5. Record which combinations work to isolate the fault.

Fix 2: Power-cycle the USB hardware

Unplug all USB devices, shut the laptop down completely (not sleep, not hybrid shutdown — hold Shift while clicking Shut down to force a full shutdown), unplug the charger, and wait 60 seconds. This drains residual power and resets the USB controllers at the hardware level. Power on, let Windows settle, then plug in only the problem device. This clears a surprising number of “not recognized” errors caused by stuck controller state.

  1. Unplug every USB device from the laptop.
  2. Hold Shift, click Shut down, then unplug the charger.
  3. Wait a full 60 seconds.
  4. Power on and let Windows finish booting.
  5. Connect only the problem device and test.

Fix 3: Disable USB Selective Suspend

Open Power Options, edit your active plan, and under USB settings, set “USB selective suspend setting” to Disabled for both battery and plugged-in states. This stops Windows from powering down idle ports — the source of many intermittent recognition failures. Our dedicated walkthrough covers turning off USB Selective Suspend in detail. Retest the device over a day of normal use, including after sleep/wake cycles, which is when suspend-related failures usually appear.

  1. Open Power Options and edit the active plan.
  2. Expand USB settings, then USB selective suspend setting.
  3. Set it to Disabled on battery and plugged in.
  4. Apply and reboot.
  5. Test the device, especially after sleep/wake cycles.

Fix 4: Reinstall the USB controller drivers

Open Device Manager and expand “Universal Serial Bus controllers.” Right-click each “USB Root Hub” and “USB Host Controller” entry and choose Uninstall device — do this for all of them, then reboot. Windows will redetect and reinstall fresh controller drivers at startup. Don’t worry: your keyboard and mouse will stop working during this, so have the steps memorized or use a PS/2-era backup plan of navigating by memory. If a specific device shows Code 43, uninstall that device entry too, with its driver removed. Microsoft’s Windows support hub documents Device Manager recovery steps.

  1. Open Device Manager and expand Universal Serial Bus controllers.
  2. Uninstall every USB Root Hub and Host Controller entry.
  3. If the device shows Code 43, uninstall it with driver removed.
  4. Reboot and let Windows reinstall the controllers.
  5. Reconnect the device and check recognition.

Fix 5: Inspect and clean the physical port

Power off the laptop and examine the suspect port with a flashlight. Look for lint packed in the bottom (extremely common), bent pins, or green corrosion. Use a wooden toothpick or plastic pick — never metal — to gently remove debris. For USB-C ports, check that the internal tongue isn’t cracked. If one port is physically damaged but others work, you have your answer; USB ports can be replaced but it is board-level work. For USB-C-specific display and data issues, see our USB-C charging troubleshooting .

  1. Power off the laptop completely.
  2. Inspect the port with a flashlight for lint, bent pins, corrosion.
  3. Remove debris with a wooden toothpick or plastic pick.
  4. Check USB-C port tongues for cracks.
  5. Retest; consider repair if a port is physically damaged.

Fix 6: Remove conflicting USB filter drivers

Old phone management suites, some VPN clients, and virtualization tools install USB filter drivers that intercept device enumeration. In Device Manager, check the device’s Properties, Details tab, and look at driver providers. Uninstall software you no longer use that touches USB — old Samsung Kies, HTC Sync, or similar relics are classic offenders. You can also use the pnputil command to list third-party driver packages and remove stale ones, but research each package before deleting.

  1. Uninstall unused phone-sync and virtualization USB tools.
  2. In Device Manager, inspect the device’s driver provider details.
  3. Run pnputil /enum-drivers in an elevated prompt to list third-party drivers.
  4. Remove stale USB filter packages carefully.
  5. Reboot and retest the device.

Fix 7: Update the chipset driver and BIOS

The USB controllers are part of the chipset, so an outdated chipset driver can cause enumeration failures across all ports. Download the latest chipset driver from your laptop maker — Intel’s Driver & Support Assistant can detect the right package automatically. While you’re at it, check whether the maker has a BIOS update mentioning USB stability for your model, and apply it with the charger connected. After updating, retest every port with the problem device.

  1. Download the latest chipset driver for your exact model.
  2. Or run Intel’s Driver & Support Assistant to detect it.
  3. Install the chipset driver and reboot.
  4. Check for BIOS updates mentioning USB fixes; apply with charger connected.
  5. Retest all ports with the problem device.

Closing

USB recognition failures look mysterious but surrender to methodical elimination: device, cable, port, power, driver — in that order. Most cases resolve at the cable or the Selective Suspend setting, and the rest usually yield to a controller driver reinstall. When a device fails on every computer with every cable, believe the evidence: the device itself is done, and no amount of driver work will bring it back.

Frequently asked questions

Why does Windows keep saying USB device not recognized for a device that used to work?
The most common cause is a driver or power-state problem rather than sudden hardware death. USB Selective Suspend may be cutting power to the port, the USB controller driver may be corrupted, or a Windows update changed the driver. Test the device on another computer first: if it works there, the fault is in your laptop’s ports, drivers, or power settings.
What does error code 43 mean for a USB device?
Code 43 means Windows stopped the device because it reported a problem. For USB, this usually indicates a corrupted driver, a power issue on the port, or the device itself failing to enumerate. Uninstall the device with its driver removed, unplug it, reboot, and reconnect. If Code 43 persists on multiple computers, the device hardware is likely failing.
Can a bad cable cause the USB device not recognized error?
Absolutely — cables are one of the top causes. Charge-only cables lack data wires entirely, and damaged data cables cause enumeration failures that Windows reports as unrecognized devices. Always test with a known-good data cable before troubleshooting drivers. For USB-C, confirm the cable actually supports data, not just charging.
Should I disable USB Selective Suspend?
Yes, as a diagnostic step and often as a permanent fix for flaky devices. Selective Suspend powers down idle USB ports, and some devices never wake properly. Disabling it in Power Options eliminates an entire class of intermittent recognition failures. The battery cost is negligible on most modern laptops.