Business Hours

Monday – Friday
6 AM – 6 PM PDT
Local: 6:24 AM
Saturday 6 AM – 6 PM

Sign in

  1. Forgot your password?

Error Writing to File

Unable to install updates for Logos 5.

Article Details

Platform / Device

Windows

Operating System

Vista (or higher)

Version

Logos 5.0+

Recommendations

Related Tutorials

0:36 Logos & Windows 8
 

Related Articles

Installion Guide Unable to Update or Install Unable to Download Installation did not Succeed Diagnostic Logging for Windows Remote Assistance

Symptoms

When updating Logos, you may receive a message "error writing to file" which prevents the update from installing.

Problem

Logos is designed to be used as a standard Windows User, with "non-elevated" permissions. By default, we install to a sub-directory of your Windows User folder (C:\Users\owner). This means that your user account should "own" and have full permissions to access Logos files.

This error can occur if the permissions or ownership for Logos files have been changed. This may be caused by certain PC "Cleaning" or Security software. To fix it, we can either elevate the process or we need to repair the ownership settings on the Logos folder and files.

Solution

    Temporary Work-Around:
  1. Close the Logos software.
  2. Right-click the Logos icon.
  3. Choose "Properties".
  4. Click on the "Compatibility" tab.
  5. Check the box at the bottom, "run this program as an administrator".
  6. Click OK.
  7. Open Logos and attempt to apply the update.

This will "elevate" the process, and should allow the update to install, but this does not resolve the root issue. We would recommend fixing the root issue as a long-term solution by resetting the ownership of the Logos directory and applying to all child objects. You will find instructions for advanced users on the wiki.

If you are not familiar with this process, please do not attempt it on your own. Modifying ownership and permissions in the Users folder can be dangerous and may prevent access to other files if not done correctly. For help, please contact a Microsoft technician or your computer manufacturer.
Last Updated: 4/30/2013

Was this article helpful? Rate it!

[5]