Knowledge Base


Please enter your query or select one of the above categories.

All entries (Page 3 / 15)

If the NTFS deduplication (available since Windows Server 2012) is enabled, TreeSize displays some strange values for the size of files and folders. A lot of files have a size of "0 Byte" while a folder called "System Volume Information" requires a huge amount of disk space. What is the reason for this?

The NTFS deduplication segments files with fractionally equal content into so-called "chunks" which are moved into a the subfolder "System Volume Informaton\Dedup\ChunkStore\" (SVI) located on the corresponding NTFS partition. After the deduplication has been applied, the original files are replaced by a pointer to the corresponding chunk in the SVI directory. Two identical files will only require half of the disk space they occupied before after a NTFS deduplication. Since the original files now only contain a small pointer, the allocated disk space will be indicated by Windows with a much smaller value than before (for two identical files the occupied disk space would be indicated as "0 Byte"). To make TreeSize show the original file and folder sizes again, simply switch the view mode from "Allocated Space" to "Size". The "allocated size" shown in TreeSize is the disk space you would obtain by deleting the corresponding file

I have just noticed that the line chart in the "History" tab of TreeSize has gone. What is the reason for this?

The line chart can only be shown if there was a scan of the same root folder performed at an earlier point in time. Furthermore, for a reasonable comparison the scans must have the same exlcude filters defined.

How can I make TreeSize to export data to Excel in the same spreadsheet (same file)?

When using Excel as export format, TreeSize will create a spreadsheet with the current timestamp and save the data into this sheet.

If the same file is selected for another export, TreeSize will create another sheet and append it to the file, so you won't lose the data from the previous export.

You can also specify a "Default Export File", so you don't need to select a file, every time you want to export the data. This can be done either in the Options of TreeSize (Tools -> Options -> Columns/Export -> Excel Export -> Default Export File") or in the corresponding export dialog (File -> Export -> Export to Excel -> "Always use this filename and add a new sheet when exporting").

When the default file was defined, you can simply go to "File -> Export -> Export to Excel" and TreeSize will add the current scan data to its own Excel sheet, using the default export file.

When exporting a scan result to Excel, everytime I export data the precedent data are replaced by the last export. How can I have multiple exports in the same Excel file?

By default, TreeSize will ask for a file name, every time an Excel report is created. If the file from a previous export is selected, the data will be overwritten.

If you would like TreeSize to create an Excel sheet for each export, you need to define a "Default Export File". This can be done either in the Options of TreeSize (Tools -> Options -> Columns/Export -> Excel Export -> Default Export File") or in the corresponding export dialog (File -> Export -> Export to Excel -> "Always use this filename and add a new sheet when exporting").

When the default file was defined, you can simply go to "File -> Export -> Export to Excel" and TreeSize will add the current scan data to its own Excel sheet, using the default export file.

Please note that this is not required when using the command line options of TreeSize. If an Excel report is created using a command line option (e.g. TreeSize.exe /EXCEL "D:\MyReport.xls" D:\), an Excel sheet will be appended if the file "MyReport.xls" already exists. Please refer to our online manual for more information about the available TreeSize command line options:

If I create a scheduled task for TreeSize, I cannot edit anything in the command line option window because it's read-only. Why is that so?

The command line options are automatically defined by TreeSize, based on your settings in the "Scheduled Task" window.

If you want to edit the command line manually, please save the current task and click on "All Tasks". In this view, please right-click the recently created task. In the context menu, click on "Edit Task in Windows". A new window will open which allows you to edit the command line options of the task manually.

If I right click a file within TreeSize, the application crashes. What is the cause for this?

This issue typically occurs if an application which extends the Windows context menu fails for some reason. In such cases, the faulting application will also crash TreeSize. Besides TreeSize, several other applications such as "WinRar" or "DropBox" extend the Windows context menu. As those applications share the same resource (the context menu) with TreeSize, an exception in one application might cause the application where the context menu is called from to fail.

Identifying the actual source of the problem is not an easy task. If the problem has occured only recently, you should check in the software list of Windows which applications have been installed recently. If one of these applications extends the Windows context menu, you should try to uninstall the application and check if the problem still persists.

For further questions or assistance please contact the TreeSize customer support under  (


TreeSize is using the wrong date format! I even checked the Windows date settings where it is set correctly. What can I do?

In general, TreeSize uses the date settings of Windows. Due to a problem in Windows 7 and Windows Server 2008 it may however display the 'wrong' date format.

To fix this problem, please open the "Regional Settings" ("Clock, Language and Region") in the Window Control Panel and click "Additional Settings". In the following dialog, click "Reset". After the confirmation, close the dialog and restart TreeSize. The problem should be fixed.

We have a file server with 3 volumes, drive E:, F: and G:. If I open TSP and double-click on the F: drive and then choose the History tab I get graphical chart that goes back to 6/11/2012. If I choose a different drive, it only shows a graph for that day. No history. How did I get the 6/11 date, I didn't choose it, and how do I get historical data for the other 2 drives. I realize that SpaceObServer will do a better job of providing historical data.

For each scan that is executed on a specific folder, TreeSize automatically saves the size from that scan for the use in the "History" view. If another scan on that same folder is done, TreeSize will add the new size data and create a graphical trend for this folder. This is the reason why you might see different periods of time for different drives and/or folders.

As you mentioned, SpaceObServer is much more powerful in regards to creating reliable statistics for the increase/decrease of disk usage of your systems. SpaceObServer scans local and network drives as well as Exchange mailboxes using a background service and stores their structure, sizes and properties in an SQL database.
In an Explorer-like user interface the collected data can be viewed and browsed in hierarchical or tabular views, 3D bar, pie, line charts and tree maps. Using the archived data you are able to track the development of the space usage from past to present, and forecast future size usage.

Can I use TreeSize to scan the file system of a mobile phone, which is connected via USB? I can browse the files on the device using the Windows Explorer.

In general, TreeSize can scan any systems that have a drive letter assigned in Windows. This typically applies to local drives, network shares, etc.

Most mobile devices will announce themselves as MTP (media transfer protocol) devices, which allows access via Windows Explorer without having an actual drive letter assigned. In this mode, TreeSize cannot scan the contents of the device.

To scan the contents of your mobile device you should check if your mobile device provides a "mass storage usb mode" when being connected to a PC. In this mode, the mobile device will be treated as a regular USB device by Windows and therefore having assigned a drive letter. This will allow TreeSize to scan the device.

Given that your mobile device uses a memory card, you can also use a memory card reader which usually provides the content of the card as a device that can be processed by TreeSize.

I'm trying to create a report of two separate drives by using the command line options of TreeSize:

"C:\Program Files (x86)\JAM Software\TreeSize Professional\TreeSize.exe" /EXPAND 1 /GROUPSCANS /EXCEL "myreport.xlsx" "C:\" "D:\"

The Excel file only includes the search locations "C:\" and "D:\" and not the designated 1 level expansion.

If you use the /GROUPSCANS switch, TreeSize combines your scan paths into a virtual root folder which is referred to as expand level 0. Following this, /EXPAND 0 will only show the virtual folder. 

/EXPAND 1 will show the virtual folder plus the given scan paths (M:\_PROJECTS" "R:\_PROJECTS in your case)
/EXPAND 2 will show the virtual folder plus the given scan paths plus their first level of files and folders. 

In order to expand the first level of each defined scan path you will need to use "/EXPAND 2".

Is TreeSize capable of scanning distributed file systems (DFS)?

TreeSize is capable of scanning Distributed File System environments. It will follow the links to the target directories so you won't have to map single shares.

I would like to report on multiple mapped drives and have the locations reported on a single Excel worksheet. By default TreeSize will create a seperate sheet within the Excel file for each location. Is it possible to merge those sheets so I get a summarized report for all of the drives scanned?

Yes, this is possible by using the "Virtual Root Folder" feature of TreeSize. Using this feature it is possible to group scans under a virtual root folder. This virtual root folder shows a summary of all scans that are part of this group. This way you can merge different scans together e.g. for printing or exporting. You can add or remove scanned paths individually from the virtual root folder using the context menu.