Skip to main content

Gamepad Tester

SolvedVerified By Gamepad TesterVerified By Gamepad Tester

Windows Says My Controller Has A Problem, Error Code 43 In Device Manager

Asked by Vera L.27,410 views

Controller stopped working and Device Manager shows it with a warning triangle and the message that Windows has stopped this device because it has reported problems, code 43. The browser sees nothing, obviously. It happened after I unplugged it while a game was running, which I suspect is relevant. I have uninstalled the device and rebooted twice and it comes back with the same code. Is the controller dead or is this a Windows state I can clear?

Brand
Microsoft
Model
Xbox Wireless Controller Model 1914
Connection
USB-C Cable
System
Windows 11
Browser
Chrome 141
Test used in this questionGamepad TesterLive test of every button, stick, trigger and axis on any controller
Open Free Test
Short Answer

Code 43 is usually recoverable and your controller is probably fine. It means the driver reported a fault, and a full power cycle of the USB controller plus a clean device removal normally clears it.

Verified By Gamepad TesterVerified By Gamepad Tester
Tyler Vance
Tyler VanceVerified Gamepad Tester team memberGamepad Tester Team
QA And Test Automation Lead · Answered Mar 29, 2026

Code 43 sounds terminal and usually is not. It means the driver told Windows the device reported a problem, so Windows stopped talking to it. It is a state, and states can be cleared.

Your detail about unplugging mid-game is almost certainly relevant. Pulling a device while software holds it open can leave both the device and the USB stack in an inconsistent state, and Windows caches that. This is why uninstalling and rebooting has not helped: a normal restart on Windows 11 is a hybrid shutdown that restores the previous session, including USB controller state. You need a genuine cold power cycle, which is a different thing from a restart.

So the sequence that clears most code 43 cases: uninstall the device in Device Manager, including ticking any option to remove the driver, then shut the machine down fully with fast startup disabled, or hold shift while clicking Shut Down, and physically unplug the controller. Leave it a minute so the USB controllers lose power properly, then boot and plug the controller back in to a different port. Windows re-enumerates it from scratch.

If it comes back with code 43 on a different port after a cold boot, test the controller on a second computer. That single test splits the problem definitively: working elsewhere means your first machine's USB stack or that port, and failing everywhere means the controller. It is worth doing before you spend any more time on drivers.

Two other things worth clearing while you are at it. Update or roll back the chipset and USB drivers if the problem started after an update. And check the cable, because a cable with an intermittent data line can produce code 43 rather than simply not working, which catches people out.

For what it is worth, in our experience a controller that reports code 43 after a hot unplug is healthy far more often than not.

Step By Step Fix
  1. In Device Manager, uninstall the controller device and tick any option to remove its driver software.
  2. Disable fast startup in Windows power settings. A normal restart restores the previous USB state, which is why rebooting has not helped.
  3. Shut the machine down fully, or hold shift while clicking Shut Down, and unplug the controller.
  4. Leave it a minute so the USB controllers lose power, then boot and plug the controller into a different port.
  5. Swap the cable for one you know carries data. An intermittent data line can produce code 43 rather than simply failing.
  6. If code 43 returns, test the controller on a second computer. Working there means your machine or that port, failing everywhere means the controller.
  7. If it is machine-side, update or roll back the chipset and USB drivers, particularly if this started after a Windows or driver update.

Tested on: Xbox Model 1914 and DualSense CFI-ZCT1W deliberately hot-unplugged during active use on Windows 11 24H2 across six ports, with recovery attempted by restart, by cold shutdown with fast startup enabled, and by cold shutdown with fast startup disabled. Only the last reliably cleared the code 43 state.

Checked by Lucas Rocha on . How we verify answers

Did this fix your controller?
Was this answer helpful?
Share this guide

Community Replies 4

  • Accepted Solution
    Vera LindqvistCommunity Member

    Fast startup was the missing piece. I had restarted about five times and it never actually power cycled the USB controllers. Proper shutdown with it disabled and the controller came back first try. Not dead at all.

  • Mohan PillaiCommunity Member

    Mine was the cable. Code 43 made me think the controller was broken but a different cable worked immediately. Step five is worth doing early.

  • Aoife CarragherCommunity Member

    The second computer test is such a good tiebreaker. Mine worked fine on my laptop so I stopped blaming the controller and fixed my desktop's USB drivers instead.

  • Lennart FischerCommunity Member

    Hold shift while clicking shut down is a neat trick I did not know. Easier than digging through power settings every time.

Add Your Reply

Add screenshots, a short recording or filesDrag here, paste a screenshot, or tap to choose. Up to 2 files, 8 MB each. JPG, JPEG, PNG, WEBP, GIF, TXT, LOG, PDF, JSON, MP4, WEBM
Tyler Vance
Written and tested by

Tyler VanceVerified Gamepad Tester team member

QA And Test Automation Lead at Gamepad Tester

Tyler leads test automation. Before each change to the tools here goes live, his pipelines drive simulated inputs through the pages across multiple browsers and desktop environments and compare the readings against known-good baselines. It catches the regressions manual testing misses: a button index that shifts, an axis that stops updating, a layout that breaks at one viewport. On Gamepad Tester he signs off releases of the test tools and handles the answers where the tool itself, rather than the controller, is behaving oddly.

Browser test automationregression baselinessimulated input pipelinescross-environment QA
  • 25 answers on Gamepad Tester
  • Runs the automated regression suite that every change to these test tools passes before release.
  • Reviewed by Lucas Rocha

The Team Behind These Answers

All 40 specialists

Each answer is written by the specialist who owns that part of the hardware, tested on a real controller, and checked by a second team member. How we verify answers

Answers are free general guidance from the Gamepad Tester Team and the community. Opening a controller or replacing a thumbstick module can void your warranty, so check the maker's support or warranty first. Battery and soldering work carries a real risk of damage or injury.

Free Controller Tests

Every test runs in your own browser with the Gamepad API. No sign up, no download, and your controller data never leaves your device.

All tools

Read Next On The Gamepad Tester Blog

All articles

Latest From The Community

The newest replies from players and the Gamepad Tester Team.

All guides