[FIXED] - The "Non pool used" value display by the client can be misleading

Issue - The value displayed by "Non pool used" can be much larger that it really is. The value is meant to represent any files that sit outside of the Drive Bender mount point folders (mount point folders are where the pooled files are located, for more information see - http://support.division-m.com/entries/20437652). When Drive Bender calculates this value, it taken the file size of all files in the pool, then subtracts this value from the total size of each drive in the pool, as reported by Windows. This first issue with this is the "slack space", although as of v2.3.0.0, Drive Bender does attempt to work out a files real drive usage, this does not always work as expected and as a result, a larger than expected values is reported. The second issue is that some users will get a further error when this final value is calculated, making the overall value even larger.
Workaround - You can check to ensure there are no files located outside of the mount point folders, sometimes the Recycle Bin folder can contain files/folders, and it is also possible that the System Volume Information folder can also contain files/folders. However if these are empty, and the value is still high, then the issue is likely to be the result of the calculation errors as detailed. One thing to note, this values does not affect the pool. Other than displaying the value on the client, this values is not used anywhere else.
Expected Fix - v2.4 Note that the way Windows calculates display space, this value can still be slightly incorrect.