I would like to report a possible issue with AppControl.
On my system (Windows 10), the original Task Manager shows a process related to WSL2 called Vmmem, currently using about 3477 MB of RAM.
However, this process does not appear in the list of processes displayed by AppControl.
What is unusual is that the total RAM usage percentage is identical in both AppControl and the Windows Task Manager. This suggests that the memory used by Vmmem is being counted in the total, but the process itself is not shown individually in AppControl.
I have attached a screenshot of both applications side by side to illustrate the issue.
Could you please confirm whether this is a known limitation or a bug?
Interestingly, for my own PC I have the opposite problem where a thing called vmmemCmZygote would appear on my own PC in AppControl, but strangely, not in Task Manager. After becoming very concerned, I finally figured out vmmemCmZygote was part of the Windows Sandbox and my PC was safe.
We use a Windows API for our data that should be 100% accurate every time so it’s strange it could somehow leave something using that many resources out completely. I’ll share this with our team and we’ll try to reproduce this, then see if there is anything we can do on our side to solve it since the data we show actually comes from Windows itself and should be 100% accurate.
Thanks again for taking the time to post these details so we can try to find a solution. AppControl not picking up something using resources is not acceptable.
@KarmaGame if you go to our “Apps” screen, then use the top search for “vmmem” does it appear there? Our team needs to know this so we can determine if this is happening with our Windows Service, or our user interface somehow.
Hi,
First, I would like to thank the appControl team. The tool is awesome!
Personally, I am in the case of OP where app control does not show the Vmm wsl process (whereas task manager does). It would be really great to have it in the next version, and if I am being greedy, the details of the WSL processes would make task manager useless.
I just followed up with our team on this. We think we know what’s going on here, and we think there is a solution for it. The fix probably won’t be in our coming update but we hope to fix it on the next one if we don’t run into anything super complicated.
We may release a pre-release today on Discord if you could test that one and confirm the issue is resolved. @Michael I can also just send the link to you privately here if you want.
While the processes (2) are recorded now, the disk activity is straying still, in two dimensions: 1) named COM surrogate 2) even that one does not show the full rate (missing e.g. 400 out of 600 MB/s)
