I am seeing the same. Scan "Failed" for build 839. Have not seen this with previous builds. It still fails after reboot.
It has been suggested that this may be an issue due to not having HitmanPro application installed locally, i.e., it needs to be downloaded before each scan. I am fairly certain that in my case it has indeed been downloaded as and when I run the scan...but for some reason it would appear that it no longer does that. Perhaps the source location has changed and it has not been updated in the HMP.A program? In a way I am glad that I am not the only one have the issue, unless those who are suffering from this are all suffering the same issue with their systems. As I think was said earlier, and perhaps elsewhere, hopefully Erik & Mark will be along to sort this out. Regards, Baldrick
Hi there I can confirm that downloading a copy of HMP to the local system (and making sure it remains on disk after the inital scan) resolves the 'issue'. So my guess that something has recently changed in HMP.A by design or due to a bug in the url that is called when a scan is requested AND HMP is not found locally, is most likely correct...but would be good if Erik or Marko could confirm/advise either way. Regards, Baldrick
I am seeing the scan failure also. It's the download that I believe is failing. Build 839 Win 7 x64 Pro Also tested in my two VM's 1. Win 7 x64 Pro Fails 2 Win 10 x64 Pro Build 1809 Fails
@deugniet, Perhaps you have HMP installed? If not, the issue may have been resolved. I can't test it, as I have HMP installed next to HMP.A, so the issue didn't show on my systems.
There were quite a few Windows 10 users who reported the scan issue, in the HMP.A stable thread as well. If you don't see the scan issue, the issue may have been resolved by now. Let's see what other users report.
That makes one wonder, what's different on your first mentioned system, on which there's no such issue.
Again I can (re)scan my Win10 laptop with build 839 CTP1 but I can’t scan my second Win10 laptop with build 779 (both HMP not installed).
HitmanPro.Alert v3.8.0 Build 839 Community Technology Preview 1 To Mark, Erik and Ronny, I use KeePass v2.41 and for autocompiling I use the Ctrl + Q keys. When I use this key combination, the letter Q is always inserted at the beginning of the password and the login does not work. Example: Q12345 instead of 12345. If you disable the "Keystoke Encryption" function everything works fine. Thank you and hello to everyone!
Scan now working on my computer as well. I ran a norton live update and rebooted before I tried HMPA scan. Norton installed a patch. Then after the reboot, HMPA scan worked. Not sure is this is why, but am glad it is working again.
Any alerts? I would make a guess Lockdown? In that case find keepass on the blue button -> applications and untick "Application lockdown" + reboot the machine, that should unlock the "lockdown" and should allow inline updates. (side effect it would also allow all other downloads of executables keepass might trigger and/or be abused for).
Yes, a lockdown indeed. It was not an inline update though; I updated by running the 2.42 installer myself.
Just a heads up about CryptoGuard v5, VMWare creates during the session, and at the shutdown, files ending with extensions .lck, CryptoGuard maybe thinks is a ransomware, and interfer with the correct VM shutdown, that doesn't happen with v4, but of course this a work in progress. Now that I think about, I remember to have seen ransomwares with that name extension in the past too. But in this case is unreleated, the .lck is for good.
The latest beta 839 absolutely wrecked my Firefox Nightly setup. Nearly put my profile back to a blank slate. Firefox Sync brought some stuff back in place but not everything. At first Firefox wouldn't even open and was throwing a Cryptoguard error. Changing to V4 allowed it to open, and that's when I noticed the issue.