Playing Mobile Games With A Controller: What Works, What Doesn’t, And What To Test Before You Spend
You paired the controller, the light went solid, your phone said "Connected," and then the game did absolutely…
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?
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.
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.
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
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.
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.
Every test runs in your own browser with the Gamepad API. No sign up, no download, and your controller data never leaves your device.
You paired the controller, the light went solid, your phone said "Connected," and then the game did absolutely…
There is a particular kind of bad session that never gets diagnosed. You lose a duel you should have won. Your car…
A shot fired half a second after I pulled the trigger, the same delay I had been chasing for two weeks, faulting…
The newest replies from players and the Gamepad Tester Team.