FAQ & Knowledge Base

Welcome to our Knowledge Base. Search or browse through the topics below to find answers to your questions.

Categories: TreeSize | Show all categories

This can be done by navigating to the advanced or duplicate search and by then right-clicking in an empty space in the search configuration area where you normally add filters. Select "Import from file" or "Export to file" afterwards and the program loads a previously saved filter configuration or saves the current one to a file, depending on what you chose.

TreeSize allows importing paths from a .csv or a .txt file. To do so, you can first expand the search path list by clicking on the arrow next to it or by clicking on an empty space inside somewhere, then right-click into the expanded path list and select "Import paths from file".

There are a few reasons why this can happen. The two most common ones are:

1. The duplicate files do not have the same MD5 checksum

2. There is an issue accessing the selected search path(s)

Regarding #1: The standard setting for the comparison method of the duplicate search is "File Content", which means the program compares the MD5 checksum of each file to determine if the files are identical. A way to find these files where the checksums don't match is to use "Name and size" as comparison method for example. This way, only the name and size have to match, but this is less accurate than the default setting.

Regarding #2: If TreeSize can't access the search path, it can't find any duplicates even if they exist and use the same MD5 checksum. This is indicated by an error on the bottom of the program window which you can click on. It should then tell you that the access to the path was denied.

In this case, please start the program as administrator as this solves the issue most of the time.

In our customer area, you can find an offer to upgrade to this version at a discount.

To change this, please use the command line parameter /SIZEUNIT N

For more information on this, please refer to this page in the manual for TreeSize.

The XML export's purpose is to be used to save a complete scan and to be able to load it later on, as well as using it for comparisons.

If you are only interested in the top level or a low depth, please consider using the Excel or CSV export instead.

It is also possible to reduce the size of the XML file by disabling the statistics for age of files, file owners and extensions in the scan settings.

If a SharePoint Online site is configured to require a multi-factor authentication, TreeSize will perform a browser based authentication. For a detailed explanation on how to set everything up, please refer to this page in our user manual.

TreeSize offers the possibility to use filters for this. Please navigate to "Scan" -> "Filter" -> "Customize filters". There you can define criteria to exclude files or directories.

 

Two examples:

1: Name     does not match     thumbs.db   would only include objects that are not named "thumbs.db" (= excludes files that have this name).

2: Full Path     does not start with     C:\Windows   excludes the "C:\Windows" directory and all its subfolders and files from the scan.

This is possible by using the advanced search and using the following filter:

Name     matches pattern     *.

In general, the exporting speed highly depends on the amount of data that is exported.

 

Exporting single files massively increases the amount of data for the export so if you do not need to include individual files, setting the export to only include folders and file nodes is a very good idea.

It is recommended to remove all columns from the export that you do not need.

Besides these factors, there are certain columns that are known to slow down the export by a lot. Especially SHA256 takes a lot of time but the MD5, "Owner" and the "Permissions" columns can increase the duration by a noticeable amount as well.

All entries (Page 4 / 22)