Windows 10 storage

[Krit]

Why does all C folders file size and Local Disk C proporties Used space does not match ? Difference is 38gb of unknown space. All junk files are removed by this method and recycle bin is empty!

Is it normal or not ? And what is your personal result....

 

[Bill_Bright]

This is normal. It is because some system folders and files (including restore points - which can be rather large) are not directly accessible by the user so are not counted. If there were HUGE differences (like 100s of GB), it might indicate some corruption, but I see nothing alarming in your screen shots.

 

[Marcus L]

As said above also things like pagefile.sys and hyberfil.sys will likely be using a large portion of that space you can't see, you can edit the explorer Windows view to see hidden files and operating system files if you're concerned or just curious to learn, just don't go deleting those kinds of hidden files if you don't know what they are or what they do.

 

[P4-630]

just don't go deleting those kinds of hidden files if you don't know what they are or what they do.

Even if you tried, you can´t delete important system files, they are hidden for a reason.

 

[Krit]

After another restart i got even better results. These junk files takes a lot of space! I got down from 310GB to 262GB "Local Disk C proporties Used space" That's like size of one decent pc game.

Right now unknown space is only 19GB....

 

[Dr. Dro]

If you don't use hibernation or fast startup, open CMD as administrator and type

powercfg /h off
shutdown /r /t 0 (for a clean reboot)

Will free 32 GB from hibernation file. (your system specs claim you have 32 GB RAM)

I don't advise disabling the page file, but leave it on system managed - it'll save space and increase as needed. Capping system restore point storage to 1-2% of drive capacity can also help, but will reduce amount of available restoration points, and depending on how many things are installed in program files, you may need at least 10-15% of capacity there.

 

[DaemonForce]

Why does all C folders file size and Local Disk C proporties Used space does not match ?

Because ever since the tail end of the XP/LH era WinSxS has been a thing. Component Based Servicing is a huge part of the Windows internal software stack.
My suggestion is to only mess with the parts you're sure about and that means using the basic install/uninstall routines provided by Windows.
Also a lot of things like hibernation files, update files, the system PAGEFILE and many others are marked as system components and (super)hidden by default.
You won't see any of them without Hidden items checked.

I can cut things down pretty good since I have a fair idea of what I'm doing but with each iteration of Windows it becomes significantly easier to break all of it.
Then there are rolling updates, tons of broken update packages and all the other junk that's engineered with the same diabolical file structure as SharePoint.
The longer these builds exist, the less worth messing with any of it but I need to exercise a bare minimum level of control just to make Windows behave.

I really need to do a lot of cleanup soon.

 

[Bill_Bright]

Right now unknown space is only 19GB....

You can get yourself all ruffled up over nothing here. Unknown does not mean wasted or lost forever space. Windows is actually very good at managing resources - contrary to what some want us to believe. You have over 1.5TB of free disk space. Should you get down to critical levels, Windows will automatically free up what it absolutely does not need. But if you get that low, you have bigger issues to deal with - like buying more space, or uninstalling programs you don't use.

 

[bonehead123]

38gb out of 1.8tb.....
yes, normal
OCD, yes, normal (or not)

either someone needs help, or is just plain bored AF IMHO

 

[agent_x007]

Windows can't count multilayer folder trees (the more folders in folders it sees, the less accurate the count) - Try to use SpaceSniffer.
Windows SoftwareDistribution folder can also weight a lot and Windows system files can get dumb ("clean" drive with system files option should help with that).

 

[Bill_Bright]

Windows can't count multilayer folder trees (the more folders in folders it sees, the less accurate the count)

Huh? Sure it can. Please show us a link to a reliable source that says otherwise.

This is not about Windows being about to tally up totals for file sizes in subfolders accurately - it can. This is about files and folders being visible for counting. It should also be noted this information is being gleaned from the file system.

 

[agent_x007]

Huh? Sure it can. Please show us a link to a reliable source that says otherwise.

If you are under character limit, sure.
However, shouldn't counter "just work" regardless of how you name folders ?
My point was : It WILL break if your folder path is over ~255 characters long (ie. it will not count whatever files are beyond that limit).
You can do whatever you want with files themselves (open/close/edit), they simply won't show up on search or... when moving them to different partition.
Got this issue when my mom wanted to do a backup of her pdf/epub book collection (with year/source/author/type/series/title + number in folder's name).
It was a pain...

 

[Bill_Bright]

So you can't show us a link. Got it.

My point was : It WILL break if your folder path is over ~255 characters long

First, you never said, implied or suggested anything of the sort. So PLEASE, don't try to change your story now.

Second, that is a big if and is applicable to old, 32 bit applications and the use of very long file and folder names - not exactly an every day occurrence. So instead of allowing extremes to rule the day, let's stick to everyday reality, okay?

By the way, a folder/filename path that long would look something like this:

c:\windows\foldername\anotherfoldername\andanother\yetanother\foldername\anotherfoldername\andanother\yetanother\foldername\anotherfoldername\andanother\yetanother\foldername\anotherfoldername\andanother\yetanother\foldername\anotherfoldername\andanother\filename.com.​

Seen many of those lately? I thought not.

 

[agent_x007]

@Bill_Bright I'm not changing story, I just generalized too much in my first post - which is my bad.
I added more information in second one.

If you just want a link to max character limit issues with moving files, here's example :

Why does the 260 character path length limit exist in Windows?

I have come up against this problem a few times at inopportune moments: Trying to work on open source Java projects with deep paths Storing deep Fitnesse wiki trees in source control An error tryin...

stackoverflow.com

But that's not what You wanted, isn't it ?

I can't provide link for capacity/file counter being broken, because I never considered it an issue worth my time - so why should I bother with documenting it ?
I bet most that came in contact with it are the same... This is VERY niche problem, and just throwing more hard drive capacity vs. what Windows claims files/folders require "fixes it" (or makes it not appear).

If you don't want to believe me - that's fine. You have the right to do so.
I put my comment out there for others to know there is this limitation.

As for "everyday occurrence" - that means it should usually be different for each of us, right ?
In my case, I've seen character limit capacity or file counting issues plenty of times (before my mom learned how to go around it).

Here's two samples of what my mom has currently on her laptop* :



BTW, there should be .pdf/.epub at the end (since all words after last "/" are the actual filename).
I copied file paths 1:1 into MSWord, and highlighted them for easy count.

For ease of translation, here's in order what window ("Statystyka :" = "Statistics :") on right lists :
"Wyrazy" : Words
"Znaki (bez spacji)" : Characters (no space)
"Znaki (ze spacjami)" : Characters (with spaces)

SO, after all that we get 270 characters without space and ".xyz" ends (and 320+ with spaces).
Overlimit ?
Very much so.
Does it present issues with file counting/capacity used by files - Yes.
Again, you don't have to believe me if you think I'm wrong.

PS. *Laptop uses latest Windows 10 x64, with Office 2007.

 

[Bill_Bright]

But that's not what You wanted, isn't it ?

A link to a forum thread? No. I said a reliable source - like maybe this one.

because I never considered it an issue worth my time - so why should I bother with documenting it ?
This is VERY niche problem,

Thank you for agreeing with my point - this is "not exactly an every day occurrence. So instead of allowing extremes to rule the day, let's stick to everyday reality, okay?"

If you don't want to believe me - that's fine.

Who said I didn't believe you? I even explained how it can happen. But again, it is not common.

I'm not changing story, I just generalized too much

Sure you did change your story. You said,

Windows can't count multilayer folder trees (the more folders in folders it sees, the less accurate the count)

Here you are saying (1) it can't count and (2) it becomes less accurate the more folders it sees. Both are NOT true and what I was challenging.

Then you changed your story to say

It WILL break if your folder path is over ~255 characters long

Will "break" once it reaches that limit is NOT the same thing as (or even a generalized version of) claiming it can't count and it becomes less accurate with more folders. Now as you said, "If you don't want to believe me - that's fine. You have the right to do so." But everyone can read for themselves what you said the first time, then how you changed it.

The fact is, Windows is very accurate, unless and until the maximum path length reaches 260 (not 255) characters, then it faults - for THAT folder, not the entire disk.

Regardless, it would be highly unlikely such a scenario would result in 10s of GBs of unreported disk space - which again is my point.

 

[agent_x007]

Here you are saying (1) it can't count and (2) it becomes less accurate the more folders it sees. Both are NOT true and what I was challenging.

Windows can't count multilayer folder trees (the more folders in folders it sees, the less accurate the count)

It "can't count", isn't equal to "can't count multilayer folder trees". That is one line of text, don't just pick convenient parts to make your point forcefully valid. It sounds as if you were trying to tell everyone that what I wrote "Windows can't do math", which isn't what I wrote. Text in parenthesis should give a clue I was thinking of 255 character limit. Regardless, it's my error for omitting "255 character limit" in that sentence.
Which was my fault for being lazy/wanted to shorten my reply.

The fact is, Windows is very accurate, unless and until the maximum path length reaches 260 (not 255) characters, then it faults - for THAT folder, not the entire disk.

Regardless, it would be highly unlikely such a scenario would result in 10s of GBs of unreported disk space - which again is my point.

That last part is what WILL fail the same way OP has seen :
"Entire disk" in folder/file counting, won't be equal to "entire disk" in partition proprieties.
"Entire disk" can be interpreted in multiple ways, please keep that in mind.
Size of missing space is ALWAYS up to number and size of files that are inside beyond 255 character limit folders, and You can't know what other people are putting there unless they write it themselves, so don't assume anything.

As for "your point" : At this... point, I feel like it's more to prove You are "correct", and I'm "wrong".
Which is pointless, as you clearly know (unlikely scenario).
So... what does it actually take for end this toxic exchange ?

I guess, some good will ?
For me, I just hope next time you just write : "That applies only if 255 character limit was exceeded".
Instead of :

Huh? Sure it can. Please show us a link to a reliable source that says otherwise.

Not everyone have time for reading all fluff we already generated, for which I'm sorry for anyone reading (I got heated too much). I unwatched this thread, so - no more popups... unless someone quotes me again

 

[Bill_Bright]

It is not about proving one right or wrong. This is a ""technical" support site. So it is about providing the readers the technically correct facts to make informed decisions.

 

[lexluthermiester]

Why does all C folders file size and Local Disk C proporties Used space does not match ?

This is due to the folder in the root of the drive called "System Volume Information" which contains data that is excluded from all data-space calculations except the drive used/free pie graph.

 

[Wirko]

This is due to the folder in the root of the drive called "System Volume Information" which contains data that is excluded from all data-space calculations except the drive used/free pie graph.

Firing up Linux from USB and peeking inside that folder (and other inaccessible folders) is always an option. In Windows 10/11, it may even be possible to abuse WSL for that.

38gb out of 1.8tb.....
yes, normal
OCD, yes, normal (or not)

either someone needs help, or is just plain bored AF IMHO

You can compare 38 GB to the total disk space ... or you can compare it to Windows 10 system requirements, for example. "20 GB". This forum doesn't allow scare quotes big enough. Out of those 20 GB, Windows eats up 38 GB for we-don't-tell-you-what.

 

[Marcus L]

Pagefile which is enabled by default is usually anywhere between 4Gb-16Gb, Hyberfil.sys is the same as the system RAM, could be another 16Gb, OP has managed to find the root cause to most of the "missing space" however, though what's a few gigabytes between friends?

Temp files, installation files, update files etc, I mean... yea, there is space to be freed up, but on modern systems with a 2TB drive and only 150Gb full, is it really worth the hassle to go digging for those extra 15Gb's? regular maintenance of your OS drive such as clearing the temp folders, getting rid of unused apps, deleting restore points etc are all part and parcel of maintaining a system, if you don't do this, chances are you will be just fine, but for those of us who have been using and tinkering with Windows installs for 20+ years it just comes as 2nd nature

 

[bonehead123]

This is normal. It is because some system folders and files (including restore points - which can be rather large) are not directly accessible by the user so are not counted. If there were HUGE differences (like 100s of GB), it might indicate some corruption, but I see nothing alarming in your screen shots.

As said above also things like pagefile.sys and hyberfil.sys will likely be using a large portion of that space you can't see, you can edit the explorer Windows view to see hidden files and operating system files if you're concerned or just curious to learn, just don't go deleting those kinds of hidden files if you don't know what they are or what they do.

Even if you tried, you can´t delete important system files, they are hidden for a reason.

GOD mode, if anyone wants to look at and/or try deleting hidden files, some of which still won't delete because they are critical to the OS working correctly, and even if you could delete them, would most likely result in a non-bootable crash bunny, hahaha

 

[Wirko]

GOD mode, if anyone wants to look at and/or try deleting hidden files, some of which still won't delete because they are critical to the OS working correctly, and even if you could delete them, would most likely result in a non-bootable crash bunny, hahaha

I hope the OP didn't take this thread as a instruction to delete everything that doesn't seem necessary. We still prefer bootable young male elephants to non-bootable crash bunnies, don't we? (Young because it has yet to grow, and male because male elephants gain weight throughout their life, mwahaha.)