Question
Feature Update Rollback Window: Extending the Windows.old Retention Boundary
Rey Lane
0 reputation · 08 Dec 2021, 11:48 UTC
74.4K views
Loading…
0 reputation · 08 Dec 2021, 11:48 UTC
After a Windows 11 feature update, the operating system preserves the previous build in the Windows.old folder and exposes a rollback path through Settings → System → Recovery → Go back. By default, this recovery option remains available for 10 days before Windows automatically removes the Windows.old directory. Administrators can modify this behavior through Group Policy or MDM, but current documentation indicates these mechanisms support only a one-time extension of the uninstall deadline, capped at 60 days.
The unresolved boundary concerns whether this retention period can be extended indefinitely or made permanent without manual intervention. Organizations that need a longer rollback horizon for compatibility testing or staged deployments face uncertainty about whether the 60-day cap represents a hard technical limit or a configurable policy threshold. Additionally, it remains unclear whether extending the deadline through policy prevents the automatic cleanup of Windows.old entirely, or simply delays the deletion while the underlying version schema change from the feature update remains in effect.
Can the Windows.old folder be retained permanently through supported Group Policy or MDM configuration, or does Windows 11 enforce a hard deletion boundary regardless of the configured uninstall deadline? If the 60-day extension is applied, does the rollback option remain functional for the full duration, or does the feature update's schema changes introduce a separate expiration constraint? What is the supported method for maintaining rollback capability beyond 60 days without re-imaging or manual folder preservation?
35275 reputation · 08 Dec 2021, 17:08 UTC
No supported Group Policy or MDM configuration can make Windows.old permanent in current Windows 11. The available policy sets a maximum folder age, and the documented cap is 60 days. Values above 60 are ignored. After that boundary, Windows automatically removes Windows.old and the rollback option disappears. There is no supported way to keep the built-in rollback path functional beyond 60 days without manually preserving the folder or re-imaging.
Documented behavior: The Windows Update policy “Specify maximum age of the Windows.old folder” delays cleanup until the configured age is reached, up to 60 days. When the limit expires, Windows removes the folder.
Uncertain or build-dependent: Whether Settings → System → Recovery → Go back remains visible for the full 60 days, or whether component-store schema changes from the feature update impose a separate earlier expiration, is not clearly separated in public documentation. Treat the 60-day cap as a hard technical boundary for supported configuration until verified on your target build.
windows11gpedit.msc and go to Computer Configuration → Administrative Templates → Windows Components → Windows Update.gpupdate /force from an elevated command prompt.HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\MaximumAgeOfWindowsOld is set to 60.C:\Windows.old exists and that Go back appears under Settings → System → Recovery. Plan for automatic removal near day 61.For rollback beyond 60 days, manually copy Windows.old to another volume before cleanup. Manual preservation retains the files but does not guarantee the graphical rollback path will still function.
Version assumption: This applies to current Windows 11 releases. Windows 11 Home does not include gpedit.msc; use the registry value or equivalent MDM catalog where supported. This guidance should be verified against your specific build because Microsoft may change the cleanup policy in future updates.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.