/
/

How to Manage the Windows 11 Rollback Period to a Previous Windows Version

by Stela Panesa, Technical Writer
How to Manage the Windows 11 Rollback Period to a Previous Windows Version blog banner image

Instant Summary

This NinjaOne blog post offers a comprehensive basic CMD commands list and deep dive into Windows commands with over 70 essential cmd commands for both beginners and advanced users. It explains practical command prompt commands for file management, directory navigation, network troubleshooting, disk operations, and automation with real examples to improve productivity. Whether you’re learning foundational cmd commands or mastering advanced Windows CLI tools, this guide helps you use the Command Prompt more effectively.

Have you ever upgraded from Windows 10 to 11 only to encounter more bugs and even slower startup times? Don’t worry; you can roll back to Windows 10 within 10 days.

Once you’ve upgraded to Windows 11, your computer keeps a copy of the previous Windows version in the Windows.old folder you can use to roll back to Windows 10. However, the file will only be available for up to 10 days. Afterwards, your system will automatically delete it.

The good news is that there are methods for extending the Windows 11 rollback period to a maximum of 60 days.

How to extend the rollback period after upgrading to Windows 11

📌 Prerequisites:

  • Administrative Privileges: You need administrative rights to extend the rollback period for a previous Windows version.
  • Windows.old Folder: You need to have the Windows.old folder on your computer; otherwise, rollback will not be possible.

📌 Recommended deployment strategies:

Click to Choose a Method 💻

Best for Individual Users

💻💻💻

Best for Enterprises

Method 1: Check the current rollback period using DISM
Method 2: Change the rollback period using DISM
Method 3: Configure the rollback period via Registry Editor

💡 Note: These methods only apply to in-place upgrades, not clean installations.

Method 1: Check the current rollback period using DISM

📌 Use Case: This method is best for individual users who want to check how many days they have left in the rollback period.

Steps:

  1. Open Command Prompt or PowerShell as Administrator.
  2. Enter the following command: DISM /Online /Get-OSUninstallWindow
  3. The output will show the current rollback period in days.
    • If you receive “Error 1168: Element not found,” then the rollback period has expired, and the Windows.old folder has been removed.

Method 2: Change the rollback period using DISM

📌 Use Case: This method is ideal for extending rollback periods across multiple Windows devices.

Steps:

  1. Open Command Prompt or PowerShell as Administrator.
  2. To set the rollback period between 2 and 60 days, enter:
    • DISM /Online /Set-OSUninstallWindow /Value:<Number_of_Days>
  3. Replace <Number_of_Days> with your desired value. For instance, if you want to extend the limit to 30 days:
    • DISM /Online /Set-OSUninstallWindow /Value:30
  4. A confirmation message will pop up indicating that the operation is complete.

Method 3: Configure the rollback period via Registry Editor

📌 Use Case: This method allows you to adjust the rollback period manually.

Steps:

  1. Press Win + R, type regedit, and press Enter to open the Registry Editor.
  2. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\Setup
  3. In the right pane, look for a DWORD value named UninstallWindow.
    • If the value doesn’t exist, create it:
      1. Right-click on the right pane, selecting New > DWORD (32-bit) Value
      2. Name it UninstallWindow.
  4. Double-click on UninstallWindow and set the value to:
    • Select Decimal as the base.
    • Enter a value between 2 and 60 to set your desired rollback period in days.
  5. Click OK to save the changes.
  6. Close the Registry Editor and restart the computer to apply the changes.

Once you’ve applied the changes, execute DISM /Online /Get-OSUninstallWindow to verify the updated rollback period.

⚠️ Warning: Editing the registry can have unintended consequences. Proceed with caution and back up the registry before making any changes.

Notes on managing the rollback period for previous Windows versions

There are a few things you should consider when extending your system’s rollback period, including:

  • You must change the rollback period within the initial 10-day limit. Once this period is over, the Windows.old folder will be automatically deleted, and rollback will no longer be possible.
  • Extending the rollback period will not prevent the Windows.old file from being deleted during disk cleanup operations. You must configure your system cleanup tools accordingly.
  • There are no Group Policy settings available to configure the rollback period. You need to set it manually using one of the methods we’ve outlined above.

⚠️ Things to look out for

Keep these pitfalls in mind when following our guide.

Risks Potential consequences Reversal
Running Command Prompt or PowerShell without administrator rights. The commands will fail silently. Make sure you sign in to your system as an administrator before running Command Prompt or PowerShell.
Incorrect registry configuration Adding the wrong keys to the Registry can cause system instability. Back up your registry before making any changes.
Failing to restart the system. Changes will not take effect. Once you change the rollback period, restart your computer and verify the new timeframe by executing DISM /Online /Get-OSUninstallWindow.
Incorrect command syntax Command may fail silently. Double-check the syntax of your commands before running them.

Quick-Start Guide

NinjaOne offers several ways to manage Windows version updates

1. Patch Management Options:

In NinjaOne, you can find approval settings for “Feature Updates“.

You can choose to:

  • Reject: Block the patch from installing
  • Approve: Push the patch to managed machines
  • Manual: Choose whether to reject or approve when found

2. Patch Uninstallation:

  • NinjaOne allows uninstalling Windows patches that support rollback
  • You can uninstall patches from the Installed patch list
  • There’s a column indicating whether a patch supports uninstalls

Get flexible recovery options by mastering how to extend the rollback period for previous Windows versions

Extending the rollback period for previous Windows versions gives you greater flexibility in system recovery. It ensures you have enough time to recover an earlier Windows version instead of being confined to the default 10-day window.

Using tools like Command Prompt, PowerShell, and the Registry Editor, you can easily extend the rollback timeframe to a maximum of 60 days. Just remember that you need to make this adjustment before your computer automatically deletes the Windows.old folder.

Related topics:

FAQs

As mentioned earlier, Windows 11 has a 10-day rollback grace period. Once this timeframe is over, you won’t be able to go back to the previous Windows version.

If you want to restore a previous version of Windows 11, you can use the “Go back” feature in the Settings app. However, remember that this option is only available for 10 days after upgrading your system.

To restore your PC to an earlier date, you must access the System Restore feature via the Advanced Startup menu or the Control Panel. This feature allows you to safely restore your system to a previous state.

You might also like

Ready to simplify the hardest parts of IT?

NinjaOne Terms & Conditions

By clicking the “I Accept” button below, you indicate your acceptance of the following legal terms as well as our Terms of Use:

  • Ownership Rights: NinjaOne owns and will continue to own all right, title, and interest in and to the script (including the copyright). NinjaOne is giving you a limited license to use the script in accordance with these legal terms.
  • Use Limitation: You may only use the script for your legitimate personal or internal business purposes, and you may not share the script with another party.
  • Republication Prohibition: Under no circumstances are you permitted to re-publish the script in any script library belonging to or under the control of any other software provider.
  • Warranty Disclaimer: The script is provided “as is” and “as available”, without warranty of any kind. NinjaOne makes no promise or guarantee that the script will be free from defects or that it will meet your specific needs or expectations.
  • Assumption of Risk: Your use of the script is at your own risk. You acknowledge that there are certain inherent risks in using the script, and you understand and assume each of those risks.
  • Waiver and Release: You will not hold NinjaOne responsible for any adverse or unintended consequences resulting from your use of the script, and you waive any legal or equitable rights or remedies you may have against NinjaOne relating to your use of the script.
  • EULA: If you are a NinjaOne customer, your use of the script is subject to the End User License Agreement applicable to you (EULA).