AppGuard 4.x 32/64 Bit - Releases

I can not speak for blue ridge but my understanding is that it is major version specific. I'm one of the ones all for AppGuard tho and don't care either way so my memory may be fuzzy. :-/
eg I think if you buy it while 4 is active you'll get all future 4.x versions but when 5.x is released a minor upgrade fee may be in the horizon.

 

Oh okay, that makes sense too. I just wish they were more upfront about it. Knowing these details certainly helps make the purchase decision more comfortable, but not knowing left me hesitant. Thank you for clarifying.

 

I think your correct Pete.

 

encore==> incur ?

 

It's definitely a one time fee for 4.x. We're considering a yearly subscription when we release 5.0 (date is still TBD).

 

Thank you so much for confirming, Barb. I really appreciate that. I may just take the opportunity now to purchase 4.x so long as it will still be supported for a while and as long as 5.0 isn't right around the corner.

 

4.x will be supported for

4.x will be supported for quite a while. 5.0 is still in the early stages of planning.

 

Are there any plans to add any additional mitigation methods into AG 5?

 

After launching IE on Windows 8.1 x86 and Sandboxie 14.5.4, the following pop ups and logs appear:

Code:

11/14/14 17:08:00 Prevented process <combase.dll | c:\windows\system32\rundll32.exe> from launching from <c:\sandbox\mrx\internet_explorer\drive\c\windows\system32>.
11/14/14 17:08:00 Prevented process <shlwapi.dll | c:\windows\system32\rundll32.exe> from launching from <c:\sandbox\mrx\internet_explorer\drive\c\windows\system32>.
11/14/14 17:08:00 Prevented process <imagehlp.dll | c:\windows\system32\rundll32.exe> from launching from <c:\sandbox\mrx\internet_explorer\drive\c\windows\system32>.
11/14/14 17:08:00 Prevented process <msvcrt.dll | c:\windows\system32\rundll32.exe> from launching from <c:\sandbox\mrx\internet_explorer\drive\c\windows\system32>.
11/14/14 17:08:00 Prevented process <user32.dll | c:\windows\system32\rundll32.exe> from launching from <c:\sandbox\mrx\internet_explorer\drive\c\windows\system32>.

Besides, every time IE is launched a SBIE2203 Service not implemented: NtCreateProcessEX (XXXX) error pops up along with a "Windows Shell Common Dll has stopped working" box, even though you close those dialog boxes if you keep running IE they still popping up every 2/3 minutes... really annoying.

 

Barb, anytime I uninstall AG, and then roll back my computer to an image that already has AG installed on it I have to activate AG with my license again. I did not have to do this until just recently. Is this expected behavior?

 

What happens if you don't install uninstall AppGuard online and re-image the PC?We lose an activation count.Isn't it?

 

As long as it shows the right number installations being used for one's license is all that matters. I have not gotten any message saying i'm trying to use my license on too many machines so all is good so far.

 

It would be nice if Barb_C can reply to this question on this thread

 

Unless Barb tells me otherwise then I'm assuming if you uninstall AG it removes that machine being associated with the license so you have to register again when you roll back to an image with AG already installed. The weird thing is I expected the licensing system to work this way all along, but it just started behaving this way this week for me.

 

Yeah, I'm waiting on a confirmation from Barb as well. We may not hear from her until Monday though since she is probably off for the weekend.

 

This is what i received from her a couple of months ago,when i asked the same question as Cutting_Edgetech did now.

 

That's exactly the way I thought it was suppose to work. I remember us discussing this in the thread several times. The weird thing is I never had to reactivate AG after uninstalling it, and rolling my machine back until now. All is good though. My license is still working.

 

Providing each activation registered on the licensing server is associated with specific hardware, I can think of no good reason why an available activation should be lost in the situation you are referring to where an image being restored to the same hardware didn't have AppGuard installed (not saying an activation won't be lost though - I don't know).

If uninstalled without contacting the licensing server to remove the existing activation, I would hope that it should be possible to reinstall on the same hardware without changing the activation count on the server.

Only Barb can confirm whether the licensing system does work this way, but in my opinion it should. What is certainly true is that if AppGuard is uninstalled without contacting the licensing server, an available activation will be lost if AppGuard is never reinstalled on the same hardware, however the licensing system works.

What I can confirm from my own experience is that if AppGuard is already installed on an image being restored then the activation count isn't affected when restoring the image on the same hardware. I have done this many times and have never had to re-register after an restoring an image with AppGuard already installed, or been told that I've exceeded the maximum number of activations allowed.

 

I restore the backup image(with AppGuard installed and activated) once every Month before MS Patch Tuesday,AppGuard used to retain its activation status with v4 then.But with v4.1,AppGuard doesn't remember its activation status,i have to re-activate AppGuard again and again.Why does AppGuard not remember the activation status when the backup image is restored to the same PC Hardware with v4.1?

 

I've got v4.1.45.1 installed so what I'll do is make a new Acronis image then restore it and see what happens. I'm on Windows XP though, so no longer affected by Patch Tuesday to the same extent as Windows 7/8. I'll post again after I've re-imaged and let you know the result.

 

Just try restoring the image after 3 or 4 days or may be a week so you could reproduce this issue.

Two Cases:
1.Uninstall AppGuard Online,restore the image and see what happens.
2.Just restore the image and see if AppGuard retains its activation or not.

I have been following Case 1 as a pre-caution.

 

Okay, I can try this. Out of curiosity, why do you think a delay of a few days before restoring is needed?