The last access date of a file is maintained by Windows. Since Windows Vista/Server 2008, Microsoft disabled the automatic update for the "Last access" date by default to improve system performance on NTFS formatteddrives. Because of this, the date won't be updated anymore if a file content is changed for example. That is also the reason why the last access date isn't a good indicator anymore for recent usage of a file.
For more information, see the MSDN homepage.
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.
Since Windows Vista and later, Microsoft enforces more strict security rules on the operating system. One side effect of this is that you may not see your mapped network drives anymore (Windows 8 and later), or they all appear disconnected (typically in Windows Vista and 7) in all applications that run with administrator privileges.
This is because Windows uses different user environments for non-elevated and elevated processes. There are some workarounds to gain access to those network drives anyway:
The Windows Explorer and the TreeSize drive list do show the space that is physically allocated on the drive while TreeSize shows the space that is occupied by all files under a certain path. Please make sure that you have the view option "Allocated Space" activated when you are interested in the physically allocated space.
Another possibility is that not all parts of the drive could be scanned due to access restrictions. Therefore it is highly recommended to run TreeSize as administrator. If you want to get notified if a folder cannot be scanned, please open the options dialog (File > Options) and enable "Show error messages during scan" under the option page "Scan > General". Turning on the Option "Track NTFS specific features" in the Options dialog may result in more accurate results, because it tracks e.g. hardlinks, but slows down scans. If a drive letter points to a sub-folder of a network drive, the allocated space (correctly) reported by TreeSize may also be much smaller than the physically allocated space on this drive reported by the Windows Explorer because possibly the whole drive is not accessible through the network.
Beyond the space that is needed for storing the files itself, additional space is used for storing management data like the File Allocation Table of the file system or the boot sector. It is not possible to free this space with TreeSize or any other tool. This is usually 0.5 - 2% of the occupied space.
Another possibility is that you are using a Software RAID - like Windows offers it - which spreads the data with redundancy over several disks. These disks will appear as one logical volume and the failure of a single disk will not cause any data loss. But for storing the redundant information additional space is needed, which cannot be used for user data.
A special characteristics of Offline Files can lead to wrong values for the allocated space of stub files. To avoid this, either ensure that the user which runs the scans has full read access to the scanned file system.
Another possibilty has been introduced with Windows 10 version 1903, the system reserverd storage. This space occupies about 7 GB by default and is used by Windows exclusively. It is not visible to other applications and currently not represented with the scan. You can check the size of the reserved storage in the "Storage Settings".