How to Fix Code 43 Error in Device Manager

Code 43 means Windows disabled a device because the device or its driver reported a problem. Restart Windows, reconnect and power-cycle the device, check its cable, port, hub, and power, then update, roll back, or reinstall the exact driver from the manufacturer. If Code 43 follows the device to another computer or remains after an official driver reinstall, back up accessible data and arrange warranty service or replacement.

What Code 43 means and whether these fixes apply to your device

You can see Code 43 for USB devices, graphics adapters, Bluetooth hardware, cameras, storage devices, and other components listed in Device Manager. It is a general Windows stop signal, not a diagnosis: Windows received an error from the device or its driver and disabled the device.

The exact error is:

Windows has stopped this device because it has reported problems. (Code 43)

The cause can be a loose connection, insufficient power, a damaged cable, a bad or recently changed driver, a Windows update, firmware, or failing hardware.

Before changing anything, open Device Manager, expand the relevant category, right-click the device, and choose Properties. Record the device category, exact model name, manufacturer, and full text on the General tab. On the Driver tab, record the provider, date, and version. Also record anything that changed shortly before the failure, such as a Windows update, graphics driver installation, new USB hub, dock, cable, firmware update, or physical move.

These steps apply to Windows 10 and Windows 11. Driver changes generally require an Administrator account; restarting, reconnecting, and checking cables and ports normally do not. Save open work before restarting. If the device stores important data, back up accessible files before repeated reconnects or hardware tests. Do not format a storage device because it shows Code 43. The error concerns device communication or initialization and does not prove that its data is unusable.

If the device is not visible at all, select View > Show hidden devices in Device Manager, then choose Action > Scan for hardware changes. If it appears with a warning icon, continue below.

Try these safe checks before touching the driver

These checks restore communication without changing drivers. They normally require no Administrator account.

1. Save your work and restart Windows. Choose Restart, not only Shut down, because Fast Startup may preserve the old device state.
2. Disconnect the device, wait briefly, and connect it again. For a USB device, remove it safely first when Windows offers that option. For a monitor or graphics adapter, turn off the computer before reseating internal hardware.
3. Connect the device directly to the computer. Remove USB hubs, docks, extension cables, and adapters from the chain. A hub can fail or provide less power than the device needs.
4. Try another compatible port. On a desktop, a rear motherboard port can behave differently from a front-panel port. For USB-C devices, use a cable and port that support the required data or display mode, not merely charging.
5. Replace the cable if it is detachable. Inspect connectors for bent pins, looseness, dirt, or visible damage. Do not force a connector into a port.
6. Check external power. Turn on the device’s power switch, reconnect its power adapter, and use the manufacturer’s specified adapter when possible. A bus-powered drive, dock, or graphics enclosure can fail if the computer cannot supply enough power.
7. Test the device on another compatible computer if you can. Install no random driver for this test; use the other computer’s normal Windows support. If Code 43 follows the device, the device, cable, or firmware becomes more suspect. If it works elsewhere, focus on the original computer’s driver, port, power, or Windows changes.

If the device still shows Code 43 after these checks, continue with the driver steps. If it works, open Device Manager and test the workload that originally failed.

Reinstall or roll back the driver in the right order

Use Device Manager first, then the official support page for the computer or device manufacturer. Do not use generic driver-updater software. It can select an incompatible package, replace a working component, and obscure the change that caused Code 43.

Check for an available driver update

1. Open Device Manager as an Administrator.

Start > type Device Manager > Run as administrator

2. Expand the device’s category, right-click the affected device, and choose Update driver.
3. Select Search automatically for drivers. Install a compatible driver if Windows finds one, then restart when prompted.

The expected result is that Device Manager no longer shows the yellow warning icon. If Windows says the best drivers are already installed, that only means Windows found no newer matching package through that search; it does not prove that the installed driver is correct. If Code 43 remains, check the manufacturer’s official support page for the exact model and Windows version.

Roll back a recently changed driver

If Code 43 began immediately after a driver or Windows change, open the device’s Properties, select the Driver tab, and choose Roll Back Driver if the button is available. Select a reason, confirm, and restart.

The expected result is that the previous driver version returns and Code 43 clears. If Roll Back Driver is unavailable, Windows may not have retained the previous package. Use the manufacturer’s driver or the uninstall procedure below.

Uninstall and reinstall the device driver

Before uninstalling a graphics, storage, network, or Bluetooth driver, download the correct replacement from the computer or hardware manufacturer’s official support page and save it locally. If the device provides your network connection, make sure you can access the installer without that device.

1. In Device Manager, right-click the affected device and choose Uninstall device.
2. If Windows offers Attempt to remove the driver for this device, select it only when you have the correct replacement package ready. Removing the package can affect other devices that use the same driver.
3. Confirm Uninstall, then restart Windows. Windows may reinstall a built-in driver automatically.
4. If the device is still listed, right-click it and choose Update driver > Browse my computer for drivers, then select the extracted official driver folder. Alternatively, run the manufacturer’s installer exactly as its instructions specify.

The expected result is a clean device entry with the correct model and no Code 43. If Windows reinstalls the same failing driver or the error returns immediately, download a package specifically for the exact model and Windows version: use the PC manufacturer for built-in hardware and the device manufacturer for add-on hardware. Do not use a package for a similar model.

For graphics hardware, prefer the graphics-card or computer manufacturer’s support page and verify that the package is for the exact GPU and Windows version. A recent graphics driver can cause Code 43 even when the card itself is healthy, so rolling back provides useful evidence. Do not use a display-driver cleanup utility as the first step, and do not remove chipset or motherboard drivers casually.

How to tell whether Code 43 is gone or the hardware is failing

After a restart or driver installation, verify the device in Device Manager and test its normal function.

1. Open Device Manager and select Action > Scan for hardware changes.
2. Expand the device category and open Properties for the affected device.
3. On the General tab, confirm that the status says the device is working properly and that the yellow warning icon is gone.

This device is working properly.

4. Test the device in its normal workload. For a USB drive, copy a noncritical file. For a graphics adapter, reconnect the intended display and use an application that previously failed. For Bluetooth, pair the accessory again and test its main function.
5. Recheck after the computer has gone through a normal sleep, shutdown, or restart. Some power-management faults appear only after a state change.

If the expected status does not appear, Code 43 remains, or the normal workload still fails, the driver, Windows state, connection, power, firmware, or hardware still needs investigation. If Code 43 disappears on the original computer, the cause was likely a temporary connection, power state, Windows state, or driver issue.

If it returns only after a particular driver or Windows update, note that version and use the manufacturer’s supported alternative or a rollback where available.

If the same device shows Code 43 on another compatible computer after you have tried a known-good cable, port, and power source, the device or its firmware is likely at fault. A graphics card that fails in multiple systems, a USB device that disconnects everywhere, or hardware that becomes unusually hot, smells burnt, or makes abnormal sounds should be powered down and removed from service. Do not keep forcing it to reconnect.

Prevent Code 43 from returning and know when to escalate

Keep a record of the driver version that works, including its provider and date from Device Manager. Save the official installer when the manufacturer permits it, and note the Windows update or hardware change that preceded any failure. This gives you a known-good version to restore if a later update causes Code 43.

Use Windows Update and the manufacturer’s support page for drivers and firmware. Check update history if the error began after an update:

Windows 11: Settings > Windows Update > Update history
Windows 10: Settings > Update & Security > Windows Update > View update history

Install firmware only when it is explicitly intended for the exact model, and keep the device powered during the process. Do not download drivers from unofficial mirrors or use driver-updater programs that scan and replace hardware drivers in bulk.

Stop troubleshooting and contact the manufacturer when the device fails on another computer, a clean official driver installation changes nothing, or physical damage and power faults are present. Check warranty coverage before opening a device or replacing parts. Back up data from storage hardware while it is still accessible, then disconnect a drive that is repeatedly disappearing or producing read errors.

If the device works on another computer but not yours, provide support with the exact model, Windows version, Device Manager status text, driver version, recent update history, and the ports, cables, and computers you tested. If the device fails everywhere, replacement or warranty service is usually more sensible than repeated driver changes.

Conclusion

Restart Windows, check the connection and power, and install the exact official driver if needed. If Device Manager still reports Code 43 after testing another port or computer, back up accessible data and contact the manufacturer or replace the suspected hardware.

Frequently Asked Questions

Does Code 43 always mean the hardware is broken?

No. Code 43 can result from a temporary connection or power problem, a damaged cable, an incompatible or corrupted driver, a Windows change, firmware, or failing hardware. Test another port, cable, and compatible computer to separate these causes.

Should I use a driver-updater program to fix Code 43?

No. Use Device Manager, Windows Update, and the official support page for the exact computer or hardware model. Generic updater software can install the wrong driver and hide the original problem.

Why does my graphics card show Code 43 after an update?

A graphics driver change, Windows update, power issue, or hardware fault can cause it. Check power and connections, roll back the recent driver if possible, then install the exact driver from the computer or graphics-card manufacturer. If the card fails in another computer too, suspect the hardware.