Feature Update Rollback Window: Extending the Windows.old Retention Boundary

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?