AppGuard 4.x 32/64 Bit - Releases

Moved conversation to this thread.

 

I must say the new AG website looks real good.

 

Yes, that is the consequence of getting 50+millions $ from investors/partners
But honestly if i was the marketing chief, i would change the formulation of some lines.

 

You are an AppGuard end-user so send a letter regarding the wording to operations\support.

 

It is just the "ALL" word , i guess they will keep it despite what i will say

p.s: at least they removed the "exploit" part

 

They should be moved to the exclusion list. Then again Windows Update handles updates for Office suite components.

 

I haven't even read the webpages because I could care less. There is only one person who is waging a persistent campaign to besmirch everything and anything AppGuard related. It's marketing materials of the same nature as the phrase "You are protected" that virtually every security soft publisher in the industry uses. There is not a single word in the marketing materials that is misleading if the person reading it qualifies what is being said. Things must be qualified and that is true of any marketing materials fore any product whether it is the track record of a security soft, the degreasing capability of a dish detergent or the advertised specifications for a Ferrari.

If a person doesn't like the wording, then they can write a letter to operations\support or simply not use the product at all. These issues have no influence whatsoever on our product sales.

 

ClicktoRun Office updates are not done via Windows Update. The .msi version of Office still uses Windows Update, but not the ClicktoRun versions.

 

I'm having difficulty getting Mullvad to work with AppGuard 4.4.6.1. Any suggestions?

 

In our testing Mullvad's client did not work very well even when AppGuard was not installed along side it. We reported the issues to Mullvad support many months ago but it appears that they never did solve their client issues.

Look in the Activity Report. If there are any block events associated with the Mullvad client (it uses command lines such as netsh or similar if I recall correctly), then please post them here. In particular, look for blocks of any Windows processes on the Guarded Apps list such as cmd.exe.

 

After another unsuccessful attempt to start Mullvad with AppGuard in Windows 7 x64, there wasn't anything new in the Activity Report. But after reading your first paragraph, it's now less important finding a fix, instead I'll be looking at other VPNs. Thank you for the reply.

 

When I tested the Mullvad client, it would take a very long time to connect - even without AppGuard installed. It would also not connect at all. I tried different ports and protocols and that did not resolve the issue. I reached out to Mullvad support and they basically had me re-do the things that I had previously done. I also made the extra effort to evaluate the Mullvad client on multiple systems to ensure that the client behavior was not system specific. The behavior was the same on all test systems.

I invite you to try Mullvad's client on a system with AppGuard set to permanently OFF or even uninstalled. I am curious to know if either of those cases completely resolve the Mullvad client issues.

I know from extensive testing that IVPN and its client work quite well with AppGuard. The IVPN client has a few minor quirks which I reported. Since IVPN has a very small staff they are commensurately very slow to fix bugs, but despite the bugs (one is just a graphics issue) the client works quite well.

 

When I've used Mullvad without AG installed, it was slow to connect, taking something like half a minute.
There was an occasional glitch, but it was usually stable, and passed numerous leak tests.

Yes, IVPN is the one I was planning on installing. Good to know it works with AG.

 

@justenough

If you wish I will purchase a month-long Mullvad subscription and re-test it.

 

+1 Yes, ivpn works AOK on my win7_64 along with AG_4461

 

Thank you for offering. I'd be interested in what you would find, and if you can get AG and Mullvad working together. It could just be something simple that I overlooked. On the other hand I've read good things about IVPN and would like to try it anyway.

 

@justenough

It isn't AG. It is the Mullvad client. In your case you can try unguarding cmd.exe by unticking it in the Guarded Apps list. Perhaps that will make a difference on your system.

I even removed a separate OpenVPN client which I use for split-tunneling and tested with AG in OFF and uninstalled. Mullvad takes at least a minute to connect always, sometimes will not connect and trying different settings\config does not improve things. It is the same as before.

It is throwing errors. I disabled even the firewall and it still doesn't work. It is the same issues as I covered with Mullvad support in the past. The error below is without AG installed, Windows Firewall completely disabled.

 

Good to know, thanks simmersK00L.

 

Lockdown, that's odd, since I haven't seen any of those problems with Mullvad, and doubt that they would still be in business if many people had your experience with it. I just did about 10 connection attempts with AppGuard protection turned off and the connection sites set to random countries, and it connects in about 25 seconds on all of them. I rarely have any problems with Mullvad once connected and it always passes leak tests. The only real problem I've had is getting it to work while AppGuard is running. You might have a conflicting program or Windows setting?

 

That is the result on 3 separate test systems so I don't know what to tell you. And we have Mullvad support saying they couldn't figure out what was wrong in the past. We're not the only ones who have seen such behavior from the Mullvad client.

You can:

1. unGuard cmd.exe in the Guarded Apps list
2. Make Mullvad a Power App

If neither of those work, then you'll have some decisions to make.

 

Sorry we've drifted off topic, thanks for your advice on using Mullvad with AppGuard, but one last thought: Could it be a Windows 10 issue you are having? From a cursory online search it looks like at one time there was a conflict there. I'm using 7 x64.

 

One W7 test system and two W10 test systems. I went over all of it again with Mullvad support. Everything was documented and submitted. It's a case of wait-and-see what they uncover. The last two times reports were made, we never received any reply.

You can make the Mullvad client a Power App. That means when it executes, any Guarded processes that it calls (such as cmd.exe) will launch un-Guarded. Please try that step and see if it resolves the issue.

 

I have not had anymore problems with Microsoft Word since disabling Memory Guard for Word. I think that is what was causing the problem. I think Microsoft is partially to blame though due to the their own design, or possibly a bug that is triggered after the memory block occurs. Word should not be so easy to break (for lack of a better description).

I do have another problem now that I have switched to a Metered Connection. Microsoft Office informed me it had updates available over a week ago, but they will not install. I get the warning message that I may be charged a fee for bandwidth (I don't remember the exact wording of the warning), and I choose yes to download the updates anyway. The updates will never install. I follow the instructions from Microsoft to restart the Office Application to apply the updates, but no updates are installed. I disabled AG so it's definitely not to blame for this. Temporarily disabling the metered connection is not an option because it will start updating to Creators Edition again which will eventually lead to problem.

I need to get my hands on an ISO that already contains Windows 10 Creators update, and burn it to a disk. A fresh install of Windows will hopefully save me a lot of headaches in the feature. I have not been able to find an ISO that already contains Creators Edition yet, so i'm not sure Microsoft has released one yet. I may just have to do a fresh install with latest build they have available on an ISO. I hate having to resort to this because it will take a long time to install the Office Suite, and all the other software I use for school, and update it.

 

When I added mullvad.exe to the Power App list, it seems to work normally, connecting and disconnecting by using a right click on the Mullvad icon in the Windows notification area. But the small Mullvad control window that's supposed to open on launch isn't opening.

 

Yeah, I started the media creation tool about 20 minutes ago. I just don't know which build I will receive. Hopefully it want download the same build I already have. I already have build 1607 on ISO. Do you know what the latest build available on ISO is?

I can't wait any longer because my classes start back in less than a week. I need to have a machine ready to go for school.