In any case, using windirstat will shed some light on where to find missing drive space. Windirstat, however, allowed me to right click and quickly delete the multitude of large log files.Įxchange was my issue, but your server may have another - some people mentioned anti-viruses causing issues. I tried deleting them in Explorer (which showed me that the Exchange folder was 0kb in size) which resulted in FAIL. As I suspected, there were some super hidden files C:\Program Files\Microsoft\Exchange Server that took up nearly 30GB. Ultimately, I used a free tool called windirstat not only to find the missing space, but to delete the offending files as well. Where was the remaining 30GB? Poking around the net didn’t help - most of other people’s issues revolved around System Restore and Volume Shadowing but I had disabled all of that. What explains the 15 GB WinDirStat 'unknown', and the difference between the 66 GB and 45 GB There should be about 30 (75-4530) GBs free space, not only 9.
Explorer showed 25GB free, but only 25GB had been used. File Explorer, Disk Management, and GParted agree 66 GB is used, but I can only identify 45 GB of files on C: drive not 66. So we will try this.Tonight, I uninstalled Exchange Server 2007 from a development server and was surprised to see that, after the uninstall was complete (and not without a few workarounds), only 50GB of an 80GB hard drive remained. The machine does not or has not had backup & restore turned on as far as I am aware. (I have tried the right click > run as admin) When I manually check folder sizes on the machine they seem to match what WinDirStat is telling me. It turns out our nessus scan is crashing a view service for a couple seconds so it creates a large dump file. When I use WinDirStat to check for files on the C drive it returns as only having 57GB of files. In our case it was in C:\Windows\System32\config\systemprofile\AppData\Local\VMware\VDM there were several large dump files, these were the mysterious unknown files in WinDirStat. This allowed us to drill down to the folder that had the issues. We ended up disabling UAC and then the Properties showed the true file size of the Windows folder, as shown in powershell script. How can I find out what files are taking 25 GB of space? This is on a secondary drive that does not contain OS files it simply stores all the program files. I checked volume shadow copy and that is disabled and there are no volume shadow files listed. 169GB unknown file in windirstat Windirstat is showing a 169GB file and it is not restore points. It seems 40 GB is about right because if I use that 40 GB and add it to the rest of my folders on C I get the 45 GB that is in use. What is the best way to find out what files are sucking up so much space? My Windows directory lists its size as 15 GB but when I run a powershell script against it, it shows 40 GB.
0 kommentar(er)
