Why Doesn't Windows Storage Add Up?
When you select all files in C: and check properties, the sum is much smaller than the used space on the drive. Learn the technical reasons why.
- File Explorer Properties cannot read permission-restricted system folders like System Volume Information.
- NTFS Cluster Slack causes small files to occupy more physical disk space than their logical size.
- Volume Shadow Copies (VSS) and Master File Table (MFT) reserved zones consume space invisibly.
- ClearKun measures physical volume allocations directly to show genuine storage usage.
The Problem You're Experiencing
You open your C: drive, select all visible folders, right-click, and check Properties. It says 150GB. Yet, when you check the C: Drive Properties in 'This PC', it shows 230GB of used space. 80GB of disk usage is completely unaccounted for.
Why This Happens
Windows storage consumption is typically driven by a combination of background system maintenance and application cache expansion:
Access-Denied System Volume Information
15 GB – 60 GBThe System Volume Information folder contains restore points and shadow copies. Because standard users lack read permissions, File Explorer reports its size as 0 bytes.
Cluster Slack (Size vs Size on Disk)
5 GB – 25 GBDisks allocate space in 4KB cluster blocks. A 100-byte file still occupies a full 4KB cluster. Millions of small files create significant cluster slack overhead.
NTFS Metadata & Master File Table (MFT)
5 GB – 15 GBThe file system reserves 12.5% of the drive volume for the MFT index to track file locations and metadata, which is hidden from File Explorer.
System Paging and Hibernation Reservations
10 GB – 35 GBSystem-level files (hiberfil.sys, pagefile.sys, swapfile.sys) are locked by the kernel and excluded from multi-folder selection calculations.
How to Investigate on Your PC
Check Volume Shadow Copy Allocation
Open PowerShell as Administrator and run 'vssadmin list shadowstorage' to reveal hidden restore point allocations.
Compare 'Size' vs 'Size on Disk'
Right-click any folder with thousands of files (e.g. node_modules) and observe the difference between Size and Size on Disk.
Review Windows Storage Settings
Check Settings > System > Storage > System & Reserved to view Windows OS and virtual memory allocations.
How ClearKun Helps You Solve This
ClearKun runs locally on your Windows PC using native Win32 APIs, analyzing disk usage without streaming your private file contents to the cloud:
Direct Volume Allocation Reading
Queries native NTFS volume allocation records to account for protected system areas accurately.
Physical vs Logical Size Breakdown
Displays both true size on disk and file content size so you understand cluster slack impact.
Hidden System Allocation Transparency
Explains exactly what portion of your drive belongs to system restore, paging, and application caches.
What You Should Do (Safe Action Plan)
Manage System Restore Allocation Limits
Limit System Protection maximum usage to 5% or 10% in Windows System Properties to prevent shadow storage bloat.
Consolidate Small Files and Repositories
Compress or archive directories containing hundreds of thousands of tiny source files to eliminate cluster slack.
Disable Hibernation if Not Used
Run 'powercfg -h off' in an admin command prompt to remove hiberfil.sys and instantly reclaim gigabytes.
Important: What NOT to Delete
To prevent Windows crashes, Blue Screens of Death, and broken applications, never manually delete or force-purge the following paths:
System Volume InformationContains NTFS file system indexes and active system restore points. Deleting it corrupts drive metadata.
$MFT and NTFS System MetadataCore disk file allocation structure. Tampering with it causes total partition loss.
Why Manual Size Calculation Fails
Selecting all folders in File Explorer and checking properties is one of the most common mistakes in disk troubleshooting. Windows prevents standard user processes from reading administrative directories, causing File Explorer to silently calculate restricted folders as zero bytes.
The Difference Between Size and Size on Disk
Every storage drive is divided into fixed allocation clusters (usually 4,096 bytes). Even if a file is only 50 bytes, it occupies the entire 4KB cluster. When you have hundreds of thousands of small files, this cluster overhead creates gigabytes of phantom usage.
Frequently Asked Questions
Related Guides
Explore more guides to optimize your Windows storage.
Where Did My Storage Go?
Your Windows storage rarely disappears on its own. Discover how hidden caches, shadow files, update leftovers, and expanding application data silently consume your drive space.
Why Are Hidden Files Taking Up Space?
Dozens of gigabytes on your disk are completely invisible. Learn how hidden OS files, hibernation, and system volume stores consume space.
Why Is the System Folder So Large?
Windows Settings says System & Reserved is taking 50GB–100GB. Learn what lives inside C:\Windows and how to safely reduce its footprint.
Why Is My C: Drive Full?
A full C: drive degrades PC responsiveness and blocks Windows updates. Learn what fills your system drive and how to safely reclaim space.