How to Fix “Windows Has Stopped This Device” Code 43 Errors in Windows 11 and 10

Jake Harfield
·
15 min read

Help Desk Geek is reader-supported. We may earn a commission when you buy through links on our site. Learn more.

“Windows has stopped this device because it has reported problems. (Code 43)” means the device or one of its drivers told Windows that something failed, so Windows shut it off. Start with a full shutdown, then reinstall the device from Device Manager. If the error comes back, work through the rest of the fixes below in order.

Illustration of a glowing error dialog box with an OK button and mouse pointer

What Causes Code 43 in Windows?

Code 43 is a status that Windows shows after a device’s driver or firmware reports a failure. It tells you which device failed, but it doesn’t say why. You find the cause by checking the driver, the cable and port, power, and the hardware itself. It can show up on any device in Device Manager on Windows 11 and Windows 10. It’s especially common with graphics cards, USB devices, external drives, Bluetooth adapters, audio devices, and docks (Microsoft: Error codes in Device Manager).

Common causes include:

  • A corrupted, incompatible, or half-installed driver, or a driver update that introduced a bug
  • A failed Windows update or an incomplete device installation
  • Outdated BIOS/UEFI, chipset, USB controller, or device firmware
  • Not enough power, or a bad cable, hub, port, dock, or external enclosure
  • Overheating, physical damage, or a failing component
  • GPU instability from overclocking or undervolting
  • Less often, a specialized device that needs the manufacturer’s own driver rather than the generic Microsoft one
Method / FixBest ForQuick Steps / Key Detail
Restart or full shutdownAny device, first attemptStart > Power > Restart, or shut down and unplug the device
Swap cable, port, or PCUSB devices, external drives, docksUse a rear motherboard port and remove hubs and adapters
Uninstall and reinstall the deviceCorrupted driver installDevice Manager > Uninstall device > Scan for hardware changes
Install the manufacturer’s driverGPUs, chipsets, docks, laptopsDownload the driver for your exact model from the vendor’s support page
Roll back the driverError started after a driver updateProperties > Driver > Roll Back Driver
Disable USB power savingError comes back after sleep or idleTurn off USB selective suspend and hub power saving
Update BIOS/UEFIKnown compatibility issue in vendor release notesUse only the PC or motherboard maker’s update tool

How To Check for Code 43?

Before you fix anything, confirm that Code 43 is the error you’re dealing with. Other Device Manager codes need different fixes.

  1. Right-click the Start button and select Device Manager.
  2. Look for a device with a yellow warning icon. If you don’t see one, expand Display adapters and Universal Serial Bus controllers first.
  3. If the device still doesn’t turn up, check Disk drives, Bluetooth, Network adapters, Sound, video and game controllers, Cameras, Human Interface Devices, Portable Devices, System devices, and Other devices.
Windows 11 Device Manager with Display adapters and Universal Serial Bus controllers expanded, one device showing a yellow warning triangle
  1. Double-click the device, or right-click it and select Properties.
  2. On the General tab, read the Device status box. If Code 43 is the problem, it says “Windows has stopped this device because it has reported problems. (Code 43)”.
Device Properties General tab showing Device status "Windows has stopped this device because it has reported problems. (Code 43)" with OK and Cancel buttons visible

On USB problems, the entry with the warning might be USB Root Hub, Generic USB Hub, USB Mass Storage Device, a host controller, or the device’s brand name. A Code 43 on a USB controller can take down every device plugged into it.

While the Properties window is open, check two more tabs. The Events tab lists recent install and configuration events. The Details tab shows the Hardware Ids value, which helps you find the exact driver on a manufacturer’s site. Copy it down before you start changing drivers.

If the status shows a different code, this article won’t fix it. Look up that specific code instead.

How To Fix Code 43

Try the fixes in order. The quick, low-risk ones come first. Firmware updates and system rollbacks come near the end.

Fix #1: Restart Your Computer

A restart reloads the driver and resets the device’s connection. That clears a lot of one-time Code 43 failures.

  1. Save your open files and close your programs.
  2. Select Start > Power > Restart.
  3. Once you’re signed back in, check the device status in Device Manager again.

If the error is still there, do a full power cycle. That resets USB and dock controllers more thoroughly than a restart does:

  1. Select Start > Power > Shut down.
  2. Wait until the PC is completely off.
  3. Unplug the affected device. If it’s practical, unplug the PC’s AC power too.
  4. Wait at least 30 seconds, then plug everything back in and power on.
Windows 11 Start menu with Power button menu open showing Sleep, Shut down, and Restart options

Use Restart for the first attempt. Fast Startup keeps part of the Windows session saved through a normal shutdown, and Restart doesn’t. Only pull power on a desktop, or on a laptop running from its charger. Don’t open a sealed laptop to disconnect the battery unless the manufacturer’s instructions tell you to.

Fix #2: Check If the Device Is Faulty

This tells you whether the problem is in the device or in your PC.

  1. Plug the device into a second computer.
  2. Swap in a known-good USB cable, or the original cable that came with the device.
  3. On the first PC, try a different port. On a desktop, use a rear port that connects straight to the motherboard, not a front-panel port or a hub.
  4. Remove any docks, KVM switches, extension cables, and adapters, then test the device on its own.
  5. Check for bent connectors, cracks, unusual heat, or clicking and grinding noises.

If the device works on the second PC, the hardware is probably fine and the problem is in the first PC’s drivers, firmware, or ports. That’s a strong hint, but the second PC also has different power, drivers, and USB controllers, so it doesn’t prove the device is healthy. If the device fails on both machines, suspect the device, its cable, or its enclosure.

Power is a frequent cause with USB gear. Bus-powered external drives and some audio interfaces need more current than an unpowered hub or front port supplies. Try a powered USB hub, the device’s original charger, or a different docking station. USB-C ports also vary in what they support.

A port that charges a device might not support display output, Thunderbolt, or the data speed the device needs, and that mismatch usually shows up as no display, slower speeds, or a different error rather than Code 43, so rule it out before blaming the driver. If your USB port is faulty, you might be able to repair it.

Fix #3: Properly Eject Your Device on a Separate Computer

This optional step sometimes helps external drives that were unplugged in the middle of a write. You’ll need a second computer. It won’t fix a failing drive or a damaged USB controller.

  1. Connect the drive to the second computer and wait until it shows up in File Explorer.
  2. Close any files or apps that are using the drive.
  3. Open File Explorer, right-click the drive, and select Eject. You can also click the Safely Remove Hardware and Eject Media icon in the notification area. It’s often hidden behind the up arrow next to the clock.
Windows 11 taskbar notification area overflow open with Safely Remove Hardware and Eject Media icon menu listing the external drive with an Eject option
  1. Wait for the notification saying it’s safe to remove the hardware.
  2. Unplug the drive and connect it to your original PC.

Some devices don’t offer an eject option at all. If the drive doesn’t appear on the second PC either, open Disk Management to see whether Windows detects it. Don’t initialize, format, or create partitions on a drive that holds data you need. Those steps can make data recovery much harder.

Fix #4: System Restore

If Code 43 started right after a driver change, a Windows update, or a new program, System Restore can return system files, drivers, and registry settings to an earlier point. It doesn’t touch your personal documents. It does remove apps and drivers installed after the restore point you pick (Microsoft: Recovery options in Windows).

Before you start, write down the current driver version from Properties > Driver.

  1. Open Start, type Recovery, and open the Recovery Control Panel result. Pressing Windows + R, typing rstrui.exe, and pressing Enter also works.
  2. Select Open System Restore.
Control Panel Recovery page with "Open System Restore" link highlighted
  1. Select Next, then choose a restore point dated before the error started.
  2. Select Scan for affected programs to see what will be removed, then select Close.
System Restore window listing restore points with dates, one selected, and the "Scan for affected programs" button visible
  1. Select Next > Finish. The PC restarts and applies the restore point.

Note: System Restore only works if System Protection was turned on and a restore point already exists. On some installs, System Protection is off by default. On work or school PCs, IT may have blocked System Restore. If Windows won’t boot normally, open Windows Recovery Environment > Troubleshoot > Advanced options > System Restore.

Fix #5: Disable and Re-enable Your Device

Disabling and re-enabling the device makes Windows reload its driver without a full restart. It’s low risk.

  1. Right-click Start and select Device Manager.
  2. Right-click the affected device and select Disable device.
  3. Confirm with Yes. The wording can vary by device.
  4. Wait a few seconds, then right-click the device again and select Enable device.
  5. Open Properties and check whether the Device status now says This device is working properly.
Device Manager right-click context menu on a device showing Update driver, Disable device, Uninstall device, and Scan for hardware changes

Some system-critical devices don’t offer a Disable device option. If you disable your network adapter, display adapter, keyboard, or mouse, you’ll lose that function until you re-enable it. If it’s your only keyboard or mouse, keep a second input device handy.

Fix #6: Update, Reinstall, or Roll Back Device Drivers

This is one of the most useful fixes to try, especially for graphics cards. Microsoft’s own instructions for graphics Code 43 are to update the driver, and if that doesn’t work, to uninstall the device and scan for hardware changes (Microsoft: Fix graphics device problems with error code 43).

Update the driver

  1. Right-click Start and select Device Manager.
  2. Right-click the affected device and select Update driver.
  3. Select Search automatically for drivers (Microsoft: Update drivers through Device Manager).
Update Drivers dialog showing "Search automatically for drivers" and "Browse my computer for drivers" options

Windows updates might report that the best driver is already installed. That only means Windows has nothing newer on hand. Also check Settings > Windows Update > Advanced options > Optional updates and expand Driver updates if that section appears.

Install the manufacturer’s driver

For graphics cards, chipsets, storage controllers, docks, and laptops, the manufacturer’s driver usually works better than the generic one.

  1. Use your PC maker’s support page for chipset, USB, and platform drivers.
  2. Use the GPU maker’s official driver for a discrete graphics card.
  3. Use the peripheral maker’s support page for docks, drive enclosures, audio interfaces, and Bluetooth adapters.
  4. Match the exact model, Windows version, and architecture. Don’t install a driver built for a different OEM model.

For a graphics card, run a clean install with the GPU vendor’s own installer. Skip third-party “driver updater” utilities. They can install the wrong or modified drivers, which makes Code 43 harder to diagnose.

Uninstall and reinstall the device

  1. Download the replacement driver first, especially for a network, storage, chipset, or display device.
  2. In Device Manager, right-click the device and select Uninstall device, then confirm.
  3. If a checkbox like Attempt to remove the driver for this device appears, only tick it when you already have a replacement driver ready.
  4. Right-click your computer’s name at the top of Device Manager and select Scan for hardware changes. Restarting the PC also works.

Windows usually detects the device and reinstalls it. Check Device status again. If the device doesn’t reappear, the problem may be the hardware, cable, or controller rather than the driver.

Roll back the driver

If the error started right after a driver update, you can roll back the drivers to the previous version.

  1. In Device Manager, double-click the device.
  2. Open the Driver tab and select Roll Back Driver.
Device Properties Driver tab showing Driver Version, Driver Date, and the Roll Back Driver button
  1. Choose a reason and select Yes.

Note: Roll Back Driver is greyed out when Windows has no earlier driver package saved for that device. In that case, download a known-good older version from the manufacturer and install it manually.

Fix #7: Update Windows

Windows updates often include driver and USB stack fixes, so install any pending ones.

On Windows 11:

  1. Open Settings > Windows Update.
  2. Select Check for updates.
  3. Select Download & install or Install all if updates appear.
  4. Restart when Windows asks you to.

On Windows 10, the path is Settings > Update & Security > Windows Update > Check for updates. Windows 10 reached end of support on October 14, 2025, so it only gets security updates if the PC is enrolled in Extended Security Updates (ESU).

Windows 11 Settings > Windows Update page with Check for updates button and Advanced options link visible

Updates can also cause Code 43. If the error started right after an update, open Update history on the same page and check what installed. Then uninstall that update with Uninstall updates, or roll back the device driver from Fix #6. On a work or school PC, your IT department might control updates, and some of these options can be missing.

Fix #8: Power Management

Windows power saving can switch off a USB hub or device to save energy. If your device shows Code 43 after sleep or after sitting idle, turning this off is worth a try, though it won’t fix every case.

For USB hubs:

  1. Right-click Start and select Device Manager.
  2. Expand Universal Serial Bus controllers and double-click USB Root Hub, Generic USB Hub, or a similar hub entry.
  3. Open the Power Management tab and uncheck Allow the computer to turn off this device to save power.
USB Root Hub Properties Power Management tab with "Allow the computer to turn off this device to save power" unchecked
  1. Click OK.
  2. Repeat for the other hub entries that matter, then restart.

The Power Management tab doesn’t appear for every hub, driver, or Windows build. If it’s missing, see the next section.

For USB selective suspend:

  1. Open Control Panel and select Hardware and Sound > Power Options.
  2. Select Change plan settings next to your active plan.
  3. Select Change advanced power settings.
  4. Expand USB settings, then expand USB selective suspend setting.
  5. Set it to Disabled. If you see separate On battery and Plugged in settings, change both.
Power Options dialog with USB selective suspend setting set to Disabled on battery and plugged in
  1. Select Apply > OK.

This uses more battery, so treat it as a test. If Code 43 stops coming back, keep the setting. If it doesn’t help, switch it back to Enabled.

Fix #9: Update BIOS

An outdated BIOS/UEFI can cause compatibility problems with USB controllers, PCIe graphics cards, storage, and docks. A failed BIOS update can also leave the PC unable to boot, so only do this when the release notes mention a fix for your problem, or the error started after a platform change.

  1. Find your exact PC or motherboard model and your current BIOS version. Type System Information in Start to find both.
  2. Go to the PC or motherboard maker’s official support page and read the release notes for newer versions.
  3. Back up anything important.
  4. Plug a laptop into its charger. Don’t rely on the battery.
  5. Disconnect unnecessary peripherals.
  6. Run only the manufacturer’s update tool or firmware file.
  7. Don’t power off, restart, or close the lid while the update runs.

Never flash a generic motherboard BIOS onto a branded PC from a company like Dell, HP, or Lenovo. If the failing device is a graphics card, SSD, dock, or drive enclosure, also check whether that device’s maker offers its own firmware update.

When the Standard Steps Fail

The fixes above follow Microsoft’s standard steps. These are the situations where those steps don’t work as described.

The Power Management tab or a setting is missing or greyed out

This happens on laptops with Modern Standby, with vendor-specific drivers, on devices controlled by a dock or system driver, and on PCs managed by Group Policy or an MDM tool like Intune. Windows doesn’t offer a supported way to force the tab to appear.

Instead, install your PC maker’s chipset, USB, dock, and BIOS updates, test without the dock, and plug directly into the PC. Skip registry hacks that unhide power settings, because they’re hard to undo. If an admin locked the setting on a work PC, ask IT to make the change.

“The best drivers for your device are already installed”

This message only means Windows Update has nothing newer for the device. The installed driver could still be the wrong one. Search the manufacturer’s site using the Hardware Ids value from the Details tab. Then compare the driver date and version under Properties > Driver.

Windows keeps replacing your driver

If you install a known-good driver and Windows Update swaps it out again, Code 43 returns. Pause updates for a week from Settings > Windows Update while you confirm the older driver is stable. Then use the manufacturer’s installer, which handles this better than a manual driver install. Keep the newer driver package saved in case the older one fails.

The device doesn’t show up in Device Manager at all

  1. Select View > Show hidden devices.
  2. Select Action > Scan for hardware changes.
  3. Try another cable, port, and power source, and remove any hubs or adapters.
  4. Check whether the BIOS/UEFI or the manufacturer’s diagnostic tool can see the device.

If the device doesn’t appear in Device Manager or in firmware diagnostics, Windows isn’t getting a hardware connection at all. Treat it as a cable, port, or device fault.

Code 43 comes back after sleep, shutdown, or docking

Check these:

  • Sleep, hibernation, Fast Startup, and Modern Standby. Do the USB power steps in Fix #8.
  • Dock and USB-C firmware from the dock maker.
  • GPU overclocking or undervolting. Return the card to stock settings.
  • BIOS and chipset driver versions.
  • Overheating, especially in laptops and small-form-factor PCs.

Graphics card Code 43

Device Manager can’t tell whether the cause is the driver, the power supply, the firmware, or the card. Check that the monitor cable is plugged into the graphics card and not the motherboard. Check that the card is fully seated and that every PCIe power connector is attached. Then do a clean install of the vendor’s driver. If Code 43 survives all of that and the card is overclocked, reset it to stock speeds first.

External drive Code 43

Your data comes before the fix. If the drive clicks, grinds, or keeps disconnecting, stop testing it. Copy off what you can while it’s stable, or contact a professional data recovery service. Trying a different cable or a powered external hard drive enclosure is fine. Initializing or formatting the disk isn’t.

Back to Work

Uninstalling the device and reinstalling the manufacturer’s driver (Fix #6) is the fix most worth trying first, and the full shutdown in Fix #1 is a quick second check. If the error keeps returning after sleep or docking, check power management and dock firmware as well as the driver. If the device fails on two different computers with a known-good cable, it’s a hardware fault. Check the warranty, and before you contact support, write down the device model, hardware ID, driver version, and your Windows version.