Your Meta Quest Pro controllers work fine during setup, then start dropping out mid-session. The tracking ring light goes dim or off, the pointer freezes or drifts for a second or two, and the headset shows a “Controller disconnected” toast — sometimes reconnecting on its own, sometimes requiring you to press a button to wake them back up. In heavier titles like Beat Saber or Contractors, a dropout usually means a missed block or a lost firefight, and the symptoms often get worse as battery levels fall or as the session goes on.
This is annoying but rarely urgent — it is almost always a software, power, or interference issue rather than broken hardware, and the vast majority of cases get solved with one of the fixes below. Work through them in order, starting with the two-minute checks, and only consider a warranty claim if everything here fails. Everything applies to Quest Pro controllers paired with a Quest Pro, Quest 2, Quest 3, or Quest 3S headset running current firmware in 2026.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Low or failing AA batteries | Check Settings > Controllers battery readout; dropouts cluster below roughly 20% | Very easy |
| Auto-sleep triggering too aggressively | Controllers sleep when idle even during active play; wake delay is noticeable | Easy |
| 2.4 GHz Wi-Fi or USB 3.0 interference | Dropouts get worse when a router is near the play area or a USB 3.0 drive is plugged into a PC during Link play | Easy |
| Stale pairing or firmware glitch | Dropouts persist across apps and restarts; one controller fails more than the other | Easy |
| Outdated headset OS | Check Settings > System > Software for a pending update | Easy |
| Tracking ring IR window dirty or obstructed | Physical inspection — smudges, silicone cover edges, or case residue on the ring’s camera window | Easy |
| Defective controller hardware | Dropouts continue after a factory reset, fresh batteries, and re-pairing | Hard (RMA) |
Fix 1: Replace the Batteries Properly
What causes it
Quest Pro controllers use one AA battery each, and Bluetooth output power drops as voltage sags. Cheap or partially drained cells cause exactly the intermittent-dropout pattern described here, and rechargeable AAs at 1.2V nominal can also read “low” earlier than alkalines.
How to check
Put on the headset and open Settings > Controllers (or Quick Settings > Controllers). Each controller shows a battery percentage. Anything under about 30% is a prime suspect. Also check for a controller that reads fine at rest but dips suddenly when vibration or intense tracking kicks in.
What to do
Open the battery hatch on the grip (press the latch and slide the cover down), remove the cell, and inspect the contacts for corrosion or bent springs. Insert a fresh name-brand alkaline AA, matching the polarity marking. Repeat for both controllers even if only one is misbehaving, so you have a known-good baseline.
How to undo it
No undo needed — swap in your old cells or different batteries at any time. If you prefer rechargeables, use low-self-discharge NiMH brands and accept they may report lower percentages sooner.
Fix 2: Check for a Pending OS Update
What causes it
Meta ships periodic Horizon OS updates that include controller firmware and Bluetooth stack changes. Running an outdated build can leave your controllers on mismatched firmware that drops the link intermittently.
How to check
Go to Settings > System > Software (labeled Software Update on some builds). If an update is available, you will see it listed here with an option to install. The headset typically shows a notification badge on Settings when one is pending.
What to do
Connect the headset to Wi-Fi, leave it charging, and tap Download and Install. The process takes 10–20 minutes and the headset will restart. Afterward, leave both controllers powered on and near the headset for 15 minutes so their firmware updates propagate automatically.
How to undo it
You cannot roll back a Horizon OS update once installed. There is normally no reason to — this fix only changes the headset build, not your games or data.
Fix 3: Disable Aggressive Controller Auto-Sleep
What causes it
Quest Pro controllers sleep to conserve the AA cells. Firmware updates have occasionally tuned the idle timer aggressively, so controllers power down during lulls in gameplay — menus, dialogue scenes, or moments where your hands rest at your sides — and the drop you see is actually the sleep timer firing.
How to check
Note when the disconnect happens. If it occurs while you are stationary in-game rather than during fast motion, and the controller needs a button press to come back, auto-sleep is the likely culprit. Compare behavior with the controllers held and moving continuously.
What to do
Open Settings > Controllers and look for power management options such as controller sleep or idle timeout, and set the timer to its longest available value (typically 5 minutes rather than shorter options). On builds without a user-facing timer, keep the controllers in motion during passive scenes, or simply tap the grip button periodically during long menu sequences. Installing the latest OS update (Fix 2) also picks up the most recent sleep-timer tuning.
How to undo it
Return the timeout setting to its previous value in the same menu, or factory reset the headset to restore defaults (Settings > System > Reset Procedures > Factory Reset — this erases data, so back up first).
Fix 4: Reduce Wireless Interference
What causes it
The controllers and headset communicate over 2.4 GHz Bluetooth LE. That band is shared with Wi-Fi routers, USB 3.0 ports and cables (which radiate broadband noise), microwave ovens, and crowded channel environments in apartments. Interference causes packet loss that shows up as tracking dropouts.
How to check
Test whether dropouts correlate with location. If the problem disappears when you play in a different room or with the router powered off for five minutes, interference is confirmed. During PCVR via Link, unplug any USB 3.0 devices and see if the dropouts stop.
What to do
Move your Wi-Fi router at least 6–10 feet (2–3 meters) from your play space, or switch it to the 5 GHz band for devices other than the headset. Set the router’s 2.4 GHz channel to 1, 6, or 11 — whichever is least congested in a Wi-Fi analyzer app. During wired Link sessions, use a USB 2.0 extension or a port on the opposite side of the PC from the one driving the headset, or use Air Link on 5 GHz instead of a noisy USB 3.0 run.
How to undo it
Move hardware back and restore your router channel settings. Nothing here is persistent or destructive.
Fix 5: Re-Pair the Controllers
What causes it
Pairing data can become stale after OS updates, long storage periods, or a failed firmware handoff. A controller holding a half-valid pairing will connect, drop, and reconnect in a loop — the classic symptom set.
How to check
Open Settings > Controllers > Left/Right Controller and look for connection errors, repeated “Searching” status, or a controller that appears paired but does not respond. If one controller is consistently worse than the other, that controller’s pairing is suspect.
What to do
In Settings > Controllers, select the problem controller and choose Unpair (or Remove). Then re-pair it: for the left controller, hold the X and Menu buttons together for about three seconds until the tracking LED blinks; for the right controller, hold the Meta and Y buttons. The headset detects the controller and completes pairing automatically. Pair one controller at a time with the other powered off.
How to undo it
Re-pairing replaces the old link; there is nothing to undo. If you want to revert entirely, repeat the process with both controllers — no data is lost.
Fix 6: Clean the Tracking Ring’s IR Window
What causes it
Each self-tracking controller has an IR camera behind a window on the tracking ring. Skin oils, sunscreen, residue from silicone coverings, or a shifted cover can partially block it, degrading self-tracking until the controller briefly loses confidence in its position — which the headset reports as a disconnect.
How to check
Inspect the ring’s window under bright light at an angle. Look for smudges, a silicone controller cover overlapping the window edge, or adhesive residue from labels. Compare dropouts before and after a quick wipe.
What to do
Remove any controller covers. Wipe the window with a dry microfiber cloth; for stubborn residue, lightly dampen the cloth with water only — never alcohol or solvents near the window seal. Recheck in a well-lit play area, since the self-tracking cameras also need reasonable lighting; very dark rooms can compound the problem.
How to undo it
Put the covers back on, ensuring they sit clear of the camera window.
Fix 7: Power-Cycle Everything Correctly
What causes it
The headset’s Bluetooth service can get into a bad state after sleep/resume cycles, leaving controllers in limbo. A full cold boot clears the radio stack without touching any settings.
How to check
If dropouts started suddenly after the headset sat on a charger or came out of sleep, and no settings changed, a stuck radio state is likely.
What to do
Power both controllers off (hold the system/menu button area until the LED goes dark, or remove a battery). Then fully restart the headset: hold the power button on the headset, choose Restart — or for a true cold boot, hold the power and volume-down buttons until the boot menu appears. Once the headset reaches the home environment, power the controllers back on by pressing any button and let them reconnect before launching anything.
How to undo it
Nothing to undo — a restart has no persistent effect.
Fix 8: Factory Reset and Start Clean
What causes it
Deep software corruption in the Horizon OS controller service, accumulated from many updates, can survive restarts and re-pairing. A factory reset rebuilds the entire configuration from scratch.
How to check
Use this as the final software step: if Fixes 1–7 have all failed, and both controllers misbehave on a freshly restarted headset with fresh batteries, residual software corruption is the remaining software explanation.
What to do
First back up: confirm cloud backup is on under Settings > System > Backup so your app data restores. Then go to Settings > System > Reset Procedures and choose Factory Reset, or use the hardware method: power off the headset, then hold the power and volume-down buttons until the boot menu loads, and select Factory Reset with the volume buttons and confirm with the power button. The reset takes several minutes. After setup, re-pair the controllers (see Fix 5) and install any pending updates before testing.
How to undo it
A factory reset cannot be undone, but restoring from cloud backup during setup recovers your apps and most data.
If Nothing Works
If dropouts persist after a factory reset, fresh quality batteries, re-pairing, and an interference-free play space, one of the controllers is likely defective — most often a failing radio module or a damaged tracking-ring camera. Contact Meta support through the Meta Horizon mobile app or meta.com/help to start a warranty service request; Quest Pro controllers carry a one-year limited warranty (two years in some regions, including the EU). Before shipping, note exactly when the dropouts occur and which controller fails first — support will ask, and a precise symptom description speeds up approval. If one controller is out of warranty, replacement individual Quest Pro Touch controllers are sold separately, so you do not need to buy a full pair.
FAQ
Do Quest Pro controllers work with Quest 2 and Quest 3, and do the same fixes apply?
Yes. Quest Pro controllers pair with Quest 2, Quest 3, and Quest 3S headsets, and every fix in this guide applies identically — the pairing button combos and menu paths are the same across those headsets on current Horizon OS.
Why do my controllers disconnect only in PCVR and not standalone?
During PCVR, the headset is streaming over your network while also managing the controller link, and a USB 3.0 Link cable or a congested 2.4 GHz network adds interference exactly where the controllers are vulnerable. Apply Fix 4 first: move the router, switch to 5 GHz, or reroute your Link connection through a USB 2.0 port.
Can I use rechargeable batteries in Quest Pro controllers?
Yes, but use low-self-discharge NiMH cells. Their lower nominal voltage (1.2V vs. 1.5V) means the battery readout dips below the warning threshold sooner, which can look like a power problem when the cells are actually fine. If dropouts track the battery percentage, fall back to alkalines to rule it out.
How do I know if the controller itself is broken?
Swap battery positions and test each controller alone in a simple app. If the same physical controller fails with fresh batteries on a freshly restarted, updated, and even factory-reset headset while the other works flawlessly, the controller hardware is the problem — start a warranty claim.
