Your C: drive doesn't need a new SSD. It needs one command — and it's already built into Windows.
Every few months, the same message shows up on machines I manage: "Your C: drive is running out of space." If you're trying to free up C drive space in Windows 11, the good news is that you usually don't need a bigger SSD or a third-party "cleaner" app — Windows already ships with a command-line tool that can safely reclaim several gigabytes in one run.
I'm talking about the DISM component cleanup commands, which target a folder most users have
never heard of: WinSxS.
On systems that have gone through years of Windows updates, this single cleanup can recover anywhere from a few
gigabytes up to 10–15 GB — without deleting anything your system actually needs.
In this guide, I'll walk you through the full process I use as an IT infrastructure admin who has maintained Windows machines since 2008: first the quick wins most guides cover, then the safe DISM commands, the dangerous variant you should think twice about, and the mistakes that turn a cleanup session into a support ticket.
I'm Mostafa Amaan, and on Valley4Techs I write practical Windows and infrastructure guides built on real-world experience. Open an elevated terminal — let's reclaim some space.
How Do I Free Up C Drive Space in Windows 11?
DISM /Online /Cleanup-Image /StartComponentCleanup.
This safely trims superseded Windows update files from the WinSxS component store, often freeing several GB (up
to 10–15 GB on older installations) without removing anything Windows needs to run.
That's the headline command. But before you run it, it helps to understand what's actually eating your C: drive, because a proper cleanup works in layers. Here's the order I follow on every machine:
- The usual suspects — Recycle Bin, Downloads folder, temporary files.
- Built-in cleanup tools — Disk Cleanup and Storage Sense.
- Big background files — like
hiberfil.sysif you don't use hibernation. - The component store (WinSxS) — cleaned safely with DISM, covered in detail below.
A free tool like WizTree or the built-in Storage settings page will show you exactly where your
space went. One warning from experience: never manually delete anything inside
C:\Windows
— especially the WinSxS folder. We'll get to why in a moment.
If your PC has been feeling sluggish along with being full, it's worth reading our guide on why a PC slows down even when the hardware is fine — low disk space is one of the most common hidden causes.
What Is the WinSxS Folder and Why Does It Keep Growing?
WinSxS
(short for Windows Side-by-Side) is the component store of Windows. It's where
the operating system keeps multiple versions of the same system file side by side, so different applications can
use different versions without conflicts breaking.
Here's the catch: every time Windows Update installs a new version of a system component, the old version often stays in the store. Why? So that you can roll back a problematic update later. On a machine that has received updates for years, those superseded components quietly pile up into gigabytes of dead weight.
WizTree's view of WinSxS — the reported size is inflated by hard links, so don't trust it as "recoverable" space.
This is also why the folder must never be cleaned by hand. Deleting files from WinSxS directly can break Windows Update, System File Checker, and even the ability to boot. The only supported way to shrink it is the DISM (Deployment Image Servicing and Management) command family — and that's what we'll use next.
Step 1: Analyze the Component Store First
Before cleaning anything, measure. DISM ships with an analysis mode that tells you exactly how large your component store is and whether a cleanup is worth your time. Open Terminal (Admin) — right-click the Start button, or press Win + X and choose Terminal (Admin) — then run:
Command Prompt (Admin)
DISM /Online /Cleanup-Image /AnalyzeComponentStore
After a minute or so, you'll get a summary that includes the actual size of the component store, whether Windows Explorer's file count is misleading you (remember those hard links), and the line everyone cares about: "Component Store Cleanup Recommended: Yes or No."
The AnalyzeComponentStore output: note the "actual size" line and the cleanup recommendation at the bottom.
Step 2: Run the Safe Cleanup Command
If the analysis recommends a cleanup, this is the command to run:
Command Prompt (Admin)
DISM /Online /Cleanup-Image /StartComponentCleanup
Here's what each part does:
| Flag | What It Does |
|---|---|
| /Online | Targets the currently running Windows installation, not an offline image. |
| /Cleanup-Image | Tells DISM you want servicing and repair operations on that image. |
| /StartComponentCleanup | Removes superseded versions of components from the WinSxS store, keeping only the most recent version of each so you can still roll back the latest update. |
Expect the process to take anywhere from a couple of minutes to twenty, depending on how stale the store is. Don't interrupt it, and don't shut the machine down mid-cleanup. When it finishes, re-run the analyze command from Step 1 — seeing the "actual size" drop is oddly satisfying.
Set realistic expectations, though. On a well-maintained Windows 11 machine, I've seen this recover only a few gigabytes; on a system that has taken years of cumulative updates without ever being cleaned, gains of 10–15 GB are realistic. The result depends entirely on how much superseded material your installation is hoarding.
Should You Use the /ResetBase Flag for Even More Space?
DISM offers a more aggressive variant of the cleanup command:
Command Prompt (Admin)
DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase
My rule of thumb, shaped by managing Windows machines in production environments: run the safe /StartComponentCleanup routinely, and reserve /ResetBase for machines in a known-good state — ideally right after a big feature update has proven stable for a few weeks, and always with a recent backup image on an external drive. The extra gigabytes are rarely worth the lost rollback option on a machine you rely on daily.
A related flag, /SPSuperseded, removes backup files created by a service pack installation. It barely applies to modern Windows 11 (which uses cumulative updates instead of service packs), so you'll typically only encounter it on older or legacy systems.
4 More Built-In Ways to Free Up C Drive Space in Windows 11
The DISM cleanup handles the biggest hidden consumer of space, but it isn't the whole story. These four built-in tools cover the rest — from the automated option you set once and forget, to the classic utility that still packs the deepest clean. Here they are in the order I apply them on any machine I maintain:
1. Turn On Storage Sense
Go to Settings → System → Storage and enable Storage Sense. It automatically clears temporary files, empties the Recycle Bin on a schedule, and can offload files you haven't opened in a while to OneDrive (optional). It's not dramatic, but it's a steady drip of reclaimed space that requires zero effort after setup.
Settings → System → Storage: flip Storage Sense on and Windows starts tidying up on a schedule.
2. Run Disk Cleanup With System Files
The classic tool still works: search for Disk Cleanup (cleanmgr), select
your C: drive, then click "Clean up system files" before choosing what to remove. That button
unlocks the deeper categories — Windows Update Cleanup, previous Windows installations, and
Delivery Optimization files — that the quick scan never shows.
3. Disable Hibernation if You Don't Use It
The hibernation file (hiberfil.sys)
routinely eats several gigabytes — its size scales with your RAM. If you never use hibernate (most desktop users
don't), reclaim the space in one line:
Command Prompt (Admin)
powercfg /h off
4. Check the Quiet Space Hogs
A few more places worth a look on any machine I service: the Downloads folder (installers accumulate silently), Settings → Apps sorted by size (uninstall what you stopped using), and developer features like WSL distributions and Docker images — these live on C: by default and can quietly consume tens of gigabytes. Our guide on running WSL and containers on Windows 11 covers how to manage those environments properly.
What Mistakes Should You Avoid When Cleaning the C: Drive?
After years of undoing other people's "cleanups," these are the mistakes I see over and over:
- Manually deleting the WinSxS folder. This is the big one. Renaming or deleting it directly corrupts servicing infrastructure, breaks Windows Update, and can leave the system unbootable. Only DISM (or Disk Cleanup's Windows Update Cleanup entry) should ever touch it.
- Trusting aggressive third-party "optimizers." Many of them delete files based on stale rules, break application caches, and install background services you didn't ask for. Windows' built-in tools and a disk-space analyzer are genuinely all you need.
- Cleaning without a backup. Most of these operations are safe, but "safe" isn't the same as "zero risk." I always take a full backup image to an external drive before deep system cleanup — if the machine matters, so should the image.
- Deleting "unknown" files to hit a quota. If a folder in the C: root looks unfamiliar, look it up before acting. Some folders regenerate on reboot (wasting your effort), and others — like WinSxS — are load-bearing.
- Ignoring the cause. If your C: drive fills up every few weeks, find the offender with a tool like WizTree instead of repeatedly mopping the floor. A misbehaving application writing huge log files is a common culprit I've seen in enterprise environments.
And if your cleanup is motivated by an ageing machine rather than a full disk, remember that free space is only one variable — our article on a PC getting slower without a hardware cause covers the rest, and our walkthrough on disabling DiagTrack telemetry on Windows 11 removes one more background service that keeps the disk busy for no benefit.
Final Thoughts: One Command, Real Space Recovered
Freeing up C drive space in Windows 11 doesn't require new hardware or a utility suite you don't trust. The
built-in tools handle almost everything: Disk Cleanup and Storage Sense for the routine stuff,
powercfg /h off
for the hibernation file, and the DISM component cleanup for the biggest, most overlooked consumer of all — the
WinSxS component store.
The amount you recover will vary from system to system. Some machines give back only a few gigabytes; others hand you 10–15 GB in a single command. Either way, the analysis step tells you beforehand whether it's worth your time — and the safe variant keeps a rollback path open, which is exactly what you want on a machine you depend on.
Your next step is simple: run
DISM /Online /Cleanup-Image /AnalyzeComponentStore
today and see what your component store has been hoarding. Then check on the result next month — a
shutdown timer and scheduled maintenance habit makes this painless, which is exactly what our
guide on
setting a shutdown
timer in Windows
helps you build.
Video: Reclaim the Space, Then Extend the C: Drive
Prefer to watch? These two walkthroughs from the Valley4Techs YouTube channel pair perfectly with this guide: once the cleanup commands above have given you back several gigabytes, you can put that free space to work by extending the C: partition itself — no paid software required.
A free, built-in way to extend the C: drive in Windows 10 and 11 — no third-party software needed.
What if the unallocated space isn't next to C:? This walkthrough covers that case too, using a free tool.
Frequently Asked Questions
These are the questions I hear most often from users and colleagues about reclaiming space on Windows 11. If yours isn't here, leave it in the comments and I'll add it.
We'd love to hear your thoughts! Leave a comment below
and share your experience or questions.