USB Device Not Recognized (Error Code 43) on Windows 11: A Real Fix
Code 43 means Windows stopped a USB device that reported problems. Here is how to tell hardware faults from driver and power-setting causes.
When you plug in a flash drive, phone, or webcam on Windows 11 and get "USB device not recognized" with Code 43 in Device Manager, it means Windows has stopped the device because it reported a problem. The trick is figuring out whether the fault is the device, the cable, the driver, or a power setting, because each needs a different fix, and the order you test them in saves a lot of wasted effort.
Quick answer
Code 43 means Windows stopped the device because its firmware or driver reported a fault. Test in order: rule out hardware first by swapping the cable, removing any hub or dock, and trying a rear port, since a device that also fails on a second PC is the device, not Windows. If the hardware is fine, uninstall the device in Device Manager and reboot to reinstall the driver, then do a full power drain of the PC. The most common software cause is USB selective suspend, so disable it in Power Options. Finally, install pending Windows and chipset updates.
Key takeaways
- Code 43 reads "Windows has stopped this device because it has reported problems", a deliberately vague signal from either the firmware or the driver.
- Rule out hardware first: cable, hub, and port. A device that also fails on a second PC is the device, not Windows.
- USB selective suspend is a frequent cause, a port powers down an idle device and fails to wake it.
- A full power-drain of the USB controllers clears stuck states that a normal restart won't.
What Code 43 really means
In Device Manager, Code 43 reads: "Windows has stopped this device because it has reported problems." That message is deliberately vague. The device firmware or the driver signaled a fault, and Windows shut the port down to protect the system. Common triggers are driver corruption, a flaky cable, aggressive USB power-saving, a missing chipset update, or a genuinely failing device or port.
Use the clue you have to jump to the likely cause and fix:
| Clue | Likely cause | Fix |
|---|---|---|
| Fails on a second PC too | The device, cable, or enclosure | Replace the cable or the device |
| Works on rear port, not front | Underpowered front header or hub | Use a port wired to the motherboard |
| Drops out after sitting idle | USB selective suspend | Disable selective suspend |
| One controller has a yellow triangle | Corrupt USB driver | Uninstall the device and reboot |
| Every port shows Code 43 | Missing or buggy chipset driver | Install chipset and Windows updates |
| Several devices fail behind a dock | Dock power budget or fault | Test devices directly on the PC |
Step 1: Isolate hardware before touching software
Spend two minutes ruling out physical causes, it saves a lot of wasted driver fiddling.
- Unplug the device, wait 10 to 15 seconds, and reconnect it firmly into a port directly on the PC.
- Remove any hub, dock, USB-C adapter, or extension cable from the chain and connect the device directly.
- Swap in a known-good data cable, ideally the original. Many cheap cables are charge-only and carry no data.
- Try a different port, preferably one on the rear of a desktop (those are wired directly to the motherboard).
- If you can, plug the device into a second PC.
Tip
If the device fails on a second computer too, the problem is the device, cable, or its enclosure, not Windows. Stop troubleshooting the PC.
Step 2: Reinstall the USB driver
If the hardware checks out, the driver is the next suspect.
- Right-click Start and open Device Manager.
- Expand Universal Serial Bus controllers and look for any entry with a yellow warning triangle.
- Right-click the faulty device and choose Uninstall device.
- Restart the PC. Windows reinstalls the USB stack automatically on boot.
If a specific device (not a generic controller) shows Code 43, also try Update driver, then "Search automatically for drivers." For phones and specialized hardware, install the manufacturer's current driver package. This uninstall-and-reboot pattern is the same one that revives a missing audio device or a Bluetooth adapter broken by an update.
Step 3: Power-cycle the USB controllers
A full power drain clears stuck controller states that a normal restart does not.
- Shut the PC down completely.
- Unplug it from power. On a laptop, also disconnect the charger.
- Wait about a minute, then press and hold the power button for 15 seconds to discharge residual power.
- Power back on and reconnect the device.
Step 4: Disable USB selective suspend
USB selective suspend lets Windows power down idle ports to save energy. It is a frequent Code 43 cause because a port sometimes fails to wake the device back up. Microsoft documents two places to turn it off.
Through Power Options
- Open Control Panel, then Power Options.
- Click Change plan settings for your active plan, then Change advanced power settings.
- Expand USB settings, then USB selective suspend setting.
- Set it to Disabled for both On battery and Plugged in, then click OK.
Through Device Manager
- In Device Manager, expand Universal Serial Bus controllers.
- Right-click a USB Root Hub and choose Properties.
- On the Power Management tab, uncheck "Allow the computer to turn off this device to save power."
- Click OK and repeat for every USB Root Hub listed.
Warning
On laptops, disabling selective suspend slightly increases idle battery drain. That is a fair trade if it stops a device dropping out, but re-enable it later if the real fix turns out to be elsewhere.
Step 5: Check for Windows and chipset updates
A missing or buggy chipset driver can produce Code 43 across every port. Go to Settings > Windows Update and install everything pending, including optional driver updates under Advanced options > Optional updates. For desktops and many laptops, also grab the latest chipset driver from the motherboard or PC maker's support page. If updates themselves are failing, our guide to Windows 11 update error 0x800f0922 covers the most common 2026 blocker.
What to do right now
Run the checks in this order so you do not waste time on driver fixes for a hardware fault:
- Swap the cable for a known-good data cable, remove any hub or dock, and try a rear port on a desktop.
- Plug the device into a second PC. If it still fails, the device or cable is the problem, not Windows.
- In Device Manager, uninstall the faulty USB entry and reboot so Windows reinstalls the stack.
- Do a full power drain: shut down, unplug, hold the power button 15 seconds, then power back on.
- Disable USB selective suspend in both Power Options and each USB Root Hub's Power Management tab.
- Install all pending Windows updates plus the latest chipset driver from your PC or motherboard maker.
Why the order saves you time
The reason hardware comes first is simple: no amount of driver reinstalling, power-cycling, or update-chasing will fix a charge-only cable or a dying device. People routinely spend an hour reinstalling drivers for a Code 43 that was a frayed cable all along. The second-PC test is the cleanest single check you can run, because it isolates the variable completely. If the device works elsewhere, you know with certainty the fault is on this PC and the later software steps are worth your time. If it fails everywhere, you stop troubleshooting Windows entirely and replace the cable or the device. Spending two minutes on that test up front is the difference between a quick fix and an afternoon lost.
Frequently asked questions
Does Code 43 mean my USB device is dead?
Not always, but it can. Code 43 is the device or driver reporting a fault. If the same device fails on a second computer with the original cable, it is genuinely failing. If it works elsewhere, the cause is the PC's driver, power settings, or a specific port.
Why does the same device work on one port but not another?
Ports differ in power delivery and which controller they hang off. A rear desktop port wired straight to the motherboard is more reliable than a front-panel or hub port. A failing front-panel header or an overloaded hub can trigger Code 43 on one port while another works fine.
Will disabling USB selective suspend hurt my laptop battery?
Only slightly. It keeps idle USB ports powered, which adds a small amount of idle drain. If turning it off fixes a dropping device, the trade is worth it; if it makes no difference, re-enable it to reclaim the battery life.
I plugged in a USB-C dock and several devices show Code 43, what's going on?
A dock concentrates many devices behind one controller and one power budget. An underpowered or faulty dock can throw Code 43 across everything attached. Test the devices directly on the PC; if they work, the dock or its power supply is the problem.
Putting it together
Work in order: hardware first, then driver reinstall, then a hard power-cycle, then selective suspend, then updates. That sequence separates a dying cable or port (which no driver fix will solve) from the software and power causes that the later steps actually address. In most cases the device is recognized again well before you reach the last step.
