update from 38.1 to 39.0 fails on only one of my 3 computers

David Thomas · January 16

@Dave Hooton, I know there is a folder somewhere that I can clear the update cache and "re-trigger" an automatic update, can you (or any other user) help?

Everytime the update launches I get

Logs attached as

Logos.zip

38.1 seems to be fully operational on this computer. It is just stuck in the 2-3 backround update operations

John Goodman · January 16

It possibly could depend why it didn't succeed. The installer is in the Logos folder as an msi package. AppData/Local/Logos/Install/Installers/Logos-x64.msi You could try to run it a second time.

David Thomas · January 16

@John Goodman, Thank you for trying to help. Don't the logs that I attached reveal "why it didn't succeed"? I don't understand code to that degree. I've tried running more than 5 times, exit program, restart computer, restart logos, same message each time.

John Goodman · January 16

They give me a clue but I'm uncertain… Do you mean from within Logos or did you try running the file below with logos closed? Try again and then please let me know if it works.

C:\Users\pasto\AppData\Local\Logos\Data\ippurq4b.tei\UpdateManager\Installers\24121\Logos-x64.msi

David Thomas · January 16

I try opening the file you specified and am able to open

C:\Users\pasto\AppData\Local\Logos\Data\ippurq4b.tei\UpdateManager

but when I click on "Installers" the folder is empty

John Goodman · January 16

A guess is you don't have write permission for the Program Files dir? Is that possible?

David Thomas · January 16

I've had this computer for 5 years and used Logos on it the whole time. the update to 38.1 in December worked fine.

John Goodman · January 16

This new version adds files to Program Files dir which was never the case before though. Is Logos loading for you? If so, sit tight on v38.1 and talk to tech support. They are very good.

Bradley Grainger (Logos) · January 16

This new version adds files to Program Files dir which was never the case before though.

This isn't true as far as I know. Where are you seeing that in the logs?

Bradley Grainger (Logos) · January 16

@David Thomas here's the error from the install log:

Calling custom action LogosCustomActions!LogosCustomActions.CustomActions.RegisterStubMsixPackage

Installing MSIX package C:\Users\pasto\AppData\Local\Logos\Pending\LogosStub.msix to 

Installing: Processing 0%

Install failed: : This app package type is not supported on this filesystem


Windows cannot install package LogosStub_39.0.0.408_x64__1xye41dhr7sbj to volume D: with media ID {EA8BC127-0000-0000-0279-8E76C842B633} because it is not supported on this filesystem.

What is the filesystem of C: and D: (if you have a D: drive)?

In Windows 10, open Explorer, open This PC, find the C: drive, right-click it, and choose Properties. Under "General", look for "Filesystem". (Hopefully those instructions are the same for Windows 11 but I'm not at a Windows 11 computer right now to check.)

Aaron Hamilton · January 16

@Bradley Grainger (Logos) please note that this is not an isolated incident.

This situation appears to be identical:

https://community.logos.com/discussion/245383/install-box-opens-weird

This situation may be related, but I'm not sure:

https://community.logos.com/discussion/245388/help-with-ruined-logos-install-from-new-update

John Goodman · January 16

https://community.logos.com/discussion/comment/1353801#Comment_1353801

So on my win10 system Logos 39 added C:\Program Files\WindowsApps\LogosStub_39.0.0.408_x64__1xye41dhr7sbj

I had guessed that if the OP was on a managed profile they might not have write access to this dir.

David Thomas · January 16

Bradley Grainger (NTFS with almost 16 GB available.

David Thomas · January 16

Bradley Grainger (Logos) · January 16

https://community.logos.com/discussion/comment/1353880#Comment_1353880

Do you have a D: drive? If so, what filesystem is it?

(The install log only mentions D: in one place, but it's in conjunction with the failure.)

Frank Sauer · January 16

https://community.logos.com/discussion/comment/1353805#Comment_1353805

I am seeing this folder as well on Windows 11, but I cannot access it due to Security….

When I check the Security Tab, no option to add and my User permissions give an error about access control entry being corrupt….

Update - I was able to gain access to the the folder and have a LogosStub as well

David Thomas · January 16

@Bradley Grainger (Logos) thought I'd spell it right this time :D

D: is a MicroSD card (in a Microsoft Surface Pro 7) exFAT

I don't have ANY Logos data or program files on this drive.

For kicks and grins I tried running the installer and also ran a CheckDisk on c:

David Thomas · January 16

https://community.logos.com/discussion/comment/1353886#Comment_1353886

I ejected the Micro SD card (D: drive), restarted the computer so that Windows wasn't even looking for a D:, opened Logos and it updated to V.39!!!!! Even though I have no logos data on the removable drive, just having the drive on the system did something funky with the installer. A bug for developers to be aware of going forward.

Jack M. Tenney · January 17

Hi all

I am Jack Tenney from above about Ruined logos install from update. The Customer service tech told me the go to the downloaded logos install file R click on it and run as Administrator. That did it for me. I pray that this helps someone else.

Praise God Jack Tenney

Daniel R. Smith · January 17

https://community.logos.com/discussion/comment/1353953#Comment_1353953

Thanks Jack! That worked for me. It's been some time that I needed to "run as Administrator". It used to be my default when and install wouldn't work.

update from 38.1 to 39.0 fails on only one of my 3 computers

Comments

Categories