Recently, I signed into Windows 10 but noticed something different about how it was behaving. Random dialog errors appeared on screen and apps started performing slowly or would not save files. This certainly created a concern and the culprit was right in front me. As you probably know, I generate a lot of screenshots for the articles I write here at Groovypost. The Snip app has been a lifesaver; making it easy to capture screenshots I can edit, save, and then incorporate into the various articles I publish.
The errors were happening a lot when I tried to save screenshots from Snip. It wasn’t until I tried saving to a different partition I came across something weird; I didn’t have a single byte of disk space left on my system drive. I thought, how could this be? I don’t work with large applications or files, if I do watch a video, it’s immediately archived to my external drive; old files no longer used are archived to the drive too. The majority of my active files are on OneDrive, which only use 6 GB of space.
Resolve 0 Bytes of Free Space Error in Windows 10 using TreeSize
I went ahead and performed all the usual tasks such as running disk clean up, following the steps in our Groovypost free up disk space tutorial and of course searching manually for any files I might have stashed somewhere on the drive. The only major files I had accumulated were the 4 GBs of HP drivers in the swsetup folder; kept at the root of my drive. I moved those too along with taking a close look at my installed apps to see, which ones might be eating up space. I accepted the fact that universal apps would eat up some space along with Windows Update. There was nothing I could do about that. What I was able to archive made no difference, 4 GB of disk space dwindled down to zero bytes in minutes.
What was causing this? A look through my Startup programs and Event Viewer yielded no clues. None of the Microsoft built in utilities were not working either. Windows 10 still continued to function, but apps remained funky.
Jam Software TreeSize (Free)
Doing a quick search for tools here on groovyPost turned up an article Steve wrote back in 2008 on how to create a hard drive utilization report using a tool called TreeSize Free. Good news for me, the tool is still maintained AND FREE!
TreeSize is a great tool. It comes in three versions which you can compare on their website — Freeware, and two paid versions. For my needs, the free version was good enough. That said, they offer a 30-day trial if you want to try out the paid versions of the tool. Either way — I highly recommend these guys.
After downloading TreeSize, the next step was to install it. That in itself proved to be a problem. TreeSize kept erroring out during setup because of a lack disk space. So, my next attempt was to install it in the Windows 10 Creators Update I had on another partition, which was not affected by the issue I was experiencing in Windows 10 Anniversary Update. Unfortunately, the app would not install on the Creators Update either. So, I was left in a tight spot. I had to find some way to free up space in my Anniversary Update installation. I managed to archive about a GB of audio files then rushed to get Treesize up and running. Phew! I finally got it up and running.
The interface is a bit like File Explorer on steroids. Users will have to dive in and start digging throughout the system to find files they think might be squatting on precious disk space. An excellent place to start is the AppData folder. Many applications store files there and you would be surprised to know a number of log files that can grow in size; hidden away from easy access.
After launching Treesize, the program defaults to your system drive where Windows 10 is installed, but the contents of the folder tree will be blank. Simply perform a new scan to build out a full map of your disk space usage.
Select the Tools tab then click the Options button.
Select the Start tab, click Apply then OK.
While Treesize scans your system drive, you will see an hour glass on each folder. Treesize will present some immediate locations and files you might want to review. These are normally not files you want to modify or delete.
When the scan is complete, you will get a better idea of where large files are stored on your drive. Locations highlighted in bold blue are considered folders which have a lot of large files.
As you can see in the screenshot below, Treesize determines some of the largest files are stored in the Users and Windows folders. Other directories might also contain large files users can browse and determine whether to delete or keep on a case by case basis.
One of the best places to start is your AppData folder; navigate to Users > YourUserAccount name > App data.
With a little bit of luck, I finally hit the jackpot for my particular issue; I came across two suspicious log files, created by none other than the Snip app. What was most surprising about both files is the size, 9 and 17 GB in size, which was just mind boggling.
Why were these log files so big and what were they being used for? I tried opening each in Notepad, but the app errored claiming they were too big. It seems, every time I captured a screenshot, the Snip app kept a log of it. For what reason? I haven’t got a clue. All I know is, I was ready to get rid of both of them. And just like that, I had recovered 27 GB of disk space.
No doubt, armed with TreeSize, there will be more to find and delete, however, for now, I’m back in the black. More importantly, being that Microsoft isn’t being actively developed anymore; it was a Garage project, after all, it was time to go back to using Snagit. Although not as simple as Snip, it’s rock solid and shouldn’t be filling up my hard drive with mysterious giant log files.
There are other recommendations I came across when I googled the 0 bytes of disk space error. Some recommended deleting the contents of the Windows SXS folder, Microsoft doesn’t recommend this. It’s often utilized by applications and other components in Windows for compatibility purposes. I personally didn’t feel confident with possibly crippling my system even more. TreeSize turned out to be just the solution I needed. If you keep running out of disk space and you have exhausted all the common disk clean up routines, give TreeSize a try.
Have you ever used TreeSize or a similar tool before? Would love to hear about it in the comments and inspiration for our next groovyPost!