WindowsApps Folder Taking Up Space? 7 Safe Ways to Reclaim Gigabytes

Your C: drive is suddenly, mysteriously full. A disk-space analyzer points an accusing finger at one folder: C:\Program Files\WindowsApps. You double-click it — and Windows refuses, saying you lack permission, even as administrator. If the windowsapps folder taking up space on your drive has left you puzzled, you’re in good company. Here’s what’s inside it, why it’s locked, the hidden reasons it keeps growing, and seven safe ways to shrink it — plus what never to do.

What the WindowsApps Folder Actually Is

Every app from the Microsoft Store lands here — all UWP/MSIX packaged apps, from preinstalled ones (Xbox, Clipchamp, Widgets) to Spotify and Netflix. It’s also where Xbox Game Pass PC games install, and that matters: a single title like Forza Horizon 5 or Microsoft Flight Simulator can exceed 100 GB on its own.

The default location is C:\Program Files\WindowsApps (a second copy can appear on another drive if you changed the install location). It’s owned by TrustedInstaller, which is why even administrators get “access denied” on double-click.

Hidden answer one: your app data isn’t here. Saves and settings live in C:\Users\<you>\AppData\Local\Packages. This folder holds pure application files — clearing caches won’t shrink it; only removing or relocating apps will.

Why the WindowsApps Folder Taking Up Space Is So Hard to Shrink

Five reasons most articles never mention:

1. It’s invisible to most disk analyzers. TrustedInstaller ownership makes tools like WinDirStat report it as 0 bytes or “access denied” — so people underestimate it for months, then discover 60 GB hiding in plain sight.

2. Updates leave old versions staged behind. Windows stages the new version next to the old one and is supposed to clean up afterward — but interrupted or failed updates leave orphaned version folders sitting there for months.

3. Uninstalling doesn’t always remove the files. Standard uninstall removes the app for your account, but the package often stays staged for other users — and as a “provisioned” package Windows reinstalls for every future new user.

4. Windows has a secret cleanup command. Run this from an elevated Command Prompt:

rundll32.exe AppxDeploymentClient.dll,AppxCleanupOrphanPackages

It sweeps dead package folders into WindowsApps\Deleted; a reboot finishes the job and empties it. It’s the same engine a scheduled maintenance task uses — it just doesn’t run aggressively enough alone. (Event Viewer > AppXDeployment-Server operational log, Event ID 509, confirms it ran.)

5. Games are the number-one real-world cause. Without games, the folder is usually a few gigabytes. Add two or three Game Pass titles and it can balloon past 200 GB.

“We would actually not recommend deleting any folder or files under WindowsApps as it could mess up how your Apps works. If you want to free up hard disk space, the safest way to do it is to uninstall any unused applications.”

— Microsoft community advisor, on the official Microsoft Q&A forums

That sets the philosophy for everything below: use the front door, not the crowbar.

Method 1: Audit — Find Out What’s Eating the Space

Start with an inventory:

1. Open Settings > Apps > Installed apps, sort by Size (largest to smallest).
2. Check the Xbox app library too — games are usually the biggest offenders.
3. On shared PCs, other accounts’ apps occupy this same folder.

Note the top five space hogs — those are your targets.

Method 2: Uninstall Properly, Starting With the Giants

For ordinary apps: Settings > Apps > Installed apps > ⋯ > Uninstall, or right-click in Start. Games: uninstall from the Xbox app or Settings.

For preinstalled apps with no uninstall button, open PowerShell as administrator:

powershell

Get-AppxPackage *name* | Remove-AppxPackage

Replace *name* with part of the app’s name (e.g. *zunemusic*); add -AllUsers to remove it for every account on the PC.

Critical: never remove framework packages — VCLibs, .NET Native, UI.Xaml. Dozens of apps depend on them; removing one breaks seemingly unrelated apps.

Method 3: Move Big Apps and Games to Another Drive

Uninstalling isn’t the only option. If a second drive has room:

1. Settings > Apps > Installed apps > ⋯ > Move next to a large app. (Only apps that support relocation show this option.)
2. For future installs: Settings > System > Storage > Advanced storage settings > Where new content is saved > set “New apps will save to” to the roomier drive. This won’t move what’s already installed.
3. In the Xbox app, use Settings > Install options for the default game drive, and each game’s Manage option to move it.

Moving is the fastest fix for the windowsapps folder taking up space when games are the culprit — a 110 GB title shifts off C: in minutes, with zero risk to Windows itself.

Method 4: Clear the Store Cache and Purge Orphaned Packages

Step 1 — Reset the Store cache. Press Win + R, type wsreset.exe, press Enter. A blank Store window opens and closes — done. (This clears only the Store’s temporary cache, not your apps.)

Step 2 — Run the hidden orphan purge from an administrator Command Prompt:

rundll32.exe AppxDeploymentClient.dll,AppxCleanupOrphanPackages

This moves dead package folders into WindowsApps\Deleted. Reboot — the reboot is what empties that staging folder and returns the space. On long-neglected systems this alone has reclaimed several gigabytes. This built-in purge is the closest thing to a one-click fix for the windowsapps folder taking up space after years of unattended updates.

Method 5: Remove Staged Old Versions and Provisioned Bloatware

Still heavy? Old staged versions and provisioned packages are the likely cause. In administrator PowerShell, list everything staged:

powershell

Get-AppxPackage -AllUsers | Select-Object Name, PackageFullName

Duplicates with different version numbers are the leftovers. Remove an old version by its full package name:

powershell

Remove-AppxPackage -Package <PackageFullName> -AllUsers

Remove only the older version, never the one in use. Next, check provisioned packages:

powershell

Get-AppxProvisionedPackage -Online | Select-Object DisplayName, PackageName

De-provision the unwanted ones:

powershell

Remove-AppxProvisionedPackage -Online -PackageName <PackageName>

This stops the app reinstalling for new users, and its staged files are eventually reclaimed. Skip anything unfamiliar.

Method 6: Take Ownership — the Last Resort

Only if orphans remain after Methods 4–5, and only for folders of apps you already uninstalled. Never touch framework or system folders.

1. Right-click the folder > Properties > Security > Advanced > Change owner to Administrators, ticking “Replace owner on subcontainers and objects”.
2. Grant Administrators Full control, then delete only those folders.
3. Restore the original ownership immediately in an administrator Command Prompt:

icacls "C:\Program Files\WindowsApps" /reset /t /c /qicacls "C:\Program Files\WindowsApps" /setowner "NT SERVICE\TrustedInstaller" /t /c /q

Leaving ownership changed breaks Store app launches and updates — in bad cases only a repair install fixes it.

Rule of thumb: if Windows fights you this hard to open a folder, it’s telling you to use the front door — Settings and PowerShell — not the crowbar. Take ownership to inspect, never to demolish.

Method 7: Automate the Safe Parts

If the command-line steps feel risky, HutZon Storage Doctor automates the safe parts — removing leftover caches, temp files, and uninstall remnants without touching protected system folders. Use it for the junk around the WindowsApps folder, never as a crowbar to force the folder itself open.

Don’t Forget the Neighbors

WindowsApps isn’t the only silent hog. In Disk Cleanup (cleanmgr > “Clean up system files”), check Delivery Optimization Files — often hiding multiple gigabytes. Enable Storage Sense (Settings > System > Storage) for automatic temp-file trimming. And your GPU keeps its own giant cache — see clearing NVIDIA shader cache on Windows next.

What NOT to Do

• Don’t Shift+Delete anything inside WindowsApps by hand. You’ll break Store apps, orphan Start menu entries, and can damage Windows’ servicing stack.
• Don’t leave ownership permanently changed. It causes exactly the app failures described in Method 6.
• Don’t run random “debloat” scripts that nuke packages blindly — they routinely remove frameworks Windows needs.
• Don’t cut-and-paste the folder to another drive manually. It breaks ACLs and junctions; use Move in Settings instead.

FAQ

Q. Can I just delete the windowsapps folder taking up space on my C: drive?
Ans. No. Deleting it breaks Store apps, orphans Start menu entries, and can damage Windows servicing badly enough to require a repair install. Every method above achieves the same savings safely.

Q. Why does my disk analyzer show the folder as 0 bytes or “access denied”?
Ans. TrustedInstaller ownership blocks read access for ordinary tools. Run the analyzer elevated, or grant yourself temporary read access, to get a true measurement.

Q. Will uninstalling a game delete my save files?
Ans. Usually not. Saves live in AppData\Local\Packages or sync to the cloud through Xbox — but back up anything precious before a big uninstall, just in case.

The Bottom Line

The WindowsApps folder feels hostile because it’s designed to be left alone — but that doesn’t mean letting it eat your SSD. Work in order: audit, uninstall the giants, move what you keep, purge cache and orphans, de-provision bloatware, and save ownership surgery for last resorts. Once the windowsapps folder taking up space is back under control, keep it there: point new installs at a roomy drive, uninstall finished games, and re-run the orphan purge once or twice a year.