Created attachment 148528 [details] Overview of C drive SUMMARY Whilst trying to analyse my disc usage, I was puzzle why the overview was showing ~947GiB used on C:, but when I selected C: it would show only ~112Gib used. This made it basically impossible to use Fielight to determine where the space was being used. If I selected the folder that contained a VM, Filelight would report only 1.2MiB being used, but there was actually ~449Gib in use. STEPS TO REPRODUCE 1. Make sure you have at least one VirtualBox VM with a disc image (VDI) of a reasonable size. 2. In Filelight, navigate to the folder that contains the VMs OBSERVED RESULT Only the log files are reported on. EXPECTED RESULT All files, including VDIs and VBox files to be reported on SOFTWARE/OS VERSIONS Windows: 10 21H2 19044.1645 ADDITIONAL INFORMATION None
Created attachment 148529 [details] Details of C reporting much less usage
https://binary-factory.kde.org/view/Windows%2064-bit/job/Filelight_Nightly_win64/ Can you try the nightly build please. I've made many adjustments to how the windows logic works that should ideally have fixed this problem already (just waiting for a release)
Created attachment 148551 [details] Missing DLL I downlaoded "filelight-master-1115-windows-msvc2019_64-cl.exe" and installed, but unfortunately it failed to run with a missing DLL, "KF5Declarative.dll". The previous install was from the MS App Store, not sure if that is causing problems.
Oh. Ah. There was some more restructuring which prevents the nightly builds from working until next week. At the same time there's going to be a new release a week from now anyway. I'll try to get that to the store quickly so we can see what's the status of windows support.
Thanks for the update and hardwork.
The new release should appear in the store in the next couple of hours. Let me know how that one works for you. It should say 22.04 in the help->about dialog.
That does seem to be working better, but there is still a large discrepancy of From the overview it shows me ~571.2Gb used for c: and when I go into that drive, it shows 539.6Gb in use (most of which are my VMs, at least those are getting picked up), but being 5-6% off on size seems...odd. The folders withing c: all seem to report correctly as far as I can tell, so I am not sure where the extrta ~31Gb is coming from. I also see one discrepancy between FIelight and Windows explorer. Filelight reports 8.8Gb for c:\Program Files, but Explorer only 5Gb. This would seem to be relaed to permissions as Explorer won't tell me the size of c:\Program Files\WindowsApps without elevation. Which raises the question, how can Filelight report on the size when Explorer can't? Still, the large files I logged the bug about are being picked up and that is the important thing. Thanks for the effort in resolving!
Thanks for testing. The discrepancy probably comes from unreadable system files, hibernate and pagefiles aren't readable by filelight even with elevated privileges. Marking this as fixed as the original issue is gone.