Can You Safely Delete the Windows.old Folder?

A few days after a Windows feature update, the C drive is suddenly 20GB fuller and a folder called Windows.old has appeared in the root. It is large, it is clearly leftover, and deleting it is tempting.

It is also the only thing standing between you and a clean reinstall if the new version turns out to have broken your printer driver, your VPN client or your audio interface. Windows keeps it for ten days precisely so you have a way back.

The short version: yes, you can delete it, and there is a correct way to do so that takes two minutes. There is also a wrong way that leaves you with an undeletable folder and no rollback.

What Windows.old actually contains

A feature update does not patch Windows in place. It installs a complete new copy of the operating system alongside the old one, migrates your settings, user profiles and installed applications across, and then renames the previous installation to Windows.old.

Inside it you will find:

The size depends on how much was installed before the update. A clean system produces 12–15GB; a heavily used one with large program installations can reach 30GB or more.

Your personal files were copied forward, not moved. The versions in Windows.old\Users are duplicates of what is already in your current profile. That is worth confirming before you delete — open C:\Windows.old\Users\[your name] and spot-check Desktop and Documents against your live folders.

The 10-day clock

From the moment the feature update completes, Windows gives you ten days to go back. During that period, Settings → System → Recovery shows a Go back button. After ten days it vanishes, because Windows.old has been automatically deleted by a scheduled task.

That is the trade you are making. Deleting the folder on day two frees 20GB and costs you eight days of rollback insurance.

Extending the window, if you need more time

If you suspect you may need to roll back but want longer to decide, you can extend it before it expires. Open Terminal (Admin) and run:

DISM /Online /Set-OSUninstallWindow /Value:30

The value is in days and the maximum is 60. To check the current setting:

DISM /Online /Get-OSUninstallWindow

This only works while the folder still exists. Once Windows has cleaned it up, the rollback path is gone for good and the only route back is a clean install from media.

How to delete it properly

Two supported routes. Both do the same thing; use whichever you find first.

Route 1: Settings (Windows 11 and 10)

1. Settings → System → Storage.
2. Wait for the calculation to finish, then click Temporary files.
3. Find Previous Windows installation(s) in the checklist and tick it.
4. Check nothing else is ticked that you did not intend — Downloads appears in this same list and contains your actual downloaded files.
5. Click Remove files.

It takes a few minutes and the drive space appears once it finishes. There is no progress detail; let it run.

Route 2: Disk Cleanup

The older tool still works and is sometimes faster to reach.

1. Press Win+R, type cleanmgr, press Enter.
2. Select the C drive, click OK.
3. Click Clean up system files — this is the step people miss. Without it, the previous-installation entry does not appear at all.
4. Select C again and wait for the rescan.
5. Tick Previous Windows installation(s). You may also see Windows Update Cleanup and Windows upgrade log files — both are safe.
6. Click OK, then Delete Files.

This is irreversible. Once removed, the rollback option is gone and you cannot restore the folder. Make sure the current version has been running well for a few days first — in particular, test printing, any VPN, external audio or capture hardware, and anything with a kernel driver.

Why not to delete it manually

Attempting to delete Windows.old in Explorer goes badly in a specific way.

The folder’s contents are owned by NT SERVICE\TrustedInstaller, not by you. Explorer will throw permission errors on most of it. People then work around this by taking ownership with takeown and granting themselves full control with icacls, which does eventually let the deletion proceed — but it is slow, it frequently fails partway through on long paths, and the half-deleted remains are no longer recognised by Disk Cleanup.

The result is a folder that still occupies several gigabytes, cannot be removed by the supported tools, and needs manual permission work to clear. The Settings route does the whole thing in one pass with the correct privileges.

What not to do

• Do not drag Windows.old to the Recycle Bin. Even if it appears to work, the deleted data moves into the bin on the same drive and frees nothing until the bin is emptied.
• Do not delete it the same day the update installed. Give the new version at least a few days of normal use. Driver and peripheral problems rarely show up in the first hour.
• Do not run takeown and icacls across the whole folder to force a manual delete. Use the supported tools.
• Do not use a third-party “uninstaller” or PC cleaner for this. The function is built into Windows and the cleaners add nothing except a background process.
• Do not confuse it with $Windows.~BT or $Windows.~WS. Those are update staging folders. They are also safe to remove, but through the same Disk Cleanup checklist, not by hand.

Afterwards

Clearing Windows.old plus Windows Update Cleanup in the same pass typically recovers 20–35GB on a machine that has just taken a feature update. It is the single largest reclaimable item on most Windows drives.

If the drive is still tighter than you would like afterwards, the next candidates are System Restore allocation, the hibernation file and the OneDrive cache — all covered in how to free up disk space on Windows and, for the detective work, in C drive full for no reason.

And if the machine has felt sluggish since the update rather than merely full, that is a different problem with a different fix — see Windows 11 slow after an update.