How to Determine the Size of the System Volume Information Directory

Due to the strict permissions on the System Volume Information directory finding out its true size is not easy.

Explorer is really bad at such things. It definitely was not made for administrative tasks. It displays the directory size as zero bytes:

System Volume Information Properties_2013-01-11_00-23-39

You need a tool that can dig a little deeper, SetACL Studio. It can bypass security and list everything that is there:

System Volume Information - SetACL Studio

Unfortunately, SetACL Studio does not display the directory size and I do not know any other tool that can display directory sizes while bypassing security. Except for one tool that comes with Windows and is very well known. Alas not for calculating the size of directories, but for copying them. Yes, I am talking about robocopy.

Open an elevated command prompt and try the following:

robocopy "c:\System Volume Information" c:\dummy /l /xj /e /nfl /ndl /njh /r:0 /b

The output you get will be similar to the following:

               Total    Copied   Skipped  Mismatch    FAILED    Extras
    Dirs :        11        11         0         0         0         0
   Files :        25        25         0         0         0         0
   Bytes :   1.141 g   1.141 g         0         0         0         0
   Times :   0:00:00   0:00:00                       0:00:00   0:00:00
   Ended : Fri Jan 11 00:31:55 2013

So the size of my System Volume Information is 1.141 GB.


4 Responses to How to Determine the Size of the System Volume Information Directory

  1. Remko January 11, 2013 at 08:59 #

    Clever solution!

    Obviously we need SeRestorePrivilege and Backup API’s so the only other tool that comes with Windows I can think of is Windows Backup.

  2. André January 11, 2013 at 20:47 #

    I use TreeSizeFree, running with elevated rights. It can show the usage.

  3. Jon Mozley June 25, 2015 at 11:40 #

    Interesting use of Robocopy!

    André, TreeSizeFree is my go-to software for checking folder sizes but I found it would only work if I assigned read permissions to myself on the SysVol directory, even if I run it elevated.

  4. John Peachey March 3, 2016 at 13:39 #

    I just used the trial version of TreeSize Pro and thank god I now have exactly the info I needed. The answer was obvious for my problem when I realise it now – the replicated folders staging volumes were taking up a few hundred gigs (as configured by myself). I’ve reviewed the staging sizes and been able to trim them a bit still leaving plenty of room for expansion, and don’t have to panick about gaining more disk space for the time being. So +1 for TreeSize Pro (One of the first pieces of software I’ve considered paying for in a while)

Leave a Reply