Controller Stopped Working After a Windows Update?

Everything was fine yesterday. Windows installed an update overnight, and now your controller either isn't detected at all, connects but does nothing, or behaves erratically in ways it never did before.

This is a genuinely common experience, and the cause is almost always the same category of thing: an update changed a driver, reset a setting, or altered how Windows handles a device. The controller itself is rarely at fault, which is good news, because it means the fix is usually free and reversible.

Here's how to work through it methodically rather than reinstalling things at random.

First, confirm what actually broke

Before changing anything, narrow it down. This takes two minutes and stops you fixing the wrong thing.

Check whether Windows sees the controller at all. Right-click Start, open Device Manager, then plug and unplug the controller while watching the list, particularly under "Human Interface Devices" and "Sound, video and game controllers." If an entry appears and disappears as you connect it, Windows detects the hardware and your problem is driver or software level. If nothing changes, it's a detection problem.

Look for any entry with a warning triangle, which indicates a driver problem Windows already knows about.

Test the controller independently of games. Open a browser and run a button test. If inputs register there, the controller, connection, and basic drivers are all working, and whatever broke sits in a game or a layer above. If nothing registers, the problem is lower down.

Test wired if you normally use wireless, and vice versa. If wired works but Bluetooth doesn't, the update affected your Bluetooth stack rather than the controller, which narrows things considerably.

Fix 1: Restart properly, then power cycle the controller

Worth doing first because it costs a minute and genuinely resolves a share of post-update problems.

Do a full restart rather than a shutdown, since Windows fast startup means shutting down doesn't always fully reinitialise drivers. Then power cycle the controller itself and reconnect it.

Updates sometimes leave devices in an inconsistent state that a proper restart clears. Don't skip this because it seems too simple.

Fix 2: Reinstall the controller driver

This is the highest-value fix for post-update controller problems, because a driver that was replaced or corrupted during the update is the single most common cause.

In Device Manager, find your controller. It may appear under Human Interface Devices, or under "Sound, video and game controllers," and it might be listed as an Xbox controller, a HID-compliant game controller, or by its product name.

Right-click it and choose Uninstall device. If you're offered a checkbox to delete the driver software, tick it. Then unplug the controller, restart the PC, and reconnect the controller so Windows reinstalls the driver from scratch.

If several controller-related entries exist, including leftovers from controllers you no longer own, removing the stale ones can help too, since duplicate or conflicting entries confuse device enumeration.

Fix 3: Check Windows didn't disable it to save power

This one is easy to miss and catches a lot of people after updates, because updates frequently reset power settings to defaults.

Windows can suspend USB devices to save power, and when it does, your controller disconnects, often after a period of inactivity or seemingly at random.

In Device Manager, expand Universal Serial Bus controllers, and for each USB Root Hub entry, open its Properties, go to the Power Management tab, and untick the option allowing the computer to turn the device off to save power. Do the same for the controller's own entry if it has that tab.

If your symptom is a controller that works initially and then drops out, this is very often the cause.

Fix 4: Re-pair Bluetooth from scratch

If your controller connects over Bluetooth and stopped working after an update, don't just try reconnecting. Remove the pairing entirely and pair fresh.

Open Settings > Bluetooth & devices, find the controller, and remove the device rather than merely disconnecting it. Then put the controller back into pairing mode and add it again as though it were new.

Updates can corrupt stored pairing information, and a stale pairing will keep failing no matter how many times you reconnect. A clean re-pair fixes it. While you're there, check that Bluetooth itself is still enabled, since updates occasionally toggle it.

If Bluetooth is broken generally rather than just for your controller, the update likely affected your Bluetooth adapter driver, which you can reinstall the same way as in Fix 2.

Fix 5: Update the controller's own firmware

Distinct from Windows drivers, and worth doing since a mismatch between updated system software and old controller firmware causes real problems.

For Xbox controllers, use the Xbox Accessories app from the Microsoft Store, connected over USB. Our guide on updating Xbox controller firmware covers the process and what to do if an update stalls. For DualSense controllers, Sony's PlayStation Accessories app for Windows handles firmware updates without needing a console.

Fix 6: Check calibration wasn't reset

If your controller is detected and works but feels wrong, sticks off-centre, aim pulling, movement that doesn't match your input, the update may have reset or corrupted its calibration rather than breaking the connection.

Windows stores calibration data, and updates can disturb it. Recalibrating restores it, and the critical rule is to keep your hands completely off the sticks during the centring step, since resting a thumb there teaches the system a wrong centre point.

Our guide on calibrating a controller on Windows 11 walks through reaching the wizard, which is buried in a legacy control panel rather than the modern Settings app, and covers resetting a bad calibration.

Fix 7: Try a different port and cable

Not everything post-update is software. Updates sometimes change how specific USB controllers or ports are handled, so a port that worked before may behave differently now.

Try a rear motherboard port rather than a front-panel port or hub. Try a different cable, since charge-only USB-C cables carry power but no data and produce exactly the symptom of a controller that charges but isn't detected. These take seconds to test and rule out a whole category.

Fix 8: Roll back the update

If nothing else works and you're confident the update caused it, you can reverse it.

Windows lets you uninstall recent updates through Settings > Windows Update > Update history > Uninstall updates. You can also roll back a specific driver rather than the whole update: in Device Manager, open the device's Properties, go to the Driver tab, and use Roll Back Driver if it's available, which reverts to the previously installed version.

Rolling back a driver is the more targeted option and usually the better first choice, since it addresses the likely cause without reversing security fixes.

Be aware that Windows will generally try to reinstall the update later, so treat rollback as buying time while a proper fix or a subsequent patch arrives, rather than as a permanent solution. If a particular update reliably breaks your controller, it's worth checking whether the manufacturer has released updated drivers.

If the controller works but games don't see it

A distinct scenario worth separating. If the browser test registers your inputs but games don't respond, your drivers and connection are fine and the problem is in a game or input layer, not in Windows' device handling.

That points at Steam Input settings, remapping software that needs reinstalling after the update, or per-game controller settings. Updates can disturb these too, particularly by resetting configurations. Reinstalling your remapping tool of choice often rebuilds the virtual drivers it depends on, which updates sometimes damage.

The short version

Post-update controller problems are almost always driver, setting, or pairing issues rather than hardware failures. Confirm what broke first by checking Device Manager and testing the controller in a browser, which separates a detection problem from a game problem. Then restart properly, reinstall the controller driver by uninstalling it and reconnecting, disable USB power management, and re-pair Bluetooth from scratch rather than just reconnecting. Update controller firmware, recalibrate if it's detected but feels wrong, and try a different port and cable. Roll back the driver, or the update itself, only if nothing else works.