FAQs & 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

These incorrect sizes can also be seen in the Windows Explorer.
This results from a limitation in the server message block (SMB) protocol which unfortunately always returns the information of the host of the share and not the share itself.

Thank you very much for your helpfulness.

The configuration of WER (Windows Error Reporting) to create a user-mode crash dump in case of an application crash is covered in this article from Microsoft in detail.

Basically, you need to create a new registry key for TreeSize.exe and define three values. You can copy these commands and run them in a commandline (cmd.exe) with administrator privileges to create the keys directly. You can also adjust the path to write the crash dumps to (just change D:\TreeSizeDumpFiles\):

reg add "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\TreeSize.exe" /v DumpType /t REG_DWORD /d 2
reg add "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\TreeSize.exe" /v DumpCount /t REG_DWORD /d 3
reg add "HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\TreeSize.exe" /v DumpFolder /t REG_EXPAND_SZ /d D:\TreeSizeDumpFiles\

All of our products are being developed in Delphi or C#. Although we use Log4Net with some of the components, they are safe to use, because the reported vulnerability applies to Log4J only.

None of our applications depend on Log4J or any other Java library and are thus not affected by this vulnerability.

This applies to all versions and editions of our applications (TreeSize, SpaceObServer, SpaceObServer WebAccess, HeavyLoad, SmartPOP2Exchange, Exchange Server Toolbox, SpamAssassin in a Box, SpamAssassin for Windows, SmartCallMonitor, SEPA-Transfer, ServerSentinel, and ShellBrowser). It is recommended to always use the latest available versions though to benefit from the latest patches, improvements, and features.

This can happen, if TreeSize has been installed on the system before, but on a partition that no longer exists.

To resolve this issue, please start the installer from a command line (or a Win+R-run prompt) with an additional parameter /DIR="C:\Program Files\JAM Software\TreeSize"

If the search does not return any results, but te search filter have been set corretcly, this could be due to a missing file content reader for Microsoft Office files. The reason for the absence of these handlers is in most cases a non-existent Office installation. 

If you do not want to install Office on your system, Microsoft provides separate filter packs to install these file handlers. These can be downloaded here: https://www.microsoft.com/de-de/download/details.aspx?id=17062