Stuck In Loop - Update Ready to Install, then No Update Available

I'm stuck in a loop. It began when the Logos icon appeared TODAY in the system tray to tell me an update was ready to install. I clicked on Yes to install. It immediately said, "No update available, system up to day."

Now, each time I try to start L4, I go thru the loop again... and it won't start.

It WILL let me start if I click NO & don't attempt to install.

Ctrl + clicking on L4 startup icon enters the same loop.

Any ideas?

Blessings!

BIll

P.S. after reading another thread on a similar (but not identical) issue I chose to rebuild index to see if that'd help... Under way, now. It claims 32 hours at present, but the 1st 31 hours will go by in the next 60 minutes. LOL. If only I could get the last hour to go by that fast!

Find more posts tagged with

Comments

Bradley Grainger (Logos)

I'm stuck in a loop. It began when the Logos icon appeared TODAY in the system tray to tell me an update was ready to install. I clicked on Yes to install. It immediately said, "No update available, system up to day."

Thanks for reporting this; we're investigating the problem right now.

Mark Barnes

I think the problem is for those who have update channel set to beta. http://downloads.logos.com/LBS4/InstallerBeta/Logos4UpdateScript.lbxdat doesn't appear to have been updated yet.

Rich DeRuiter

I'm stuck in a loop. It began when the Logos icon appeared TODAY in the system tray to tell me an update was ready to install. I clicked on Yes to install. It immediately said, "No update available, system up to day."

Now, each time I try to start L4, I go thru the loop again... and it won't start.

It WILL let me start if I click NO & don't attempt to install.

Ctrl + clicking on L4 startup icon enters the same loop.

Any ideas?

So you can start Logos, if you don't do the update first, right?

What happens if you start Logos that way, let it finish loading and then type "Update Now?" Will it update then?

It's also possible that you have a corrupted MSI file. It will be somewhere in the Logos4 subdirectories. If the above suggestion doesn't work, and you see an MSI file in there, try moving it somewhere outside the L4 sub-directory and run "Update Now" again.

Well, two ideas. Not sure either one will work, but something to try in 32 hours, if indexing alone doesn't fix it. [;)]

Russ Quinn

I think the fix to all of this is to execute the command "set update channel to default".

Mark Barnes

I'm pretty sure it's just that TPTB haven't updated the software on the beta server. Downloading manually from http://downloads.logos.com/LBS4/Installer/Logos4Setup.exe fixes the problem. Changing the update channel doesn't (presumably because Logos is already confused by then).

BillS

I'm pretty sure it's just that TPTB haven't updated the software on the beta server. Downloading manually from http://downloads.logos.com/LBS4/Installer/Logos4Setup.exe fixes the problem. Changing the update channel doesn't (presumably because Logos is already confused by then).

Mark's analysis / solution was right on for me. Nothing else worked.

THANKS, all!

I guess I got my answer to a much earlier post in another thread where we were all confessing to Compulsive Beta Disorder--I wondered why I'd ever "Set Update Channel to Default". [:D]

Well, I've run out of excuses to avoid work, so it's back at it, now...

Dave Hooton

I'm pretty sure it's just that TPTB haven't updated the software on the beta server.

Mark, why do you think it is related to the beta server as opposed to the update channel when one is not on a beta version?