HitmanPro.ALERT Support and Discussion Thread

@RonnyT
I have the same issue on two devices now. How to troubleshoot this?

 

It's a known issue with 1903 and "file save as" dialogs for browsers.

You can either save the file and use explorer to "rename" or disable keystroke encryption for the browser, but that defeats the purpose of secure browsing.
So either use 2 browsers one for download+disabled keystroke and the other as daily driver, until we've fixed the issue.

 

This happened to me once, yesterday. I did your first suggestion of renaming using explorer. Not a big deal and an easy workaround.

 

ok, good to know.

 

BTW, I noticed that during install of HMPA, I get an alert from SpyShelter about HMPA wanting to take a screenshot, is there any reason for this? Windows Explorer also gives this alert, but I just wondered about it.

 

Windows 10 1903 Cumulative Update KB4501375 fixes the Custom Views Event viewer crash. Works for me.

 

It's working properly again for me, as well.

 

I tried installing Alert again. First restart I got past the Windows logo, but then the machine got stuck on the spinning dots once again. As I cannot boot into Windows the only way I can recover is by restoring a backup. I do not have time for testing (or experimenting).

Unfortunately, Alert cannot run on my Windows 10 x64 1903 machines.

 

HMP.A is still running fine on my W10-1903 -b18362.207
Also two more 1903 machines are running HMP.A flawless.

 

Any issue with the keyboard encryption becoming the output as some members here have reported ?

 

Certainly an odd one, Krusty. If I recall you have that even on Win 10 clean install, no other softs, default Alert settings.

 

Yep, fresh install of Windows while using WD, first and only other installed security software was Alert. First restart stalled at the spinning dots.

Some may remember the drama I had trying to upgrade Windows. Until I left Alert out of the equation I could neither upgrade nor clean install Windows.

 

When I was trying out the free version of HMP.A, I also had boot issues. I don't have it installed now and everything seems fine.

 

Forgot about that.
It only happens on renaming a download, before storing.
But it's a minor issue, not a show stopper.

 

@Hiltihome

Thanks for the info.

 

Sorry to hear you had troubles with Alert, but I am glad I'm not the only one.

 

Thanks for your concern.

 

If it gives problems on a fresh install, maybe it's related to Memory Integrity:
https://www.howtogeek.com/357757/what-are-core-isolation-and-memory-integrity-in-windows-10/

 

Don't know. @RonnyT asked me to try a bunch of stuff. Trouble is in my case Windows won't start so my only option is to restore from a backup using Macrium Reflect recovery media, so pretty inconvenient and time consuming.

 

Memory integrity protection looks like a feature of Windows Defender Exploit Guard.

It wouldn't be unreasonable to suspect that there may be a conflict with HMPA in certain circumstances.

https://www.howtogeek.com/329700/ho...oit-protection-works-and-how-to-configure-it/

I have had Defender completely disabled by group policy for years, and I have no issues with HMPA on Windows 10 at this time.

 

Sup , been a while, anyhow , when will you guys fix secure desktop mode not working while running HitmanPro.ALERT in Windows7, its been a while since ive asked about this issue , thanks in advance

 

This seems to reproduce, besides that the sole feature of "Secure desktop" is to prevent keyloggers to steal you master password, as Keepass is already protected by our keyboard guard there is no (or even less) risk of keyloggers stealing your master password (Secure desktop has some implementation limits), we'll see if we can mitigate this in a future version.

 

HitmanPro.Alert 3.7.9 build 781 Release Candidate

Changelog (compared to build 779):

• Improved compatibility with third-party security applications on Windows 10 version 1903 (19H1). The latest Windows 10 update applies extra exploit protections on fontdrvhost.exe, which could cause the machine to freeze into a black screen when logging off.
• Improved Application Lockdown compatibility with the Microsoft .NET Visual C# command-line compiler (csc.exe).
• Improved exclusion capability of the Kernel32Trap mitigation (part of Process Hollowing mitigation). This system-wide exploit mitigation blocks applications that disrespect module load order.
• Improved Heap Heap Protect – our system-wide dynamic shellcode mitigation – to handle third-party hooks and compatibility with binaries packed with PECompact.
• Improved compatibility with return-oriented programming (ROP) exhibited in the OfficeTabLoader.

Download
https://dl.surfright.nl/hmpalert3b781.exe

Notes

• If you want to downgrade from build 839 CTP1 to this build 781, you need to uninstall build 839 first and remove this file: C:\ProgramData\HitmanPro.Alert\excalibur.db
• Let us know how this new version runs on your machine. We aim to release it coming Monday for general availability (GA).

Thanks!

 

I'm starting to get frustrated with the Keystroke Encryption which shows incorrect characters on the Save As dialog when you are trying to amend the saved name.
I'm sure I'm not the only one with this query?

 

It's a known issue with 1903 and "file save as" dialogs for browsers.

You can either save the file and use explorer to "rename" or disable keystroke encryption for the browser, but that defeats the purpose of secure browsing.
So either use 2 browsers one for download+disabled keystroke and the other as daily driver, until we've fixed the issue.

We're working on a solution but it's taking a complete overhaul of the Keystroke Encryption module as Microsoft changed some stuff under the hood...