Upgrade Windows 1903 10 1909, not 2004

zbook said:

Post an image of tree size after restoring an image (17 GB free).
Post an image when the free space is (3 GB).
Compare the two images to see the files that consume 14 GB.

Hi zbook,

By what means do I create those images?

treesize: TreeSize Free | JAM Software

You can take a screen shot and upload it

Jacee said:

treesize: TreeSize Free | JAM Software

You can take a screen shot and upload it

Forgive me for being dense. I can take a screenshot or export a pdf file, but neither of these methods will display an expanded tree structure. Is that not needed for some kind of analytical comparison?

Mark Phelps said:

I know it's an old app -- but it's still useful -- to see what folders are taking up the space: Folder Size - Freeware file size analysis. Check the directory sizes, folder sizes and file sizes on your computer with this freeware tree size analysis tool.

I use it still on Win10 to find large folders and files.

There is Treesize (Free) as well

TreeSize Free | JAM Software

Bree said:

Run TreeSize Free as an administrator, sort by '% of parent' and open up the tree structure as needed to show where the most space is being occupied. Take a screenshot of that. Do this twice, as Zbook asked, once before the free space gets used up and again after its down to 3GB. Post both screenshots for comparison.

These screenshots range from 9/16 (available space 19.6g) to 9/23 (available space 16.7g). I also have screenshots (not posted) for the days in between, that show the steady progressive loss of space.


Attachment 298777

Attachment 298778

You will notice that it seems directly related to the Programdata folder, but I went to check out that folder, and it is only 834mb total size

Attachment 298779

Bree said:

File Explorer can be misleading. It will only show you the total size for the files and folders you have permission to see. TreeSize Free when run as an administrator can show you all files. Look again at the ProgramData folder, but this time look with TreeSize Free.

I'm guessing this will be no surprise to you. it wasn't to me once I was reminded of it.

The only thing that stands out in Program Data is windows.edb, the Windows Search Service database file, 4.8g in size.

Like many others, I'm sure, I had issues with this in the distant past, probably several years ago, with that file growing as large as 15-20g (or more if you let it) , but I didn't make the connection until, thanks to you, I took your advice and dug deep into Program data, whereupon, if I'm not mistaken, it became obvious what was going on.

What I don't understand is why now, as in, why in Windows 1909? I may be wrong, but I don't remember having this issue in Windows 1903.

In the past, I rebuilt the index, as seen here FIX: Windows.edb huge file on Windows 10

The only problem with that is it takes hours.

Do you have any advice about how you would handle it, or perhaps any prevention methods?

I rebuilt the index and got the space back, but in the 3 days since I've again lost 1.5g.

If i disable indexing, will that take care of it for good? I have an ssd. Do I really need indexing?