Discussion in 'other anti-malware software' started by Jryder54, Oct 29, 2013.
PEGR, thanks again for a great explanation.
I am waiting for our QA lead to give me the okay to post for the beta testers to test the upgrade. If all goes well, I hope we can release on Monday (at the latest).
Any special Wilders offers still available
Okay, the beta update is posted for upgrade testing. Here are the changes since the previous beta build:
Trial is 30 days (this won't affect the beta testers who I presume are already activated).
Removed unused fields in the about box (these were related to when upgrades were available for version 3.5).
About box reports all four version numbers: I hope this is really working now so I don't have to explain why the version number in the about box differs from the one in the control panel. Our first attempt to fix it didn't work - it worked on the developer's machine, but not in QA because it only worked if the GUI was running as an administrator. Sometimes what you think will be the simplest fixes are not that simple
Modified help file: Should be up to date with the exception of some screen shots perhaps.
Made improvements to folder settings for Guarded applications: Went with a combination of the old and new ("Private (Deny Access)" for example).
Fixed an issue where upgrade was leaving the AppGuard protection turned off after reboot.
Updates should work even if Restore Points are not allowed (wish I could have included a progress indicator - maybe next release).
On the License Activation page, there is a "where is my license" link. This was incorrect.
There was a crash of the GUI if you tried to add a Guarded Application that had a path that was over 255 characters (I'm surprised no one from Wilder's found this, but it was found by one of our summer interns).
There was a crash to the service if you tried to add a power application that had a path that was over 255 characters (same comment as above).
Added Opera Launcher.exe to Guard List. This will result in multiple instances of Opera in the Guard List, but will protect Opera after an upgrade without rebooting the system.
One of the prompts that occurs during installation has some text describing how you need to customize the tray if you want AppGuard icon to always appear in the tray. This was not appearing in Window 8.1.
The "red-listing" feature was fixed so that if you add an individual file to user-space policy it will not be permitted to run even if it is digitally signed.
A cert with a blank Organization will appear in the Publisher List.
I'll see if we can get one to coincide with the release.
How is C:\ treated in regards to privileges by the OS? Is it treated as userspace, or system space? I ask this because AG does not protect C:\ since adding that to the policy would include the entire C drive. What would keep a drive by download from downloading to C:\ and executing. You can copy an installer to C:\, and install it from there with no problem while VS is in Lock Down Mode.
It is treated as System Space by AppGuard. So once a file is there, AppGuard won't block it, but a Guarded Application won't be able to copy a file there.
I knew AG treated C:\ as system space, but I was wondering how the OS treated it? I guess as long as AG does not allow anything to download to that location it will not be an issue. I was concerned about drive by downloads using that path to bypass AG protection.
I know you are testing the upgrade/update feature now built into the beta (especially since many had issues when it last upgraded/updated) but are you going to post a download link for this new beta? The previous download link you posted gives the previous version. I am testing the upgrade/update feature on my main machine but have an old laptop with a fresh install of Windows on it that I would also like to try this beta on...
Never mind. It does not really matter how the OS treats it. Since AG treats it as System Space as you said, it should not allow data to be written to that path from a guarded app. I just tested to see if AG would allow me download an executable through Firefox to C:\, and it would not allow it to write to that path so I guess that's covered.
I wasn't planning on it because we're not accepting any more beta testers. You could always download the old beta and upgrade to the new beta.
If all goes well, I will probably update the site sometime tomorrow with the latest beta.
Thanks for the quick reply. No big deal, just thought I would ask. I had thought about downloading the previous version and letting it upgrade, but I think I will wait until Monday (sooner if the site is updated before then).
I missed the call for testers so I'll just gave to wait but can't see in the change log about compatibility for Office 2013 x 64 protected view. Is it in there?
The fix for Office 2013 x64 is in there (it was in the original beta that's why it is not in the list of fixes in the latest beta)!
When I post the official release, I'll note all the changes since the 4.0 release.
Updated smoothly to version 22.214.171.124. No glaring issues noticed. Updated and rebooted without any issues.
I am happy to report the same here. None of the issues that I had experienced with the previous automatic update (which resulted in having to manually download and install) were observed this time. Great work!
Should my beta detect an update? If so, this is the second update my beta hasn't detected. I had to manually download and install the update before this one as well.
Nice to hear, thanks!
Updated to new beta. No issues. Running smoothly.
Beta update isn't working for me. It tells me it's downloading and installing and don't touch anything, and then nothing. I've waited 10 minutes and then rebooted and it hasn't updated. This update process needs to tell me what it's doing and when it's done. In my personal opinion it isn't yet ready for release.
PS No system restore on here. Win 7 x64
Where can I dl the latest stable version?
I am unable to update successfully to 126.96.36.199.
Previously reported about system restore point in Windows 7 64bit while updating is still there.
Separate names with a comma.