Windows 10 -- unable to upgrade Logos to latest version (Solved)

I upgraded my Windows 7 laptop to Windows 10, and it seemed to go smoothly. Then I opened Logos (currently 6.5 beta 5), and it downloaded the 6.5 RC1 update, but it's giving me an error when it tries to apply the update: "The installation of Logos Bible Software did not succeed."

This is similar to the error reported here in the release version: https://community.logos.com/forums/t/113639.aspxthe

So I downloaded the installer directly, and when I ran it, it reported that it got an error writing to file:

I looked for the file to see what its permissions were, and it didn't exist.

The directory path seems to have the correct ownership all the way down.

I checked disk space, and I have 20 G free.

Logs:

3122.DigitalLibraryInstall.log

1007.logossetup.log

Seems like it's not really a beta issue (because of the other report), but since I'm running the beta, I'm reporting it here. It's been several months since I've had time to be in the forums, so I'm not aware of any Windows 10 issues that might exist.

Find more posts tagged with

Comments

Dave Hooton

You crashed at a point where files are being written to the \System folder; which is later renamed to \6.5.0.0023 (for this RC1 version). So I suggest you delete the Logos4\System folder and start again.

I'd be interested to know if you still have a working beta 5 after the crash

Todd Phillips

https://community.logos.com/discussion/comment/753890#Comment_753890

You crashed at a point where files are being written to the \System folder; which is later renamed to \6.5.0.0023 (for this RC1 version). So I suggest you delete the Logos4\System folder and start again.

I'd be interested to know if you still have a working beta 5 after the crash

The System folder only seems to exist during the install process. It goes away automatically when I cancel out of the install.

The application still works fine. It is running out the 6.5.0.0018 directory. It tries to do an automatic update every time I start it, which is failing, but the app continues to work after that.

Dustin Pearson

https://community.logos.com/discussion/comment/753915#Comment_753915

Try right clicking on the install file and selecting "Run as Administrator"...most likely with the upgrade to Win 10 Windows defaulted the security settings back to the default which tend to be the highest and really restrict what can be done.

Todd Phillips

https://community.logos.com/discussion/comment/753927#Comment_753927

Try right clicking on the install file and selecting "Run as Administrator"...most likely with the upgrade to Win 10 Windows defaulted the security settings back to the default which tend to be the highest and really restrict what can be done.

I don't think that would fix the problem with the automatic upgrade not working. Plus, I've always been under the impression that Logos should never be installed as administrator because it would break the automatic upgrades since the main Logos app doesn't run as administrator.

Dustin Pearson

https://community.logos.com/discussion/comment/753933#Comment_753933

Administrator doesn't work the same as in the Linux world. And no it won't but it will tell you if you need to go in and adjust the settings.

So my suggestion, take it how you will.

Todd Phillips

https://community.logos.com/discussion/comment/753935#Comment_753935

-Solution found-

Because of Dustin's suggestion, I wanted to see what Logos has said about running the installer as administrator and Google directed me to this page:

https://www.logos.com/support/logos5/windows/error-writing-to-file

That page says to reset the ownership of the Logos directory (I had previously reset the permissions but not the ownership). I followed the steps for Win8 (I had to work around some of the steps that were different--finding the application directory isn't the same, plus my Logos is still installed in a "Logos4" directory).

Then I ran the standalone Logos installer with success!

So I guess the lesson is that Win 10 upgrades may cause this problem, and the solution is simple.

(As to running the installer as Administrator, it is suggested as a workaround in case all other options fail, but it doesn't fix the core problem.)

Thanks all for your help. I should have tried more Google searching last night, but it was late. [:P]

Dave Hooton

https://community.logos.com/discussion/comment/753963#Comment_753963

I should have tried more Google searching last night,

And I should have suggested the folder ownership as an alternative! Main thing is that Logos is working again.

Bob Soule

https://community.logos.com/discussion/comment/754095#Comment_754095

I have run into permission issues when using a Microsoft Account to logon to windows 10 opposed to a local account. When logging on to windows using a Microsoft account all of the files for my userid became read-only. Which caused problems with Logos as well as many other apps. I tried to fix by changing owner for my files which helped some but eventually had to recover my system.

See this Microsoft post:

http://answers.microsoft.com/en-us/windows/forum/windows_10-security/folder-and-file-permissions-changed-in-windows-10/38bb51a5-8cfb-4349-b635-0fdae1287eb0?auth=1

At any rate, using a local account to logon windows has worked well for me.

Dave Hooton

https://community.logos.com/discussion/comment/754720#Comment_754720

At any rate, using a local account to logon windows has worked well for me.

I never trusted the "MS account" logon and thankfully the upgrade from Windows 7 preserved the local accounts.

Dan Phillips

https://community.logos.com/discussion/comment/753963#Comment_753963

Just wanted to thank Todd Phillips. I just started receiving that error yesterday, after upgrading to Win10 last week. The solution he pointed to, massaged for Win10, seems to have worked.

Thanks!