The Change
Windows 11 version 24H2 now automatically deletes System Restore points after 60 days via update KB5060842. Previously, restore points persisted based on allocated disk space - typically 5-10% of drive capacity. The new limit applies regardless of available storage.
What This Means in Practice
System Restore creates snapshots of system files, drivers, and registry settings for rollback after failed updates or driver installations. Windows generates these automatically or users create them manually via "Create a restore point" in System Settings.
The 60-day window works for consumer PCs with frequent updates. It's problematic for enterprise environments where quarterly patching cycles mean older restore points might be the only clean rollback option after a deployment goes wrong.
The Enterprise Angle
Microsoft is simultaneously rolling out Point-in-Time Restore in System > Recovery for enterprise admins. This feature offers configurable retention periods and creation frequency through Volume Shadow Copy Service (VSS). It requires UEFI/Secure Boot, standard for Windows 11.
Notably, Point-in-Time Restore doesn't pre-allocate disk space - it uses up to the admin-defined maximum. That's better resource management than the old percentage-based approach, but the consumer-side 60-day hard limit remains.
The Pushback
Forums show IT teams attempting unsupported registry modifications to extend retention. Microsoft hasn't documented these, and they risk system instability. No official extension method exists.
The real question is whether Microsoft views this as a consumer protection measure (preventing bloated restore point directories) or a gentle push toward enterprise tooling for organizations that need longer retention.
Trade-offs
Recommended allocation remains 10GB for multiple restore points. Windows 11 requires 64GB minimum storage. The 60-day limit prevents runaway disk usage on consumer devices but removes a safety net for cautious enterprise deployments.
We'll see if feedback changes Microsoft's approach. History suggests enterprise customers get heard when deployment blockers emerge.