Above mentioned EMLPROXY.EXE (from Quickheal Total Security) suddenly takes up 95% CPU, it is not killable from task manager and Resource Monitor. I get a "Permission denied" error.

I downloaded ProcessHacker (http://processhacker.sourceforge.net/index.php), and while it is able to (partially) terminate the selected process, it leaves behind a System Idle Process (PID 0) which still shows that 95% CPU consumption, however the actual resource usage drops to normal.

I tried to read this, but didn't understand much: https://blogs.technet.microsoft.com/markrussinovich/2005/08/17/unkillable-processes/

What is the reason for such unkillable process? Please help.

  • Possible duplicate of How to terminate System Idle Process? – DavidPostill Mar 9 '16 at 14:20
  • @DavidPostill: No, my problem is not that a system idle entry is present, my problem is that Task Manager and Resource Monitor CANNOT kill a process while some other 3rd party tool, partially can. Why so? – Spandan Mar 9 '16 at 14:43
  • Because they are different programs and so have different capabilities. – DavidPostill Mar 9 '16 at 14:45
  • @DavidPostill: That's interesting. I believe that Task Manager and Resource Monitor being provided by Windows, should have kernel privileges, which a 3rd party tool cannot have. It should only execute in user-level privileges. But my case seems to be the opposite. – Spandan Mar 9 '16 at 14:56
  • User mode programs can have threads that enter kernel mode as the result of a call to a Windows API function, or because of an external event: when a device driver needs to process an interrupt or DPC, the code runs in the context of whichever thread happens to be active at the time. – DavidPostill Mar 9 '16 at 18:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.