These type of problems can occur, if the option "Force randomization for images" (mandatory ASLR) in Windows Defender is enabled, which overrides application specific settings.Activating this setting will disregard the compatibility information of the application and can cause the application to crash immediatly, or not start at all, as is the case with TreeSize.
To fix this, you can either disable this feature completely, or add TreeSize as exception to your ruleset in Windows Defender:
Open Windows Defender Security center and navigate to "App & browser control > "Exploit protection > Exploit protection settings". Under "System settings", you can deactivate "Mandatory ASLR", or use "Add program to customize" under "Program Settings", to deactivate this for TreeSize.exe only.
Other security software like Carbon Black may also be blocking Treesize or its installer.
Note that this issue should be fixed with TreeSize v8.0 or newer. Please update to the latest version if possible or contact us, should you still face this issue.
The user who should use TreeSize needs to have read access on the folders that should be scanned, or alternatively the user must be permitted to request the Windows backup privilege, which is the case by default for administrators. Using the Windows backup privilege TreeSize is also able to query meta data like size and last change date. It may be necessary to explicitly run TreeSize "as administrator". User do not need read access on the file content unless you want to use the TreeSize duplicate file search with options that take the actual file content into account, and not only the meta data of the files.
With Windows Vista / Server 2008 Microsoft introduced "Client Caches" with the SMB2 protocol in order to speed up the queries about gathering file and directory meta information on network drives. This approach helps also to utilize the available network bandwidth more efficient. However, these caches do always return an incorrect value for the NTFS hardlinks (always shown as "1").The responsible caches can be disabled by the following steps:
After these steps TreeSize should work properly with hardlinks. For further information about client caches please visit https://technet.microsoft.com/en-us/library/ff686200(WS.10).aspx