Never Delete These Windows Folders by Hand WinSxS Installer and System32
Every 'I freed 20 GB and now Windows Update fails' story starts in one of three folders. They look like bloat because they are large, cryptic and full of files with names you do not recognise. They are, in fact, load-bearing. This page names them, explains what breaks, and points at the one supported cleanup that exists for the biggest of the three.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 6 minute read
🎥 Watch the video for the safe cleanup — this page is the fence around the parts of it you must never improvise
The pattern to understand: Windows keeps spare parts of itself on purpose. Updates need old components to uninstall cleanly, installers need their patch caches to repair apps, and the system folder is quite literally the operating system. Deleting these folders never produces an error on the day you do it. It produces a PC that cannot update, cannot repair and eventually cannot boot — weeks later, when the connection to your cleanup is invisible.
Folders that break Windows when emptied by hand
C:\Windows\WinSxS — component store NEVER BY HANDLooks huge
C:\Windows\Installer — patch cache NEVER BY HANDGBs of MSI files
C:\Windows\System32 — the OS itself NEVERThe system
👆 The three red rows are the whole page. Everything else on a drive can be managed; these three can only be damaged.
1
WinSxS — the Component Store, and Why Its Size Lies
The folder at C:\Windows\WinSxS holds every version of every Windows component, so updates can be applied and removed safely.
Explorer exaggerates its size: many of its files are hard links — the same data counted in several places at once — so the folder is smaller than it looks
Delete from it and the first symptom arrives with the next update, which fails because a component it must replace or verify is gone
Servicing tools like SFC then cannot repair the damage either, because their spare parts were the thing deleted
The only supported trimming is Windows' own component store cleanup through DISM, which removes only genuinely superseded versions — a dedicated page in this cleanup series covers that route; the point here is that hand-deleting is never it
2
Windows Installer — the Patch Cache Apps Need to Heal
The hidden folder C:\Windows\Installer holds the installer and patch files of everything installed with Windows Installer technology:
When an app offers Repair, or an update patches it, the original files come from this cache
Empty it and apps begin failing to update or uninstall — the uninstaller itself asks for files that no longer exist
Office-class suites are the classic victims; the fix at that point is a full reinstall of the suite, if it will even start
There is no supported way to shrink this folder. If it is enormous, the cause is orphaned patches from long-removed software — a specialist cleanup, not an Explorer session
3
System32 — Yes, People Really Do This
It should not need saying, and yet forums are full of it:
C:\Windows\System32 is the core of the operating system — the kernel's libraries, drivers and tools
Anything deleted here is not 'freed space', it is a removed organ; symptoms range from broken features to a PC that cannot boot
The same applies to its siblings — SysWOW64, the drivers folder, and the Fonts folder people occasionally 'tidy'
If a guide or video ever tells you a System32 file is a virus to delete by hand, close it — real malware removal uses security software, not Explorer
4
Program Files — Uninstall, Do Not Amputate
The fourth folder is not Windows itself, but the rule protects the same principle:
Deleting a program's folder leaves its registry entries, services, scheduled tasks and uninstall record behind
The orphaned service then errors at every boot, and reinstalling the same program can fail over the remains
Uninstalling from Settings → Apps removes the folder and the registrations together — that is the only delete this folder understands
5
The Safe Instinct to Build Instead
Replace the dangerous reflex with a reliable one:
Inside the Windows folder, nothing is junk — whatever its size, whatever a forum said
Space inside Windows is reclaimed only through Windows' own offers: the Temporary files page, update cleanup, and the supported DISM component cleanup
Your real wins were never in there anyway — they are your apps, your games, your libraries and your leftovers, as the other pages in this series show
🔴 The cruellest part of these deletions is the delay. The PC works fine for weeks after WinSxS or the Installer cache is emptied — until the next update, repair or uninstall reaches for a file that is not there. By then nobody connects the failure to the cleanup, and the 'fix' that follows is usually a full Windows reinstall.
🎥 Watch the Complete Video Guide
See the full cleanup done live on a real full C drive — the scan, the safe deletes and the final free space, step-by-step.
WinSxS shows 18 GB in Properties. Is it really using 18 GB?
Almost certainly not. Because of hard links, Properties counts the same file data multiple times — once for WinSxS and once for the system folder it is linked into. The true extra space is considerably smaller, which is another reason the honest cleanup returns less than people expect — and why chasing the fake number by hand is doubly pointless.
A cleaner tool offers to delete the Installer folder and orphaned patches. Safe?
Distrust it. A tool that surgically removes only patches belonging to software that no longer exists is performing the most delicate operation in Windows maintenance, and getting it wrong breaks repairs for everything else. The space it offers is rarely worth the risk on a working machine.
I already deleted files from one of these folders. What now?
Act before the damage is asked to perform: run an online DISM health restore and SFC scan from an admin terminal so Windows can repair from Windows Update while it still can, confirm Windows Update completes a full cycle, and take a backup of your data. If updates already fail, an in-place repair install of Windows is the honest recovery.
This guide is based on the Technical Anshu C drive cleanup video • Stuck on any step? Ask in the video comments — you will get a reply there 🙏