Windows 10: Why is every thread about not being able to kill vmmem...locked?

Seriously,If you're no longer using WSL, or Docker - why does this thing still hang on to nearly 80% of the memory and you CAN NOT KILL IT?This is virus like implementation microsoft. Fix it and you wouldnt have to lock every thread raising this issue.Thanks kindly,Your friend.

:)

 

Kill thread of the System process

Certain protected processes - those critical to the stability of the OS - cannot be modified by user-mode programs, even those running as administrator or as the SYSTEM account. Therefore, you cannot kill or even suspend a thread of the System process without writing a kernel-mode driver. The Kill button on Process Explorer's Threads tab would stop the thread if it could, but if you try, you'll find that it can't.

Even if you could kill the thread, you shouldn't. Threads can hold exclusive locks on resources while they do something important. If a thread died in the middle of doing something like that, all other threads in the process would likely be left with that resource in an inconsistent state. Further reading: Understanding the consequences of WAIT_ABANDONED. This is bad enough in a standard user-mode process, but doing it to the OS kernel would be disastrous.

If you want to stop this driver from using your computer's resources, you should uninstall the driver as you would any other.

 

Vmmem CPU and memory usage are very high

Hey there!

Thanks for response. In short - what you are observing - Linux machine that you run with WSL2 runs in context of VMMem process - so if you run VSCode from within Ubuntu - there is no "code.exe" process but it's in context of "vmmem.exe" process - you started
"code" process inside WSL2 - Linux Virtual Machine, which is hosted by vmmem process - the more you run with WSL2, the more VMMem process will consume resources. Are you able to see this correlation? What happens with usage after you close VSCode?

Thanks!

Alex P.

 

thread lock

My problem is in viewing youtube vdeos the picture zooms to a small part of the picture as soon as play is pressed.

One suggestion somewhere was that the thread was locked which I dont understand and that I should unlock it to access overlay????