HitmanPro.ALERT Support and Discussion Thread

Nope. I backup crucial data to a NAS. If something goes desperately wrong I will reformat. So far I haven't had to reformat a machine in almost 2 years. But if I do, everything is on the NAS.

 

Upgraded 155 to 166 and rebooted. The only problem I had was Maxthon 4.4.4.2000 browser crashing. I was able to isolate the problem to the "load library" feature under code mitigations. Unchecking that option allows Maxthon to run. All of the other protected apps are running fine with all protections enabled.

 

Firefox crashed on my other system too now. No DEP or other alert though.

Erik,

I will send you a PM.

 

That link works for me.

 

No problems so far. Can't wait for the eventual release!

 

It works for me now to. I think it must have been down temporarily.

 

I rolled my machine back to a time before ever installing HMPA. Windows Media Player still gave me the intro screen you get when you run Windows Media Player for the first time. We can eliminate HMPA as the cause now. It was just a coincidence. It had to have been caused by an update from Microsoft.

 

Gettings this with BS Player when trying to open file.

 

HPA build 166 has the same issues with MediaPlayerClassic and SoftOrganizer as reported twice earlier.
Is this usefull information? Because there was no reaction whatsoever in the last couple of weeks.

Edit-1: FF 36.0.1 got a DEB mitigation issue at startup.
Edit-2: FF 36.0.1 got a SEHOP mitigation issue at closure.

 

Short feedback: Issue is fixed in Build 166. Only one alert and if I allow it, webcam works for metro apps.

Feature Request: Will it be possible in a future version, to have an whitelist for some apps, f.e. "allow every time" option in alerts?

 

Completely missed build 166. No problems updating (W7 64 bits).

 

Build 166-cpu near 8% during start flash .305 (W7 64 bits/build 166/Firefox 36.0.1).

 

A bumpy cpu-ride with build 166 (W7 64 bits/build 166/Firefox 36.0.1).

 

It must be flash. With two streams a spike of almost 9%. Streamhickups...

 

I had the same thing happen but I didn't see any update from MS for WMP but maybe I missed it I'll look again.

 

Strange behavior of hmpalert3b166.exe in my Dutch Vista system.
I got no automatic update, so I clicked on hmpalert3b166.exe.
It was started as an standalone application, so it did no install and there was no request to reboot.
In c:\Program Files\HitmanPro.Alert\ there was only one program and this was build 155.
I closed the hmpalert3b166.exe screen and clicked on the tray icon of HitmanPro.Alert.
It was still the screen of build 155.
Anyone seeing this also ?
After remove of build 155 and reboot I will retry the install of hmpalert3b166.exe again.


update:
No problems with hmpalert3b166.exe in Windows 8.1 and Windows 10, both 32bit
After remove build 155 in Vista (32bit) and reboot, build 166 installed without prpblems.

 

Remove hmpalert.exe from map: C:\Program Files (x86)\HitmanPro.Alert and try installing build 166 again. I use W7 64 bits so the map could be different.

 

I did already a remove of build 155, reboot and after that build 166 installed without problems.
So I can not test your suggestion.

 

HitmanPro.Alert 3 Build 167 Release Candidate

Changelog (compared to build 166)

• IMPROVED: IAF mitigation
• FIXED: LoadLib mitigation causing crash in Firefox and Maxthon (on some systems).

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

NOTE: Existing users are not automatically updated from build 155. This because we need more confidence in this new build. Once confidence has been established, the automatic update will be engaged.

Please let me know how this version runs on your computer

 

No problems installing build 167.

Still a bumpy ride (18% cpu).

 

18%? I see average of 1 or 2%.

 

Always 0 here...