- Dołączył
- 26 Maj 2010
- Posty
- 15126
- Reakcje/Polubienia
- 50461
AppGuard_4_3_14_5
Download:An AppGuard update has been published. You should get see an announcement soon (if AppGuard is configured to check for updates). The version is 4.3.14.5. This basically fixes the update issues that we had when we rolled out 4.3.13.1.
There are a couple policy changes:
[LocalAppData]\apps\2.0 is excluded from user-space. These are where click-to-run applications are stored.
[LocalAppData]\apps\2.0 has been added as a protected resource.
Schtasks blocking messages are now ignored.
*.cmd files can be added as user-space exceptions.
As many of you reported, when we published AppGuard 4.3.1.13, the auto-update was too silent. It basically resulted in AppGuard being turned off and there was no indication that the installation was successful or complete. The reason was that the install was considered a major upgrade by the OS which turned off our service. Our update logic didn't handle it properly. Though the update was successful, there was no indication it was and AppGuard was turned off. We recalled the update (from the perspective of automatically updating, the release is still good and can be installed - just not through our auto-update feature). Anyway, we think this version will properly alert you that the update occurred and will prompt you to reboot.
A few minor bug fixes:
The GUI was crashing adding c:\windows\assembly as user-space folder (why you would do that, I don't know).
AppGuard was blocking but not reporting a user-space folder that had a wild card in the policy.
Signed applications were not being permitted from a user-space folder that had a wild card in the policy.
If a sub-directory of c:\windows was added to user-space, AppGuard was permitting unsigned applications to launch (but they were Guarded).
Zaloguj
lub
Zarejestruj się
aby zobaczyć!