How to Fix Code 43 in Device Manager on Windows 11

What Code 43 actually means

Code 43 is not a Windows fault: it is the device's own status report. When hardware hits an internal error it cannot recover from, its driver reports the failure to Windows, and Device Manager parks the device with the yellow warning triangle. The message shows on the General tab of the device's Properties, and the same device can appear under different names when it fails during enumeration — a broken USB drive, for instance, shows up as “Unknown USB Device (Device Descriptor Request Failed)”.

That is why the fix order matters: cheap software causes first, hardware conclusions last. In practice the trouble comes from a crashed or corrupted driver, a botched Windows update that replaced a working driver, an unstable overclock, a power or cable problem on the port — or a genuinely dying device.

• Corrupted or crashed driver — the most common cause, cleared by a reinstall
• A Windows update that replaced a working driver with a broken one
• Unstable GPU overclock or undervolt that makes the card fail its own checks
• USB power or cable issues: unpowered hubs, long cheap cables, worn-out ports
• Failing hardware — a GPU, drive or controller on its way out

The fixes, in the order worth trying

Start with a full restart — not sleep or hibernate — because re-enumeration clears many one-off device faults. Then open Device Manager (Win+X > Device Manager), right-click the failing device, choose Uninstall device, tick the “Attempt to remove the driver” checkbox for GPUs, and restart: Windows redetects the hardware and installs a driver from its own store. After that, update the driver deliberately — either with the vendor's own package (NVIDIA, AMD, Intel) or through Settings > Windows Update > Advanced options > Optional updates > Driver updates — and if Code 43 appeared right after an update, roll the driver back on the same Driver tab instead.

USB devices follow their own branch of the routine: replug into a different port, ideally a rear motherboard port on a desktop, drop any unpowered hubs and swap the cable. For graphics cards that keep throwing Code 43, a clean install with DDU removes every driver trace and is the standard next step; if the card still reports failures afterwards, reseat it, check both power connectors and test it in another PC before buying a replacement.

When it is hardware — and how to be sure

The decisive test is context: a device that throws Code 43 with a known-good driver, on a different port and cable, in a different PC, or from a clean Windows setup, is reporting real hardware failure. GPUs add two more suspects — an underpowered or aging PSU and riser or PCIe-slot contact problems — so reseat the card, press the power connectors home and, on a used card, allow for a previous mining or overclocking life. Persistent Code 43 on the integrated GPU of a laptop usually points to temperature or board-level faults, which is a repair-shop diagnosis rather than a settings fix.

One practical rule: do not delete driver files in C:WindowsSystem32drivers manually or “clean” the driver store by hand — you will break unrelated devices and gain nothing. Windows manages its own store; your tools are uninstall, roll back, DDU and vendor installers, nothing else.

Questions and Answers

Read next

All articles · FAQ