Knowledgebase

The main reason for this is that if we included the data of single files, the exported XML files would grow considerably and reach a size that cannot be handled reasonably.

Other export types, like Excel or PDF for example, allow including single files if it has been configured like this in the settings.

Since v9.0 you can also export the whole scan, including single files to an SQLite file. These database files can be reimported and worked with in TreeSize, just as you already know it from the XML files.

In case you need data like history data or growth reports on file level, we would like to recommend our product SpaceObServer. It regularly collects the file system information using a background agent and stores it in an SQL database, including size development and (optionally) all permissions. The reporting is faster and more flexible compared to TreeSize, because it is built on a database and collects data on file level. SpaceObServer offers advanced scripting capabilities through OLE Automation.

Yes. This web page provides an overview on the permissions reporting capabilities of TreeSize.

Right clicking on the header of the Details list will show a popup menu that allows to choose additional columns showing the permissions.
 
If you export a scan to Excel, these columns will be included as well. (To get a full report in Excel, you need to check-mark the option "Tools > Options > Export > Excel > Export the full directory branch" and optionally "Include single files in export"). Excel Auto-Filter is a good tool to filter the exported lists for specific users or groups, or to find folders or files where inherited permissions are missing or own permissions are added.

Our advanced disk space and file manager SpaceObServer has better reporting capabilities for permissions.

Are the "Owner" or the "Permissions" column active and part of the export? In Active Directory environments, Windows can take a long time to query these values. To speed this up, please disable these columns if they are not needed.

You can compare a scan to another folder using "Scan > Compare with path". This will show the size and file count differences on folder level between the path that was scanned, and the one that was selected for comparison.

No. TreeSize does not actively change the archive bit, and the system only changes the archive bit if a file is written. TreeSize works strictly read-only when scanning and searching and also does not modify the last access date if possible,

RAM

As a basis we recommend at least 8GB of RAM. Depending on your usecase more can be beneficial. For the general usage 1GB of free RAM should be sufficient.

Disk Space

For the installation is 500MB of free disk space required. During operation of the software, additional disk space usage may occur depending on how it is used, for example from scan exports, snapshots, logging or similar.

Unfortunately, TreeSize does not currently support searching Google Photos accounts.
At present, only Google Drive accounts can be searched.

To improve the readability of the report, we recommend using a monospace font such as 'Courier New'.
The font can be changed in Outlook as follows:

Classic Outlook:
1. On the File tab, choose Options > Mail.
2. Under Compose messages, choose 'Stationery and Fonts'.
3. On the Personal Stationery tab, under "Composing and reading plain text messages", choose font.

New Outlook:
1. On the View tab, select 'View settings'.
2. Select Email, then Compose and reply.
3. Set the mail format to 'Text' and choose a monospace font.

Yes, TreeSize Professional can scan disk image files such as VHDX.

To do this, simply:

1. Open TreeSize.

2. Click "Select Scan Target".

3. Choose the VHDX file as the scan target in the directory tab.

TreeSize will then analyze the directory structure inside the disk image and display the disk usage just like it would for a regular drive.

Exporting to XML format has some weaknesses, which is why we consider it obsolete. We therefore recommend exporting to SQLite as a better alternative.

This feature will be removed in a future version. Existing XML files can still be used for all other TreeSize functions for the time being. However, please make preparations for your export automation.