Windows 10: Storage space doesn't correlate with Apps and Features

In settings, under device and then storage, it says that my Apps and Features take up 120gb. When I click on Apps and Features and click sort by size, the largest file is 18gb, then the next file is only 1gb. The files do not add up to 120gb, and I want to know where to find what is taking up so much space!

:)

 

Apps & features disc space doesn't add up to storage use listed

Under "Settings," and "Storage," my OS_Install (C total size is 238 GB.

Under "This is how your storage is used and how you can free up space," it says...

Apps & features....98.8 GB

Yet even a cursory total of all programs listed (by size) under Apps & features reveals a total of about 1.5 GB.

And, a bunch of programs are listed at the bottom (including at least one that needs a lot of storage space) without *any* numbers.

Should I presume that the Settings -> Storage utility is incapable of listing ALL programs and all of the space they require?

Why the massive difference (98.8 GB vs 1.5 GB)?

 

Windows doesn`t start. Authomatic repair doesn`t work.

Thanks again!!

I`m sorry I had not noticed that the text on the picture was in spanish. It says that windows has replaced some damaged clusters in "name" file and "directory". Then, at the end "an unspecified error occurred (75736e6a726e6c2e 4f6)".

I`ll do it and I`ll be updating this thread when I have the report.

- - - Updated - - -

I ran SeaTools. These are the results:




Does it mean my HDD is useless?

 

Windows 10 Storage Space doesn't show up on new install

This resolved itself after I received "Feature update to Windows 10, version 1803", which seems to have taken a while to apply after I installed Windows. The Storage Space was automatically detected as expected.

This suggests some kind of incompatibility between update versions of Windows 10 from a Storage Spaces perspective (I created this Storage Space well over a year ago), which is awful because nowhere on the Storage Spaces interface does it suggest that this might happen. I will follow up with Microsoft support so they can either fix this or at least improve messaging/documentation.