systeminformer VS dust

System Informer is a versatile system management tool designed to seamlessly monitor and analyze system resources, troubleshoot software issues, and identify potential malware threats. Offers system activity overviews, intuitive graphs, real-time statistics, active network connection monitoring, detailed disk access information, intricate stack trace analysis, and much more. evily2k describes it "like process explorer on steroids. Allows me to kill process that task manager would say access denied."

(VAC use to prevent you from playing with the below method, however it has since been removed from the support, but you should still use -insecure for the below method) You can also try using process hacker/system informer (github link) it's similar to task manager however right click on csgo.exe click properties and click on the the windows tab. From there you can view which library or process created a window.

This is not a false positive, there are security exploits in Process Hacker that are exploited by some cheats. I would suggest upgrading to the new version which is now called System Informer, where these issues are fixed. https://github.com/winsiderss/systeminformer

I've had it for well over a year and haven't noticed any ill effects. I find it handy for reporting when something has been added to startup or context menu etc, but I've never ran it "full time" as a task manager replacement. (Though for that purpose, I recently came across an app called System Informer that I like - https://systeminformer.sourceforge.io/)

Install system informer: https://systeminformer.sourceforge.io/

System Informer (formerly Process Hacker) might also have what you're looking for

https://systeminformer.sourceforge.io/

Try using dust https://github.com/bootandy/dust

Folks open to using gdu might like to try dust (6k stars), or even erdtree (1.4k stars) which is too recent to show up on lists like this and still a bit behind on stars. A lot of people seem to use starship (33k stars) though I'm personally oldschool on prompts. There are many other items on that list I'm not motivated to check.

The first thought I had was to use rayon for this. And looking at some prior art that does pretty much the exact same thing, it does indeed use rayon.

The dust CLI command (made with Rust) can do this too.

How does this compare to dust?

Happened to me this morning, something filled up my drive in minutes. I used dust[1] to look for large files while it was happening but knowing what was doing it would've been a big help.

[1] https://github.com/bootandy/dust

dust is also really nice.