Windows Module Store and Disk Caching Explained

The Windows Module Store, usually called WinSxS, is the folder that holds every version of every system component Windows has ever installed. It lets updates roll back cleanly, and it is also one of the largest folders on the system disk.

This guide explains what WinSxS stores, how it behaves, and how a disk cache interacts with it.

PAGE CONTENT

• What the Module Store Stores
• How WinSxS Behaves on Disk
• How It Interacts with a Disk Cache
• Where the Two Conflict
• Configure a Cache for the Module Store
• FAQs About WinSxS and Caching
• Back Up Windows Before You Change Settings

What the Module Store Stores

The folder is a component database, and it is more active than it looks:

• Multiple versions of each component. Every update that replaces a DLL keeps the old version so a rollback can restore it, as described in how the Windows Update cache grows.
• Hard links to system32. Many files in C:\Windows\System32 are hard links into WinSxS, so the folder is logically larger than it is physically.
• Manifest files. XML files that describe which components depend on which, read during update and repair operations.
• Backup software reads it all. Imaging tools walk the entire folder, which is one-pass sequential work - see caching for backup and imaging software.
• The folder lives on the system volume. Usually C:\Windows\WinSxS, alongside the OS and the installer cache described in Windows Installer cache.

How WinSxS Behaves on Disk

The access pattern is bursty and read-dominated, which is the part that matters for caching:

• Updates read thousands of files at once. A cumulative update checks and replaces hundreds of components, each requiring a manifest lookup.
• Backups read the whole folder. An image backup walks every file in WinSxS sequentially, which is bounded by the folder size, not the cache.
• Rollbacks write and delete in bulk. An uninstall swaps old versions back in, which is sustained random write work.
• Between updates, the folder is cold. Day-to-day use rarely touches WinSxS, so the cache holds blocks that sit idle for weeks - the case described in when a disk cache does not help.
• Hard links confuse size reports. The folder looks enormous in a file manager, but the physical disk cost is lower because many entries share the same blocks.

How It Interacts with a Disk Cache

The two layers overlap mainly during updates and backups, and the interaction is limited:

• Update reads are cold the first time. A new cumulative update reads components that have not been touched since the last update, so the cache has to fetch them from the SSD tier.
• Repeated updates hit the cache. If an update fails and is retried, the same manifests are read again, which the cache serves from the faster tier.
• Backup passes warm the cache. The first backup is cold, but a second pass benefits from the blocks the first one cached.
• Day-to-day reads do not involve WinSxS. Normal application use does not touch the folder, so caching it for steady-state work is a poor bet - the distinction is in cache vs buffer.
• The folder is too large for the RAM tier. A typical WinSxS is 5-15 GB, so only the hottest manifests fit in the RAM tier.

Where the Two Conflict

A few setups work against each other, and they are easy to avoid:

• Cleaning WinSxS by hand. Deleting files directly breaks updates and rollbacks; the only safe cleanup is the built-in DISM command.
• Compressing the folder. NTFS compression makes update reads slower, and the savings are smaller than the hard-link deduplication already provides - see NTFS compression and caching.
• Running updates during heavy work. An update competes with builds, copies, and the cache warm-up itself for the same disk.
• Caching the folder aggressively. A read cache learns blocks that are only read during updates, which wastes cache space that the working set could use.
• Moving WinSxS to a slow drive. The folder cannot be moved, and even if it could, a slow drive would stall every update.

Quick summary

WinSxS is a poor target for read caching. The wins come from leaving it on the system SSD and letting backup passes warm the cache naturally.

Configure a Cache for the Module Store

The sensible setup is to leave WinSxS where it is, keep it on a healthy SSD, and point a disk cache at the system volume for the files you actually reopen. Qiling Fast Cache uses a RAM tier for the hottest blocks and an SSD tier for the rest, and shows the hit rate in the task list.

• Free Download
• Windows 11/10/8/7, 100% Secure

Step 1. Install Qiling Fast Cache and open the task list. Run a DISM cleanup once before configuring anything, so the folder is at its real size.

Step 2. Click the "+" button and select the system volume. WinSxS lives under C:\Windows, so the cache picks it up automatically.

Step 3. Size the SSD tier for your real working set, not for WinSxS. The folder is too large to cache entirely and too cold to benefit.

Step 4. Run an update and a backup after the cache has warmed, then read the hit rate - see how to check cache hit rate - and confirm that update reads are being served from the SSD tier rather than the platters.

FAQs About WinSxS and Caching

Can I delete files in WinSxS?

No. The only safe cleanup is dism /Online /Cleanup-Image /StartComponentCleanup, which removes superseded components that are no longer needed.

Will a disk cache make updates faster?

Slightly, on a retry. The first run of a new update is always cold because the manifests have not been touched since the last update.

Why is WinSxS so big?

It keeps every version of every system component so updates can roll back. Hard links mean the physical disk cost is lower than the logical size suggests.

Should I compress WinSxS?

No. NTFS compression makes update reads slower, and the hard-link deduplication already saves more space than compression would.

Does Storage Sense clean it up?

No. The folder is owned by TrustedInstaller, so cleanup rules leave it alone unless you run the DISM command explicitly.

Back Up Windows Before You Change Settings

Reconfiguring storage and cache settings is easier to undo when you have a recent image. Qiling Disk Master creates a full Windows backup you can restore from.

• Free Download
• Windows 11/10/8/7, 100% Secure

Part 1: Create a Full System Backup

Step 1. Install and open Qiling Disk Master. On the home screen, open "Backup and Recovery" and choose "System Backup". This option automatically includes Windows and the hidden boot partitions, so you do not have to select them one by one.

Step 2. Check the source. The disk where Windows is installed and its system partitions are already ticked for you. If you only need your personal documents, run a separate "File Backup" task instead.

Step 3. Click the destination box and choose where the image should be saved. Use an external HDD or SSD, a NAS, or any drive other than the one Windows is installed on, and make sure it has enough free space.

Step 4. Review the task summary and click "Proceed". Wait until the progress bar reaches 100%. Do not unplug the drive or turn off the PC while the backup is running.

Part 2: Restore Windows from the Backup

Step 1. Open Qiling Disk Master again, go to "Backup and Recovery", and select the recovery option. Your backup images are listed, so pick the one you created before the changes began.

Step 2. Choose the target disk or partition. Normally you restore to the original system disk. If the drive was replaced, select the new disk instead, and the restore rebuilds Windows together with its boot partitions.

Step 3. Preview the restore plan, click "Proceed", and confirm the warning. The PC restarts to finish the job, and Windows comes back exactly as it was on the day the image was created.

Conclusion

The Windows Module Store is a poor target for read caching because its files are only read during updates and backups, and most reads are cold. The wins come from leaving the folder where it is on the system SSD, running the DISM cleanup command to remove superseded components, and letting backup passes warm the cache naturally. Point a disk cache at the system volume for the files you actually reopen, size the SSD tier for your real working set rather than the WinSxS folder, and read the hit rate after an update rather than assuming the module store needs special treatment.

Protect your PC with Qiling Backup—create a system image before your next round of settings changes.

For more Windows performance guides, see how shadow copies interact with a cache, the installer cache and caching, how Storage Sense interacts with a cache, Defender real-time protection and caching, and NTFS compression and caching.

Related Articles

• Windows Hibernation and Disk Caching
  Another Windows system folder whose cache warms up only during specific operations.
• Power Loss Protection and Disk Caching
• Thermal Throttling and Disk Caching
• Memory Compression and Disk Caching
• File Deduplication and Disk Caching

Is this information helpful?   Yes   No

This information is not relevant.

This information is not easy to understand.

This information is not deep enough.

What can we do to improve this information? (Optional)

Refresh Please enter the verification code!