M
Malcolm Lawn
Guest
I'm using MSE (Microsoft Security Essentials) on one PC as a temporary solution and its been working without incident until last weekend, after the usual definitions update.
Process Hacker 2, well known software that has been recommended for many years even on some PC security web sites, is now being seen as a hack tool with a "high" threat rating. Because I had MSE set to default it summarily quarantined the files concerned rendering the program unusable.
It took some time to work out what had happened and after full system scans with other security software on that PC and others I discovered it was only MSE that has any problem with it.
I was hoping this was some accidental MS definitions update mistake but the response persists even after a full uninstall of PH2, verified (MD5/SHA1) download and reinstall. Later I discovered other users with Defender rather than MSE were also reporting the same problem. Presumably both security tool use the same MS definitions.
We need an explanation from MS about this and, if it is as I suspect a false positive, the definitions to be updated to reflect that ASAP.
BTW if intentional whoever made the decision to include it should be made to stand on the naughty step. Not just for that either but also apparently missing the fact that Process Hacker 2 64bit includes the 32bit .exe as well. A scan of that provokes no such warning of "high" threat by MSE.
More...
Process Hacker 2, well known software that has been recommended for many years even on some PC security web sites, is now being seen as a hack tool with a "high" threat rating. Because I had MSE set to default it summarily quarantined the files concerned rendering the program unusable.
It took some time to work out what had happened and after full system scans with other security software on that PC and others I discovered it was only MSE that has any problem with it.
I was hoping this was some accidental MS definitions update mistake but the response persists even after a full uninstall of PH2, verified (MD5/SHA1) download and reinstall. Later I discovered other users with Defender rather than MSE were also reporting the same problem. Presumably both security tool use the same MS definitions.
We need an explanation from MS about this and, if it is as I suspect a false positive, the definitions to be updated to reflect that ASAP.
BTW if intentional whoever made the decision to include it should be made to stand on the naughty step. Not just for that either but also apparently missing the fact that Process Hacker 2 64bit includes the 32bit .exe as well. A scan of that provokes no such warning of "high" threat by MSE.
More...