Thank you for this educational post as a reply to Rasheed187!
I think that is a bad idea. You take the wrong approach by wanting a crippled 3.1 hmp.alert because of other/similar products you want to run....
Yes, please see erikloman post: http://www.wilderssecurity.com/threads/hitmanpro-alert-support-and-discussion-thread.324841/page-310#post-2544708
W7-x64: For both my desktop and laptop the auto-update 3.0 build 209 to 3.1 build 340 went flawless!
HitmanPro3 disables Teredo Tunneling at installation time. It is mentioned more than once in this forum, but I think the user should get a message...
Auto update 3.1 build 338 to build 340 worked just fine, no issues so far.
W7-x64: Upgraded 3.1 build 336 to build 338 without problems (I skipped build 337). Running 3.1 build 338 does not show any issues so far. :)
W7-x64 with hmp.alert 3.1 build 336 Over the last few day's quite a few hmp.alert warnings (Event-ID 214) show in the Windows Event Log.
W7-x64: Upgraded hmp.alert 3.1 build 335 to 336 without problems. Build 336 is running fine with FF-x64 43.0b3, so far no issues.
W7-x64: Upgraded hmp.alert from 3.1 build 334 to 335 without problems. Build 335 is running fine, so far no issues.
W7-x64: Upgraded hmp.alert from 3.1 build 332 to 334 without problems. Running build 334 so far without any issues. GUI access to the alert...
YES it does!
As an example please see: http://www.wilderssecurity.com/threads/hitmanpro-alert-support-and-discussion-thread.324841/page-252#post-2502601
W7-x64: Installed build 332 over build 329 without problems. After the hmpa installation reboot, NO encryption orange border showed in Firefox...
I believe the developer stated several times that HMPA will disables 'Keystroke Encryption' if it encounters an other program that is doing...
What do you mean (based on what) that HMP.alert is causing so much false positives? In our environment there are 3 desktops and 2 laptops all...
Win10 users are advised by the developer to run hmp.alert 3.1 beta build 328 or the newer 329. http://test.hitmanpro.com/hmpalert3b328.exe...
Please see: http://www.wilderssecurity.com/threads/hitmanpro-alert-support-and-discussion-thread.324841/page-289#post-2537919 Is this applicable...
See post #7032 from erikloman: ............. Norton released update 22.5.4.x causing an Intruder Alert with (unknown) listed at various wininet...
W7-x64 Professional: No problems installing 3.1 build 329 over 3.0 build 209, No issues so far running 3.1 build 329
@erikloman Thank you for this clarifying response, but for now I am pleased not to be a Norton user!
That was my interpretation after reading post #7032 and that's why I asked the two questions.
@bjm_ No I have not received a reply. Because I am not a Norton user I let it go, perhaps it is a sensitive/complicated issue?
HitmanPro Beta Build 251 runs without issues on W7-x64.
So an upgrade W7 -> Win10 (same Windows product key) is automatically covered by the hmp license mechanism?
Separate names with a comma.
