USB Code 43: What It Means and How to Fix It

USB Code 43 means Windows has stopped the device because it reported a hardware problem, and the full error message reads “Windows has stopped this device because it has reported a problem. (Code 43)” in Device Manager. The fix usually starts with unplugging the device, restarting the PC, and reseating the connection, but if that fails you need to update or roll back the driver, check for a failing USB port, or replace the cable or device itself.

What Code 43 Actually Means

Code 43 is one of several error codes Windows assigns to a device in Device Manager when the hardware fails to start correctly. Unlike a driver-specific error like Code 28 (no driver installed), Code 43 is generic: it means the device sent a signal to Windows that it cannot operate, or the driver reported a problem that Windows could not resolve. The error appears on USB devices, graphics cards, internal drives, and webcams, but it is most common on USB peripherals because of the many variables involved—cables, ports, power delivery, and drivers.

When you see Code 43, the device is not necessarily dead. The error can be triggered by a loose connection, a power management setting, a corrupted driver, or a conflict between two drivers. Windows marks the device with a yellow triangle in Device Manager and disables it until you intervene.

Why USB Devices Trigger Code 43

USB devices rely on a handshake between the hardware, the USB controller, and the operating system driver. When you plug in a device, the controller enumerates it—assigns an address, reads its descriptor, and loads the matching driver. If any step fails, Windows reports a problem. Code 43 specifically appears when the device descriptor request fails, meaning the device did not respond with the expected identification data.

Common causes include:

A damaged or low-quality USB cable that drops data lines
A front-panel USB port with a loose internal connection to the motherboard
Power management settings that put the USB port to sleep
Outdated, corrupted, or incompatible drivers
A device that draws more power than the port can supply
Physical damage to the device’s USB connector

The error is more frequent on USB 3.0 ports than USB 2.0 because the higher data rate is more sensitive to signal quality and cable shielding.

How to Fix Code 43: Step-by-Step

Work through these fixes in order. Most people resolve the issue with the first two steps.

Unplug the device and restart your PC. This clears the USB controller’s state and forces a fresh enumeration. Leave the device unplugged for at least 30 seconds.
Plug the device into a different USB port. Prefer a port directly on the back of the motherboard rather than a front-panel or hub port. If it works on one port but not another, the port is the problem.
Try a different cable. USB cables fail internally without visible damage. Use a short, high-quality cable—long or thin cables cause voltage drop and signal degradation.
Update the driver. Open Device Manager, right-click the device, select Update driver, then Search automatically for drivers. If Windows finds nothing, visit the device manufacturer’s website and download the latest driver manually.
Roll back the driver. If the error started after a Windows update or driver update, open Device Manager, right-click the device, select Properties, go to the Driver tab, and click Roll Back Driver if the option is available.
Disable USB power management. Open Device Manager, expand Universal Serial Bus controllers, right-click each USB Root Hub and Host Controller, select Properties, go to Power Management, and uncheck Allow the computer to turn off this device to save power.
Uninstall the device and rescan. Right-click the device in Device Manager, select Uninstall device, then click Action and Scan for hardware changes. Windows will reinstall the driver from its cache.
Test the device on another computer. If it fails there too, the hardware is faulty and needs repair or replacement.

What to Do If the Fixes Don’t Work

If the device still shows Code 43 after trying every step, the problem is likely physical. Check the device’s connector for bent pins, corrosion, or debris. For devices with removable batteries, remove and reinsert them. For internal devices like graphics cards, reseat the card in its slot and reconnect the power cables.

You can also check the Windows Event Viewer for more detail. Press Windows + R, type eventvwr.msc, and look under Windows Logs > System for events with the source Kernel-PnP around the time you plugged in the device. The event details may mention a specific error code that narrows down the cause.

If the device works on another computer, the problem is with your PC’s USB controller. Try updating the chipset drivers from your motherboard manufacturer, or check your BIOS/UEFI for a setting that disables legacy USB support—some systems need it enabled for certain devices.

Code 43 on Specific Devices

Code 43 appears on a wide range of hardware, and the fix sometimes depends on the device type:

External hard drives: Try a powered USB hub or a Y-cable that draws power from two ports. Some portable drives need more current than a single port provides.
Webcams: Close all apps that use the camera, then unplug and replug. Update the camera driver and check the privacy settings in Windows that may block camera access.
Graphics cards: This is a separate issue from USB. Reseat the card, update the GPU driver in safe mode using Display Driver Uninstaller, and check the power supply connections.
Android phones: Switch the USB mode from “Charging only” to “File Transfer” on the phone. Try a different USB port and enable USB debugging in Developer Options.

How to Prevent Code 43 in the Future

Prevention is mostly about avoiding the conditions that cause the error. Use quality cables that are no longer than necessary, plug devices directly into the motherboard rather than through unpowered hubs, and keep your chipset drivers up to date. If you frequently move a laptop between locations, the USB ports can develop loose solder joints over time—handle the connector gently when inserting and removing cables.

Windows power management is a common trigger. The Allow the computer to turn off this device setting can interrupt data transfers on devices that are idle for a few seconds. Disabling it on all USB root hubs prevents this specific cause.

Also, avoid using USB extension cables with high-power devices like external drives or VR headsets. The added resistance can cause voltage drop that makes the device fail to enumerate.

Frequently Asked Questions

Can a USB cable cause Code 43?

Yes. A damaged or low-quality cable is one of the most common causes. The data lines inside can break while the power lines still work, so the device lights up but cannot communicate with Windows. Try a different cable before assuming the device is broken.

Will reinstalling Windows fix Code 43?

Rarely. Reinstalling Windows resets all drivers, which can help if the issue is driver corruption, but if the problem is hardware-related—a bad port, cable, or device—a clean install will not help. Try the driver and hardware fixes first.

Does Code 43 mean my device is permanently broken?

Not necessarily. Many Code 43 errors are caused by software, power management, or connection issues that are fixable. Only if the device fails on multiple computers with different cables and ports can you conclude the hardware is dead.

Why does my device work on one USB port but not another?

This usually means the failing port has a loose connection, damaged pins, or a failing USB controller. It can also happen if the port is USB 2.0 and the device requires USB 3.0 bandwidth. Use the working port or replace the damaged port.

Is Code 43 the same as “Device Descriptor Request Failed”?

They are closely related. “Device Descriptor Request Failed” is a specific message that appears in Device Manager under the device’s status, and it often accompanies Code 43. The descriptor is the data packet the device sends to identify itself; when it fails, Windows cannot load the right driver and reports Code 43.

Can a BIOS update fix Code 43?

In some cases, yes. BIOS updates can improve USB controller compatibility and fix enumeration bugs. Check your motherboard manufacturer’s website for a newer BIOS version, but only update if the release notes mention USB fixes—updating unnecessarily carries a small risk of instability.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →