Extend your time to rollback on the latest Windows 11 Update (22H2)

  • 27 October 2022
  • 5 replies

Userlevel 6
Badge +5

Microsoft recently released the Windows 11 2022 Update (22H2) followed by a 'moment' update which introduced new features to the OS, including tabs in File Explorer.

If you’ve been reading our coverage of the problems that users have found with the Windows 11 2022 Update you might be concerned about installing it, but don’t worry you can roll back the operating system to your previous build. There’s just one problem -- Microsoft only gives you 10 days to do this, which is hardly any time at all. We think you need longer, much longer, so we’ll show you how to extend this allowance to 60 days.




The following guide only works if you’re still within the original 10-day rollback period. To check if you are, go to Settings and click on System, then scroll down to Recovery. If you see a Go Back option you’re fine. If it’s greyed out then you are stuck with the version of Windows 11 that you’re currently running.

Assuming you can see the Go Back option, click the Start button, type CMD into the search box and click on Run as Administrator on the right.

In the Command Prompt window type:

DISM /Online /Get-OSUninstallWindow

Hit enter and next to the Uninstall Window line it should say 10. This means you have ten days to roll back the update. That’s not enough, so let’s change it.

Still in the Command Prompt, enter the following (note the command this time around is Set not Get):

DISM /Online /Set-OSUninstallWindow /Value:60

Hit enter and the rollback time should be increased to two months. To check it is, type in the original command and hit enter:

DISM /Online /Get-OSUninstallWindow

This is a simple but very useful trick and one we like to perform after every Windows Update just to make sure we have all the time we need to be prepared for any potential problems that arise after ten days.


Full article here: https://betanews.com/2022/10/21/windows-11-2022-update-rollback-hack/

5 replies

Userlevel 6
Badge +4

@tmcmullen  thank you, I have forwarded this to our support teams. Failsafe patching is the solution here, as then you can choose to keep your recovery point of your machine before you patch it. 🙂 Easy roll back later should you want to do so, and you can set the retention you want. 

Userlevel 7
Badge +4

This is a brilliant tip, thank you for sharing! Passed to the team!

Userlevel 7
Badge +4

Can anyone actually enlighten me as to why they have to put a time limit on this sort of thing? I assume there is some logical reason but I can't seem to think of anything 

Userlevel 7
Badge +22

Thank  you for this article. While I may be a Mac user most of the time, I do have two Windows 11 machines for some other activities and clients who still use Windows as well. 

And to second James’ quesitons, why is there a time limit? If they had to have a time limit, I would assume it would be up to the next update, which obviously requires this one before moving forward. Although they used to do roll up updates which I do not see as often these days. 

Userlevel 7
Badge +4

Maybe just a uniformity thing, keeping everyone on the same level (Or as close to it as possible)? Either way it still seems overkill