AppGuard 4.x 32/64 Bit - Releases

Right Click on the AG tray icon, and go to protection level. Set the protection level to off, and then try to update Process Lasso. If it updates then you will know AG is blocking it. If it fails again then it's something else blocking it.

 

Tried that -- didn't work either. So, it must be something else. As I mentioned above, it could be CryptoPrevent.

 

Ok, good luck finding the problem!

 

Any special AG settings to do this effectively?

 

Appguard should block Crypto Locker with it's default settings while operating in Medium, or high protection mode.

 

CryptoPrevent prevents the launch of executables from folders which AppGuard denies as well. It is the source of your problem, TomAZ. Since you already have AppGuard, CryptoPrevent is redundant anyway.

 

Where can I download the latest version?

 

You can get the latest stable version here http://www.appguardus.com/ The new beta was projected to be released around the end of April if that has not been changed.

 

Thanks, may I ask what av gets along with AG the best? I have AG installed alone currently on my daughters laptop, but just incase someone shuts it down I'd like something as a backup.

 

A new build of Shadow Defender was just released with track 0 virtualization, and virtualization of the hidden boot volume. I just added Shadow Defender as a trusted publisher in AG, and the publisher's name is blank in AG. Could someone else try adding the latest SD certificate to AG to see if you get the same results. I think something may be wrong with the latest SD certificate.

 

I have not used anything different than NOD 32, and WSA for years. I think AG works great with NOD 32, but I guess you already know that since you already use NOD 32. I have not used AG with WSA in a while so i'm not sure about that combo. I think AG should work great with most AV's.

 

Yes,i get the same result.

 

Why do you want to add SD to trusted publishers list ? Its installed in system space, so technically AG will not interfere with SD.

 

There was some big changes made with SD in this build. I was just trying to be safe. I already got a BSOD with this build of SD so I had to roll my machine back. I sent Tony a bug report along with the crash dump.

 

Thanks for letting me know! I guess I should report the certificate problem to Tony as well. I just sent him a bug report for the BSOD I got from the latest build of SD. I get the BSOD as soon as I try to enter Shadow Mode. I don't think it is AG related. I hope not anyways.

 

I reported the digital certificate problem to Tony asking him to check his certificate. If he sees nothing wrong with it then I will open a bug report with BRN.

 

The logical solution would be to contact the author of CryptoPrevent.

 

Tony got back with me, and said he could not find anything wrong with Shadow Defender's digital certificate. I will email BRN about it tomorrow, and send them the signed file. Maybe there is a bug.

 

I decided to go ahead, and report the certificate issue to BRN now. I was afraid I would forget in the morning. I'm guessing I will hear something back from them today, or maybe tomorrow. They are usually pretty quick to get back with me anytime I report anything.

 

Have you already checked if the signature on your specific file is okay?(Just in case you don't know: right-click->properties->digital signatures->details).

 

Have done that, but no response as yet.

 

As the end of April is almost here, I hope that Barb will soon arrive with some good news....

 

Yes, i've done that.