I know about it and it has administrator rights.To install the driver need administrator rights and knowledge, or use the installer. Version without installation (zip) does not install the driver.
Yes, I still not see kprocesshacker in Services list and can not start it manually.We haven't found issues that could have been caused by any Microsoft updates. Do you still have this problem?I think, maybe Microsoft made same updates which block KProcessHacker driver. May developer check it?
On my other system (Win 10 Pro, x64) situation the same. I think problem in Avast, if it block driver it do it silently (no warning about virus or other other security reasons). I'll try uninstall Avast to check it, because switch off protection does not help.Microsoft is not likely to do such a thing.
You should switch to x64 ASAP and uninstall Avast (or any other security software you have). 32-bit is very outdated.
We have been discussing this with Avast over the last few weeks... Avast has agreed to notify users when our driver has been blocked but will not be unblocking the driver because it's able to demonstrate a flaw in their security software.I have contacted Avast about this and I'll update the thread if there's any new information.