Microsoft has officially rolled out its point-in-time restore feature for Windows 11, providing users and IT administrators with a reliable method to revert their PCs to a stable state following problematic updates, driver issues, or application corruption. This new capability is now accessible to all Windows 11 client PCs operating on version 24H2 and later, encompassing the Windows Enterprise, Pro, and Home editions.
Enhancing Windows Resiliency
Positioned as a key component of Microsoft’s broader initiative to enhance Windows resiliency, this feature aims to minimize downtime when devices become unstable or unbootable. Lia Vargas from Microsoft emphasized the importance of recovery speed, stating, “Every minute of downtime matters,” highlighting the challenges IT teams face during extensive troubleshooting or complete device rebuilds.
The point-in-time restore function automatically generates local restore points on a set schedule, capturing essential elements such as the Windows operating system, installed applications, system configurations, settings, and local user files. By default, these restore points are created every 24 hours, stored for up to 72 hours, and limited to 2% of disk space, although certain settings can be adjusted for Enterprise systems.
Microsoft aims for this feature to enable users to “recover in minutes instead of hours,” particularly when system changes lead to instability. While it shares some underlying technology with the older System Restore feature, point-in-time restore offers a more comprehensive solution, including user files and being integrated directly into Windows Settings. It also employs stricter retention and cleanup policies, tailored for modern device management.
Since its public preview, point-in-time restore has been activated on over 2 million devices. The general availability release expands its reach to both consumer and commercial editions, introducing configuration service providers for remote setup, enhanced visibility of restore points, disk usage reporting, and updated documentation.
The default settings for point-in-time restore vary by device type. For instance, it is enabled by default on Windows Home devices and unmanaged Windows Pro devices, provided the OS volume is at least 200 GB. Conversely, it remains disabled by default for Windows Enterprise and Education devices, as well as domain-joined or organization-managed Windows Pro systems, at least until the upcoming Windows 11 version 26H2.
Currently, users must initiate restores locally via the Windows Recovery Environment. The process involves navigating to Troubleshoot, selecting Point-in-time restore, entering the BitLocker recovery key if necessary, choosing a restore point, and confirming the action. However, users should be aware that any changes made after the chosen restore point, including files, applications, and settings, will be permanently lost.
Looking ahead, Microsoft plans to introduce remote initiation capabilities through Intune recovery, which would facilitate a more scalable approach for organizations to restore affected devices during widespread incidents.
This announcement coincides with preparations for Windows 11 version 26H2, the next annual feature update. Microsoft assures that this update will maintain a “predictable, low-disruption update experience” for organizations and IT professionals. The 26H2 version will utilize the same platform and servicing strategy as recent Windows 11 releases, allowing devices on versions 24H2 or 25H2 to transition to 26H2 via a “small enablement package” rather than a complete OS overhaul.
For those testing the update, it is currently available through the Windows Insider Program’s Experimental channel, with general availability anticipated in the latter half of 2026. Organizations are encouraged to validate their applications, policies, and infrastructure in preparation for the rollout.
It is worth noting that devices running Windows 11 version 26H1 will not be able to upgrade directly to 26H2 due to differences in the underlying Windows core. Instead, Microsoft has outlined a pathway for these systems to transition to a future Windows release.
For further details, please refer to the Microsoft blog.
