Controller Rumble Not Working
Dead controller rumble is more often software or low battery than a failed motor. Run the vibration test first — it drives the motors directly through the browser, bypassing the game, Steam Input, and Windows audio routing. If it buzzes there, the hardware is fine and the fix is a setting. If it stays silent, the motor or its wiring has failed.
Diagnose before you fix
Confirm the symptom and measure its severity first. The test result tells you whether to clean, recalibrate, or replace — different severities call for different fixes.
Vibration Test
This is the whole diagnosis in one step. The vibration test drives the motors directly through the browser's haptic interface — independent of any game, launcher, or driver. Run the strong motor, the weak motor, then both. If the controller buzzes in the browser, the motors and their wiring are physically fine and your problem is a software setting. If the browser test produces nothing, the failure is hardware, and you can stop chasing software fixes.
Run the vibration test- A Chrome or Edge browser (best haptic support)
- A USB data cable (to isolate Bluetooth as a cause)
- A small screwdriver set (only if the browser test confirms dead motors)
Step by step
Work through these in order. After the last step, run the diagnostic again to confirm the fix held.
- 01
Prove the motors with the vibration test
Open the vibration test, connect the controller, and run the strong motor, the weak motor, then both together. Chrome and Edge have the best support for the browser haptic interface. If you feel rumble here, skip straight to the software steps below — your hardware is confirmed working and a teardown would be wasted effort. If both motors stay completely silent, jump to the wired retest and hardware steps near the end.
- 02
Charge the battery — power-saving cuts rumble first
This is the single most common cause and the easiest to miss. Vibration motors are the biggest power draw in the controller, so when the battery drops below roughly 20%, the firmware on modern controllers (Xbox Series, DualSense) automatically cuts power to the motors to extend playtime — buttons and sticks keep working, rumble silently stops. Plug in via USB or charge to full. If rumble returns, the motors were never broken; the controller was just conserving power.
- 03
Check in-game and Steam Input vibration settings
Vibration is toggleable in most games and can be globally overridden by your launcher. Check the game's own accessibility or controller settings first. Then, on Steam: Settings → Controller → enable vibration/rumble for your controller type, and check the per-game controller profile, which can disable rumble independently of the global setting. On Xbox: the Xbox Accessories app has a vibration toggle. A browser test that buzzes plus a game that doesn't almost always means the setting is off here.
- 04
Fix DualSense audio routing on PC (the signature PS5 trap)
DualSense haptics on PC are delivered as an audio stream, so Windows sometimes routes your game's 'vibration' to the controller as a speaker — or disables haptics because it thinks the DualSense is your audio output. Open Sound settings and make sure your default output is your actual speakers or headphones, not 'Wireless Controller.' Re-enable the Wireless Controller speaker/microphone devices, then relaunch the game. Some PC titles also require DS4Windows (which presents the DualSense to Windows as an Xbox pad) to get rumble at all.
- 05
Retest wired to rule out Bluetooth
Bluetooth haptic delivery is less reliable than a cable, especially on Windows. If rumble is intermittent or absent over Bluetooth, connect a USB data cable and retest in both the vibration test and your game. If wired rumble works and Bluetooth doesn't, the motors are fine — the issue is the wireless haptic path, and wired play (or the controller's 2.4GHz dongle where available) is the workaround.
- 06
If the browser test is silent, repair the hardware
Genuinely dead motors are rare but real. With the controller open, a motor that whirs faintly but doesn't shake has usually lost its counterweight off the shaft; total silence usually means a snapped or desoldered motor wire. ERM rumble motors are inexpensive ($5–15) and iFixit publishes vibration-motor replacement guides for every major model. DualSense and Switch Pro use voice-coil/LRA actuators rather than spinning weights — those are a more involved replacement and often make warranty service the better path.
CautionOpening the controller voids the manufacturer warranty on PlayStation, Xbox, and Nintendo hardware. If the controller is in warranty, pursue the repair path below before disassembling.
Where to go next
Persistent symptoms usually mean hardware wear that cleaning and recalibration can't reach. These resources cover repair, replacement, and warranty paths.
Other tests for the same controller
A symptom rarely arrives alone. Worn sticks often coincide with deadzone creep and reduced circularity — run the related diagnostics while the controller is already in your hands.
Variants of this symptom
The same underlying issue presents differently across controllers. These device-specific guides cover the variations.
Key definitions
Plain-language definitions for the terms used on this page. Each links to the full glossary entry with thresholds, mechanism, and FAQs.
vibration questions
The most common cause is a low battery — modern controllers cut power to the vibration motors below roughly 20% to extend playtime, so rumble stops while buttons keep working. Charge to full and retest. If rumble doesn't return after charging, run the vibration test to confirm whether the motors themselves are alive before assuming hardware failure.
Run the vibration test in Chrome or Edge. It drives the motors directly through the browser, bypassing every game, launcher, and driver. If the controller buzzes in the browser, the motors are physically fine and your problem is a software setting. Only complete silence in the browser test — after charging and a wired retest — points to a genuine motor or wiring failure.
On PC, DualSense haptics are delivered as an audio stream, and Windows often misroutes them — either trying to play the 'vibration' through your speakers, or disabling haptics because it detects the DualSense as an audio device. Set your default sound output back to your real speakers, re-enable the Wireless Controller audio devices, and relaunch. Many PC games also need DS4Windows to get DualSense rumble working.
It can. Bluetooth haptic delivery is less reliable than a wired connection, particularly on Windows, and can produce intermittent or missing rumble even when the motors are perfectly fine. If vibration is flaky over Bluetooth, connect a USB data cable and retest. Working wired rumble confirms a healthy controller and points the fix at the wireless path rather than the hardware.
That split is good news — it proves the motors and the haptic path are healthy, so the problem is entirely in software. Check vibration is enabled in the game's own settings, then in Steam Input's controller profile for that specific game (which can disable rumble independently of the global toggle), and on Xbox controllers in the Xbox Accessories app. The fix is a setting, not a repair.
No. Xbox controllers use ERM motors — spinning weights that create vibration through centrifugal force, with a slight spin-up and spin-down lag. The DualSense and Switch Pro Controller use voice-coil/linear-resonant actuators that move a mass back and forth electromagnetically, giving instant start-stop and variable frequency for far more precise haptic textures. The actuator type matters for repair: voice-coil units are a more involved replacement than a simple ERM motor.
Indirectly, yes — a charge-only cable powers the controller but doesn't carry data, so the controller stays on its wireless link and you may think wired mode 'didn't fix' the rumble. Always use a known data cable when testing wired. The cable can't affect vibration strength once a data connection is established; it either carries the haptic commands or it doesn't.
Still seeing the issue?
Re-run the diagnostic to confirm whether the fix held or whether escalation is needed.
Run the test again