Settings or default email account are not being saved upon program start

Problem


Sometimes, due to your OS group policy settings, access to some key locations that this program uses is not accessible. This causes the program to not correctly record its settings. For example, the program should remember the last email account that was used when you last quit the program and re-open it.

Typically, this issue cause the following errors in the logs as well:

System.Configuration.ConfigurationErrorsException: An error occurred loading a configuration file: Access to the path 'C:\Program Files (x86)\GearMage\Mail Attachment Downloader Pro v2.4\zxhvkvxu.tmp' is denied. (C:\Program Files (x86)\GearMage\Mail Attachment Downloader Pro v2.4\MailAttachmentDownloader.exe.config) ---> System.UnauthorizedAccessException: Access to the path 'C:\Program Files (x86)\GearMage\Mail Attachment Downloader Pro v2.4\zxhvkvxu.tmp' is denied.

You can look at the logs by looking at the log files in the logs folder (open it by going to Mail Server -> Logs button).

Resolution and/or mitigation

 
The program requires the following turned on:
  • UAC should be turned on
  • Virtualizing file and registry access to be enabled via group policy. You can re-enable this by turning on the setting as described here (http://technet.microsoft.com/en-us/library/jj852189(v=ws.10).aspx). 
When the OS is installed, the default setting for both of these are 'Enabled'. If you see any of these being set as 'Disabled' via say group policy or otherwise, it probably means that someone (eg. IT) has turned it off.

Turning these on should not cause any undesired effect to other programs, in fact it may help with other programs that have similar issues. If turning these settings on is not an option, we are considering mitigating this issue in a future update, however, we do not not have a specific timeframe for that at this point.

Regardless, please make sure you email us mailto:issues@gearmage.com and tell us whether this mitigation worked or not when you encounter this problem so we can assess the number of users hitting this issue.

Feedback and Knowledge Base