You spend twenty minutes dragging your guardian boundary wider so you can actually swing your arms in Beat Saber or duck in a shooter, and the moment you put the headset back on or relaunch the game, the boundary has snapped back to some tiny rectangle you never drew. Sometimes the guardian grid appears in the wrong spot entirely, or the “Confirm Boundary” prompt loops endlessly without committing your changes. Other players see the boundary save fine in one game but reset everywhere else, which is the first clue that this is a settings-sync problem rather than a tracking issue.
This is worth fixing today, not just for convenience. If the Quest believes your boundary is smaller than your play space actually is, it will keep interrupting sessions with “You’re approaching your boundary” warnings, and in extreme cases the system drops you into stationary mode mid-game. Nothing here risks your data — the worst-case fixes involve resetting a guardian history file or clearing a sensor cache — and most readers resolve this in under fifteen minutes. Work through the fixes in order; the first three solve the majority of cases.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Boundary edit was never confirmed — you sketched the grid but didn’t trigger the confirmation step | Open Settings, then Guardian, then Boundary History. If your play space shows “Estimated” instead of a saved entry, it never committed | Easy |
| Cloud settings sync is stale or paused, so your boundary doesn’t propagate between sessions | Settings, then System, then check that Cloud Backup shows a backup within the last few hours | Easy |
| Guardian history file is corrupted | The boundary persists in place but is wrong in the same way every time, even after redrawing it repeatedly | Medium |
| Insufficient lighting or low-contrast room, so floor tracking can’t anchor the map | Boundary behaves erratically and drifts during the same session, and the passthrough image is grainy | Medium |
| Headset software needs a restart to write pending map data | Boundary saves correctly for the rest of one session, then reverts after a full power-down | Easy |
| Crowded or reflective play space confusing the floor scan | Mirrors, glass, or large moving objects (fans, pets) sit inside the area you drew; boundary anchor drifts toward them | Medium to Hard |
Fix 1: Complete the Boundary Confirmation Step Properly
What causes it
The most common cause by far. After you draw the boundary grid, the system requires an explicit confirmation gesture; if you lift the controller away, take the headset off, or the controller loses tracking at that moment, the edit is discarded silently and the old boundary loads next session.
How to check
Press the Oculus button on the right controller, then click Settings, then Guardian, then Boundary History. A properly saved boundary shows a defined footprint with the date you drew it. If the panel instead says your boundary is “Estimated,” your drawing never committed.
What to do
Go to Settings, then Guardian, then Set Up Boundary, then Stationary or Roomscale. Draw your grid, keep your headset on, and when the confirmation prompt appears, point at Confirm and pull the trigger while standing still. Hold still for the full two to three seconds it takes the progress ring to fill. Do not remove the headset until you see “Boundary Set.”
How to undo it
Nothing to undo — but you can redraw anytime via Settings, then Guardian, then Set Up Boundary.
Fix 2: Restart the Headset Properly
What causes it
Map and boundary data is written to storage asynchronously. If you put the headset into standby immediately after redrawing the boundary, the write can be interrupted, and the last known-good map loads on wakeup.
How to check
If the boundary works for the rest of your session but reverts after you take the headset off and come back later, an interrupted write is the likely culprit.
What to do
Hold the power button on the right side of the headset for a full restart (not just lifting it off your face), or go to Settings, then System, then Restart. Once it boots, redraw the boundary, confirm it, and keep the headset powered on and out of standby for at least five minutes before putting it down.
How to undo it
No side effects — restarting is always safe.
Fix 3: Force a Cloud Backup and Sync
What causes it
Guardian settings sync through your account. If cloud backup is disabled or stuck, your boundary can revert to an older synced copy or fail to persist across relaunches, especially if you use multiple headsets on one account.
How to check
Open Settings, then System, then Backup. Check the timestamp of the last backup. If it’s more than a day old or says “Backup failed,” sync is your problem.
What to do
Toggle Cloud Backup off, wait ten seconds, then toggle it back on. Tap Back Up Now. Then redraw and confirm your boundary, and leave the headset connected to Wi-Fi for ten minutes so the new guardian data propagates. On the mobile companion app, check Devices, then Headset Settings, then Guardian to confirm the updated boundary appears there too.
How to undo it
Disable Cloud Backup again in the same menu if you prefer local-only settings, though leaving it on is recommended.
Fix 4: Improve Room Lighting and Remove Reflective Surfaces
What causes it
Inside-out tracking anchors your map using visual features. A dark room, direct sunlight, mirrors, or large glossy panels prevent a stable floor scan, so the system either refuses to save the map or re-estimates it every session.
How to check
Enable passthrough and look at your floor. If it looks noisy, smeared, or the grid jitters when you stand still, tracking quality is the issue. Also check for mirrors, windows with direct sun, or a ceiling fan within your drawn area.
What to do
Turn on even, indirect lighting — a lamp behind you is better than a bare bulb overhead. Close curtains on sun-facing windows. Cover or angle mirrors away from the play space. Then delete the old boundary and redraw it: Settings, then Guardian, then Set Up Boundary, and choose Clear History before redrawing so the system rebuilds the map from scratch.
How to undo it
Return your lighting and furnishings to normal; nothing is permanently changed.
Fix 5: Clear Guardian History and Rebuild the Map
What causes it
The stored guardian history can become corrupted — typically after an interrupted update or a force shutdown. When it’s corrupted, the system keeps loading the broken boundary regardless of what you draw.
How to check
You’ve redrawn the boundary correctly at least three times, confirmed it each time, and it still reverts to the same wrong footprint. That repetition is the signature of a corrupted history entry.
What to do
Go to Settings, then Guardian, then Boundary History, then Clear History. Confirm the prompt. Power the headset off completely (Settings, then System, then Power Off), leave it off for a minute, then power back on and run the full Set Up Boundary flow from scratch, walking the perimeter slowly and keeping the floor visible to the cameras.
How to undo it
There’s nothing to undo — clearing history just removes saved boundaries, which you redraw immediately afterward.
Fix 6: Disable Automatic Stationary Fallback and Re-Test
What causes it
Some system builds attempt to auto-detect a stationary play area and can override your roomscale boundary on launch, particularly in mixed-reality passthrough modes where the boundary is drawn differently.
How to check
Settings, then Guardian. If the system asks you to choose between Stationary and Roomscale repeatedly, or your roomscale boundary is replaced by a small circular one, auto-fallback is fighting you.
What to do
Explicitly select Roomscale in Settings, then Guardian, then Set Up Boundary, redraw, and confirm. Then check that “Show Guardian System” and transition notifications are enabled so you can see when the boundary loads. Avoid switching between passthrough AR apps and standard games immediately after drawing — give the boundary a few minutes to settle before launching a different app type.
How to undo it
Switch back to Stationary via the same menu if you prefer a seated setup.
Fix 7: Update System Software and Reboot to Apply
What causes it
Guardian handling has changed across system updates, and known bugs in older builds could fail to persist boundary edits. Running a stale build keeps you exposed to bugs already patched upstream.
How to check
Go to Settings, then System, then Software Update. If an update is available, it will show here; also verify the update was actually installed, since queued updates on standby sometimes stall.
What to do
Connect to Wi-Fi, keep the headset on the charger, and install any pending update. After it finishes, do a full restart (not standby), then redraw and confirm your boundary. Leave the headset plugged in until the update fully completes — a power loss mid-update is itself a common cause of corrupted guardian data.
How to undo it
System updates can’t be rolled back individually, but there’s no user-facing setting changed by this fix.
Fix 8: Factory Reset as a Last Resort
What causes it
Persistent low-level corruption in the system partition’s map storage that clears cannot touch. This is rare but real after repeated force shutdowns.
How to check
You’ve done Fixes 1 through 7, plus a Cloud Backup restore, and the boundary still reverts every single time. Only then consider this step.
What to do
First, confirm Cloud Backup is on and run a manual backup (Settings, then System, then Backup, then Back Up Now). Then go to Settings, then System, then Reset, then Factory Reset. Alternatively, hold Power and Volume Down from the powered-off state to reach the boot menu and select Factory Reset. Sign back in and restore from backup, then set up your boundary as one of your first actions.
How to undo it
A factory reset cannot be undone, which is exactly why it’s last. Your backup restores apps and most settings, but you will redraw the boundary manually regardless.
If Nothing Works
If the boundary still won’t save after a factory reset, the problem is almost certainly hardware rather than software. A failing camera, degraded controller tracking ring, or damaged proximity sensor can prevent the system from completing a stable floor scan, which it treats as an invalid map and refuses to store. Test the cameras in Settings, then System, then Cameras if your build exposes that panel, and check whether tracking drops repeatedly in the same direction — that points at one specific camera. At that point, contact the manufacturer’s support portal with your headset serial number, approximate purchase date, and a description of the steps you’ve already tried, since the troubleshooting history often accelerates a warranty replacement. Also verify your controller batteries: low controller battery during the boundary confirmation step is an underappreciated cause of failed saves, and swapping in fresh batteries before the confirmation gesture costs nothing.
FAQ
Why does my boundary save but show up in the wrong place?
The map anchored to a different part of your room, usually because lighting changed or furniture moved. Clear Guardian History, improve lighting, and redraw the boundary from where you normally stand.
Can I skip the guardian boundary entirely so there’s nothing to save?
You can reduce it to a stationary setup, but you can’t safely disable it completely in current builds. If the system keeps prompting you, complete a minimal Stationary boundary rather than leaving it unset.
Does a boundary drawn for one headset carry over to a second headset on my account?
Guardian maps are device-specific. Cloud sync carries preferences, not the physical map itself, so each headset needs its own boundary drawn and confirmed.
How often should I redraw my boundary?
Only when you move furniture, change lighting significantly, or notice the grid drifting. Frequent redrawing is a symptom of a tracking problem, not routine maintenance.
