HitmanPro.ALERT Support and Discussion Thread

@erikloman
Please make sure the e-mail gets read before releasing the new version of HMP/HMP.Alert. Thanks!

 

The license period for a 3 PC product key starts at the moment you activate the first PC with it. So in your example, the 3 PC license expires on November 4th, 2016 for all 3 computers.

 

That's correct. Users with Windows 10 must use HitmanPro.Alert 3.1 for enhanced support.
I've updated the HitmanPro.Alert product page to reflect details of 3.1 a bit last week to give new users updated information. The Datasheet has been updated as well.
We'll be updating HitmanPro.Alert 3.0 users to version 3.1 soon. We're still chasing some stuff that we want ironed out before upgrading everybody.

 

About the ntdll copy
Norton makes a copy of ntdll functions. Many security products (EMET, MBAE, Alert, Sandboxie, etc.) detour ntdll functions to provide additional security layers. If an attacker uses Norton's copies, they bypass the detours of these security products so these additional security layers are gone. Specifically a usable exploit gadget with a syscall instruction is not a gadget that can be easily found in entire process memory (mostly only in ntdll). With Norton on the machine, these gadgets can be found quite easily. And these gadgets affect the protections provide by above mentioned products.
Since Norton is one of the most used AV products, this MAY be a problem (since it is popular). I am not saying this IS a problem, but it MAY be a problem in the future.

About the fix for Norton users
We issued an update specifically for Norton users to suppress the Intruder Alert. Basically this means that Alert cannot determine the origin of a hook because Norton decided to bypass ntdll. So for this specific protection (Safe browsing), Alert cannot provide an alert when Norton is on the machine. This because a hook on urlmon, wininet, etc. cannot be attributed to either Norton or a Trojan (both hooks look the same). So Safe browsing for Norton users is currently disabled. We are working on a fix to return this feature for Norton users.

Hope this helps.

 

Yes, that helps.

Thanks Erik.

 

@erikloman
Thank you for this clarifying response, but for now I am pleased not to be a Norton user!

 

I remember someone already reported this but I can't find the post.
The number of alerts is "...", security notification is "...", license is "...". I can't open the settings, nothing happens when I click the button.
What could be causing this? I've just reinstalled the system yesterday (going back to Windows 8 from 10) and it still happens.

 

This means that the service is not running. Please reinstall Alert.

 

I even reinstalled Windows, but I still have the same issue.
I will try to reinstall Alert once again.

Edit: Same problem.

 

Please check whether the HitmanPro.Alert service is able to start. Look under Administrative Tools, Services.

 

HitmanPro.Alert 3.0 Build 209
Released through automatic update.

HitmanPro.Alert 3.1 Build 328 BETA <- recommended for Windows 10 users
Released through automatic update.

 

(It says Error 1068: Dependency service or group failed to start)

 

HitmanPro.Alert 3.1 Builld 329 BETA

Changelog (compared to 328 )

• Fixed Application Lockdown (was broken since build 310)
• Fixed driver memory leak (introduced in build 322)
• Improved keystroke indicator z-ordering

Download
http://test.hitmanpro.com/hmpalert3b329.exe

Please let me know how this build runs on your computer

 

That means that the hmpalert.sys driver does not start. Please click on tab DEPENDENCY to show the dependencies.

 

Thanks very much, automatically updated my Windows 7 system.
However, the HitmanPro.Alert 3.0 download link at the SurfRight downloads page still offers 3.0.58.208
and the HitmanPro.Alert 3 Release History still mentions Build 207, not 208, nor 209.

 

Working on it. Thanks!

 

@markloman, @erikloman

https://www.wilderssecurity.com/thr...iscussion-thread.324841/page-280#post-2530879

https://www.wilderssecurity.com/thr...iscussion-thread.324841/page-281#post-2532746

 

HitmanPro.Alert, of course.

 

Ooops, did it again

 

HMPA 3.1 build 329 installed and working fine on Windows 10 x64

 

Try from an administrative command prompt:

net start hmpalert​

... and see if the driver is able to start.

 

"Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source."

 

Can you send me the hmpalert.sys file?

 

No problems updating build 329 beta. Also no problems with Firefox 42.0.

Windows 10 build 10240 x64/Norton Security with Backup v22.5.4.24