A new Windows 11 update quietly switched on a feature that can reserve up to 50GB of your system drive for automatic recovery snapshots. Microsoft rolled it out with the July 14 KB5101650 security update, and while the number sounds alarming, the reality is far more nuanced—and, for most people, genuinely useful.
What exactly did Microsoft turn on?
The feature is called Point-in-time Restore. It creates full-system snapshots that capture Windows itself, installed applications, drivers, settings, and even your personal files—all in one go. It’s a dramatic step beyond the old System Restore, which protected only system files and the registry while leaving your documents untouched. The new tool works on Windows 11 versions 24H2 and 25H2 (after installing KB5101650, those systems move to builds 26100.8875 and 26200.8875).
Windows will attempt to create a new snapshot roughly every 24 hours and keeps each one for up to 72 hours. If a bad update, buggy driver, or misconfiguration leaves your PC unbootable or unstable, you can roll back to a saved point from inside the Windows Recovery Environment. On an encrypted drive, you’ll need your BitLocker recovery key to proceed.
The feature is not a backup replacement. Snapshots live on the same drive as Windows, so a dead SSD, ransomware, or severe file‑system corruption can still take them out. But for surviving a routine patch‑day mishap, it’s a fast undo button that doesn’t require reinstalling everything from scratch.
The 50GB ceiling: what’s reserved versus what’s actually used
Headlines have zoomed in on that 50GB figure, and it’s easy to see why. By default, Point-in-time Restore can use up to 2% of your system volume, with a hard cap at 50GB—so a 2TB drive could, in theory, see 41GB set aside, and a 4TB or larger drive would max out at the ceiling. Here’s how the numbers break down:
| System drive size | Default maximum snapshot allowance |
|---|---|
| 256GB | ~5.1GB |
| 512GB | ~10.2GB |
| 1TB | ~20.5GB |
| 2TB | ~41GB |
| 4TB or larger | 50GB (capped) |
Those numbers define the limit, not an immediate seizure of space. Microsoft’s documentation confirms that unused capacity remains available for regular files—no 10GB or 50GB partition gets carved out and locked away. The feature relies on the Volume Shadow Copy Service (VSS), the same technology behind System Restore and many backup apps. After the first snapshot, VSS only tracks changed data blocks, so each additional snapshot is incremental. A PC that doesn’t churn through massive file changes might never touch the cap; one that installs and removes large apps daily could eat into it faster. On busy systems, Microsoft warns, usage may eventually reach most of the allowed space.
Two other guardrails matter. If your system drive is smaller than 200GB, Point-in-time Restore won’t automatically enable itself (though you can turn it on manually). And if free space ever drops to 20GB or less, Windows will purk older snapshots to relieve the pressure. That means your PC will prioritize breathing room for new downloads over keeping stale recovery points.
It’s also worth knowing that Point-in-time Restore shares VSS storage with other tools. If you already run third‑party snapshot software or rely on System Restore’s classic restore points, the same pool is divided among them. The new feature doesn’t get a private, isolated allocation.
Who gets it, and when did it arrive?
Microsoft first shipped Point-in-time Restore to Windows Insiders in November 2025. It reached the Release Preview Channel on June 12, 2026, with builds 26100.8728 and 26200.8728, then landed in the optional June preview update (KB5095093) before becoming part of July’s mandatory security update.
Enablement depends on your edition and management:
- Windows Home and unmanaged Windows Pro (not domain‑joined, not enrolled in endpoint management): On by default, provided the system volume is at least 200GB.
- Windows Enterprise, Education, domain‑joined Pro, and endpoint‑managed Pro: Off by default for now. Microsoft plans to flip the default for managed systems with Windows 11 version 26H2, giving IT departments time to test storage behavior, recovery workflows, and BitLocker‑key access.
Even after installing KB5101650, the feature may not appear immediately on every eligible PC. Microsoft uses gradual rollout mechanisms, so some users could see the new controls appear days or weeks later.
How to check and control it
You can see the feature’s status and current storage usage under Settings → System → Recovery → Point-in-time Restore. A “View or edit” link lets you inspect existing snapshots and see exactly how much space they’re consuming. Home and Pro users can toggle the feature on or off and adjust the storage allowance. Enterprise editions get additional controls over snapshot frequency and retention.
If you turn the feature off, Windows stops creating new snapshots. Microsoft notes that existing restore points might linger until their 72‑hour expiry or until the system needs the space, so don’t expect an instant, matching gigabyte‑for‑gigabyte return of free capacity. A deliberate “remove all snapshots” option would be a welcome addition; for now, the straightforward path is to keep the feature on unless you’re certain you won’t use it.
Recovering with Point-in-time Restore: steps and sharp edges
When you need it, boot into the Windows Recovery Environment (the same blue‑screen menu that appears after repeated boot failures or when you hold Shift while restarting). Choose Troubleshoot → Point-in-time Restore. On a BitLocker‑protected PC, you’ll have to provide the recovery key before selecting a snapshot.
Microsoft’s support documents highlight several current limitations and gotchas:
- Files encrypted with EFS can prevent restoration from completing.
- The recovery process needs free space on the drive roughly equal to the size of the stored snapshots; if your drive is critically full, you may need to free up room first.
- Interrupting a restore (power loss, forced reboot) can leave Windows unbootable.
- After rolling back, recently installed security updates may be gone, so Windows Update should be run immediately.
- Outlook users might need to rebuild an offline cache (
.ostfile). - Windows Recall can be disabled after a restore until the feature re‑confirms hardware compatibility.
Administrators should pay particular attention to the BitLocker flow. A recovery option inside WinRE is useless if the help desk can’t retrieve the key for the system volume. Enterprises should test that path extensively before Point-in-time Restore becomes the default for managed devices.
Should you leave it on? A practical decision guide
For most home users on a 512GB or larger SSD, the trade‑off is clear. Losing roughly 10GB of dynamic headroom—space that Windows will reclaim when it needs to—is a small price for the ability to undo a bad Patch Tuesday in minutes. If you’ve ever spent an evening reinstalling Windows and all your apps because a driver update went sideways, the appeal is obvious.
Power users who already maintain frequent system‑image backups might be tempted to toggle it off and reclaim a few gigabytes. Before doing so, consider that even the best backups are only as current as your last run. A snapshot that’s at most 24 hours old can save hours of work that a weekly image backup would miss. The feature also doesn’t interfere with those backups; it just sits alongside them as an extra, local safety net.
For IT departments, the calculus is different. Until 26H2 arrives, managed PCs won’t have the feature on unless someone explicitly turns it on. That gives time to evaluate storage impact, to ensure BitLocker recovery keys are accessible to support staff, and to check compatibility with existing VSS‑based tools like DPM or third‑party rollback suites. If your organization already forces a robust backup solution, you may eventually choose to disable the feature globally through policy—though for field laptops that rarely touch the corporate network, it could be a valuable complement.
The bottom line: Point-in-time Restore isn’t secretly confiscating 50GB from every Windows 11 PC. Most systems will see a ceiling of 5GB to 20GB, and actual usage rarely spikes to that limit. It’s a short‑term recovery tool, not a backup, and it’s enabled by default because Microsoft is betting that a few gigabytes of local snapshots are worth avoiding hours of troubleshooting—and that’s a bet most people should take.
What to watch next
Microsoft’s documentation signals that the default will expand to managed editions with version 26H2, so enterprise admins should begin testing now. For home users, the next milestones will be seeing how gracefully the feature handles crowded drives during a major feature update (when tens of gigabytes of temporary files can appear). The real test, though, will come in the wild—when the first widespread broken update sends users scrambling for WinRE and finding that a 10GB rewind point saved their week.