SSD drive is showing as full

Mar 30, 2018
2
0
10
Hello everybody. A few weeks ago, I set up a new Samsung Evo SSD on a client's Inspiron 3847 desktop computer. It had a mechanical 1TB drive that was getting tired and slow, and he was only using 100GB of that drive, so I opted for a 256GB SSD and used the migration software to clone the disk. Clone went perfectly, and the new SSD had about 150GB of free space when I left. He calls me yesterday, and said his hard drive was out of space. I picked up the computer, and sure enough it was full.

After adding up the folders, the total of used space was only about 100GB, yet the hard drive shows as full. I used WinDirStat, and it found 150GB of "Unknown" space. Hibernation and system restore are off and were off before the original cloning. I ran the restore file cleanup anyway, but to no avail.

Now this is where it gets really weird. I had left his original drive in the computer after the clone. It was NOT hooked up, but just sitting in there. I then hooked up the original drive as a secondary drive (it was 90% free space), and rebooted. I immediately checked the properties on the mechanical drive, and it shows as being full as well. WinDirStat shows about 900GB of 'Unknown".

If I take either drive, and hook them up as a secondary on another machine, the drives still show as full.

I am really stumped on this one, and would appreciate some feedback or a way to delete the "Unknown" space on these drives.

Thank you,
Randy
 
Does your folder options say to show hidden folders?

Somehow, you need to find out what is hidden there.


The ssd migration app apparently did not find the need to copy the "unknown space" from the original drive.
So, some app must have run after the migration was done to create the unknown space on the ssd.

 
After running WinDirStat on another computer with the SSD hooked up as a secondary, it found over 80GB occupied by AVG dumps. He wasn't using AVG, as it was uninstalled a few years ago when he switched to Norton. Windows>system32>config>systemprofile>Appdata>Local>AVG>log>AVG16 folder had over 15,000 dumps occupying over 80GB. Problem is now fixed, but the mystery of how that happened in the first place remains.