HitmanPro.ALERT Support and Discussion Thread

That may be a nasty issue for non computer savvy users!
Even if they know how to boot into Safe Mode to run System Restore, most probably won't know how to block HMPA's update mechanism. In fact, I wouldn't know either! I think that info must be somewhere in this thread, but I wasn't able to find it.

 

On October 22, 2010, Microsoft ceased sales of retail copies of Windows Vista, and the OEM sales for Vista ceased a year later

In August 2018, Vista's market share was 0.6% of Windows' total market share, and thus 0.2% overall. https://en.wikipedia.org/wiki/Windows_Vista

Maybe update to a supported version of Windows?

 

In the registry find this key name: "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\HitmanPro.Alert"

Add this value: "AutoUpdate REG_DWORD 0"

 

Spoiler

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\HitmanPro.Alert]
"AutoUpdate"=dword:00000000

 

Thanks very much, Tinstaafl and Adric!
I hope I'll never need it, but if I do, it's good to know how to block HMPA AutoUpdate.

 

And just fyi, the code format that Adric posted is the correct form used in a .reg file.

But it can be confusing (it was for me the first time) if you are just trying to edit the dword value in the registry editor manually. That's why I wrote it out differently. In plain English, so to speak... same result.

 

Thanks very much, Tinstaafl.
Myself, I know how to use the Windows registry, both manually or with a .reg file. Your description plus Adric's .reg file format is perfect for anyone who might need it some time.

 

Last I heard, the HMP.A folks were still supporting both Vista and XP. So I am providing feedback to help with their (welcome) objective.

 

When making this registry change, bear in mind that if HMP.A is already offering you an update, you may need to disconnect the computer from the Internet, set a previous restore point, and reboot before applying the registry fix. I got snagged by this today: when I used System Restore to go back to 773, the registry changed back to a state before HMP.A updating was disabled, but I left the laptop connected (dummy! ) and HMP.A soon found the update again .

 

Rebooted a Vista PC tonight. Thought that HMP.A updating was blocked. It rebooted fine... and then I discovered that 775 had been installed.

So build 775 is 1 for 2 on the Vista installation front: it led to a black screen on a laptop a few days ago, but it worked without problems on a desktop. Maybe some under-the-hood fixes within the same official build?

 

HitmanPro.Alert is blocking Zemana AntiMalware 3.0 Beta:

Code:

Malware found:
Gen:Variant.Ursu.377658
C:\Program Files (x86)\Zemana\AntiMalware\AntiMalware.exe
Mitigation   MalwareBlocked

 

Yes, still, about 14 hours now ...

It is a FP (I think due to BD detection, EAM also suddenly flagged it as suspicious). Zemana has reported it and I asked if I could too, which I did.

Edit: Looks like HMPA doesn't refresh malware definitions too often, alerts every 5 minutes. I just disabled Anti-Malware for now.

 

The AM component should have never been implemented the way it was. I have mine turned off too.

 

What would have been a better way to implement it?

 

Hard Disk letter D problem with HitmanPro.Alert v3.7.9 build 775?














In safe mode not error

Good Sunday everyone!

 

Allowing the user a bit of control. There's no way to whitelist anything at all without turning off AM.

 

It would be helpful to know what that malware definition refresh number is. Okay, someone might say, there is no "set" time, in which case the answer should at least be an estimated average amount of time between refreshes.

How should it have been implemented, i.e. what about the implementation never should have been?

Edit: I'm sorry, I did not see Adric's response to this same question above.

 

I noticed that if I launch windows 10 camera app, it loads, but immediately closes (no error message). Same happens with Microsoft photos app. Did not have these problems build 771, for example.

 

Photo and camera app open and work fine here.
I'm running Windows Defender, not F-Secure

 

HELP!

HMP.A build 773 intercepted what it claimed to be an attack via Firefox on my wife's Windows 10 PC when she tried to go onto Google Maps. The HMP.A notification offers to run a HitmanPro scan, and she did that.

At the end of the scan, HitmanPro reported, contradictorily, that there were "no threats found" and that 2213 threats were "detected". (See screenshot.)



Hundreds of the files removed have to do with something called "HP Touchpoint Analytics" which HMP seems to have suddenly decided is spyware. It's requesting a reboot, but I am not allowing her to do that pending a reply to this post.

We can't get into System Restore to go back; we are getting an "access denied" error.

Wife is terrified that her computer will cease to work after the inevitable, eventual reboot. I am not so pessimistic, but I do want to report this issue and to get a reply from someone at Surfright about this massive removal of HP Touchpoint Analytics.

I can provide the scan log file privately. It's very large (691 KB).

Please tell me something (accurate) that will reassure her.

 

I had HMP detecting the same program on my machine You might like to read my post and the next few after.

https://www.wilderssecurity.com/thr...iscussion-thread.236732/page-326#post-2805912

 

Thank you very much @Krusty. It sounds like it's actually a good thing HMP.A detected this spyware.

I still hope that both of us get confirmation from Surfright that this is intended behavior on their software's part.

 

For the record, there has been no bad ramifications since removing the program from my machine. HP Support Assistant still runs and found an update yesterday.

 

I just noticed the same thing happening to me now.

 

Hi JEAM,

Please contact support@hitmanpro.com