Error message when I try to start Backyardeos

[agara]

Greetings,

I downloaded the latest program version to my desktop which loaded fine.  When I open the program I get the following Error message -

 

OPPS!  This is embarrassing.  An unhandled error has occurred.

 

An error occurred loading a configuration file; Access to the path 'C:\Program Files (x86)\BackyardEOSv3.1\m02bxqgd.tmp' is denied.  C:\Program Files (x86)\BackyardEOSv3.1\BinaryRivers.BackyardES.Camera1.exe.user.config)

 

Any help would be appreciated.

[agara]

Greetings all.  Thank you so much for your help.  I ended up creating a new directory and now it works great.

[s3igell]

This sort of Error is usually associated with either 1) stringent Security Policies, 2) stringent Anti-Virus policies during Installation, or 3) otherwise Failed Installation.

 

The best workaround is to Uninstall BYE, and then Delete the "C:\Program Files (x86)\BackyardEOSv3.1" directory.  Then, Reboot, and then perform another Installation attempt, and test the results.

 

If that doesn't work, then perform the same sequence again, but with your Anti-Virus App turned OFF.  As soon as your first Test BYE execution is completed, remember to turn your Anti-Virus back ON.

 

Even then, some PCs are setup with stringent Security Restrictions which don't allow for BYE to successfully complete its Installation Process from within the "C:\Program Files (x86)" directory tree.  So, as a last resort, Uninstall and then attempt an Installation into a different directory such as "C:\BackyardEOS".  This messes a bit with the standard Windows Directory Orgnization, but it usually does allow one to overcome the Security Policies that might be blocking the Standard Installation process.

 

Let us know the results...

[admin]

Windows corrupted the config file somehow.

 

Installing in a separate folder will solve this error.

 

Keep us posted,

[admin]

Actually s3igell is correct, this is a Windows security policy error, try running the app with admin privileges until you find the actual policy causing the error.