Error Writing to File

Part 1: Backup your Logos Data

1. Right-click the Logos icon and select "Properties".
1. If you do not have Logos on your desktop, right-click the Logos icon on your task bar, and right-click where it says "Logos Bible Software."
2. Click "Properties".
   
   
2. Click the "Open File Location" button.
   
   
3. Move the Data, Documents & Users folders to your Desktop.
   
   
4. Delete the Logos folder.

Part 2: Uninstall Logos

Use Programs and Features to uninstall Logos.

Part 3: Re-install & Restore your Logos Data

Reinstall Logos from the Installation Guide.
If Logos was not previously installed, skip the steps below and sign in normally.

1. Logos may open automatically; if it does, close it.
   
   
2. Right-click the Logos icon and select "Properties".
   
   
3. Click the "Open File Location" button.
   
   
4. Move the Data, Documents & Users folders from your Desktop, to the Logos directory.
   
   
   1. Replace any files if prompted.
      
      
5. Open Logos & sign in.

There might be a problem in your Windows user permission configuration. We strongly recommend fixing the configuration issue as the long-term solution, by resetting the ownership of the Logos directory, and applying that change to all subcontainers and files.

Warning: Modifying ownership and permissions in the Windows Users folder can be dangerous and may prevent access to other files if not done correctly. Because you are modifying your Windows configuration, we may be unable to assist you. If you need help, please contact a tech-savvy friend, Microsoft technician or your computer manufacturer for assistance.

You can still follow the Temporary Work Around in the meantime.

Part 1: Find the Logos Data Folder

To begin, we need to access the Logos data folder in Windows Explorer.

1. Right-click the Logos icon.
2. Choose "Open file location" to open the Logos directory.
   
3. Click the parent directory in the address bar (usually "Local").
   

Part 2: Open Advanced Security Settings

You should see several folders in the Local directory.

1. Right-click the "Logos" folder.
   Your Logos folder may have a number next to it if you upgraded from a previous version.
   
   
2. Choose "Properties".
   
   
3. Click on the "Security" tab.
   
   
4. Click the button.

The Advanced Security Settings windows should open. You should already own this folder, but you're getting this error because one of its sub-folders or files is not inheriting this setting.

To fix that, we want to change the Owner of this folder and apply that change to all subcontainers and objects (even if the owner appears correct on this folder).

Part 3: Changing Owners

Note: The following steps will be different, depending on your version of Windows. Please follow the steps which best match your system.

Windows 10/11:

1. Click at the top of the window.
   
   
2. Click the button.
   
   
3. Make sure *your computer name* is selected.
   It will have a computer icon.
   
   
4. Click the button.
   
   
5. Click the button.
   
   
   
   
6. Select from the list and click "OK".
   
   
7. Click "OK" again.
   
   
8. Check "Replace owner on subcontainers and objects".
   
   
9. Click "OK" again, until all properties windows are closed.
   
   

Network Logins: If you log into your computer through an office network, these steps may be slightly different. In step 3, you will need to select your network, instead of your computer. If you're unsure, consult your Network Administrator before making any changes.

We do not recommend it, but you may be able to work around the behavior by using these steps:

1. Close the Logos software.
   
   
2. Right-click the Logos icon on the desktop, and choose “Run as Administrator.” (If Logos is pinned to
   the taskbar, right-click, then in the menu, right-click again on Logos Bible Software, and choose “Run as Administrator.”).
   
   
3. When the User Account Control prompts “Do you want to allow...”, click Yes.
   
   
4. When Logos prompts to install the update, click Yes again.
   
   

This will "elevate" the process, and may allow the update to install, but this does not resolve the root issue and will require administrator authentication every time Logos prompts to update.