7.11 (7.11.0.0023) is Now Available

This update has made Logos unusable for me - I can't open any resources without Logos crashing.  Logs below:

3010.Logos Log Files.zip

For those who need to get some work done. I've found that it appears that Logos will function normally if you do a CTRL start and work in the minimum screen mode. Loading layouts will crash the program so avoid this.

Do we still need to do the special Windows command for the accelerated start up with this version?

Unfortunately, holding down CTRL doesn't make any difference.

Unfortunately nothing seems to work.  I get the blank screen, but I still can't open any resources - no matter whether the screen is full window or minimized.

I've also tried the following:

• Reinstall
• Reindex
• Recatalogue library
• Update Windows
• Update Java
• Check security permissions for the Logos folder

Have restarted the computer, have reinstalled logos and holding ctrl while starting. Nothing works....this is frustrating.

The only way to solve the problem for now, is a system restore to a previous version. I did it with Windows 10. But then the Home button still does not work. Which means that this bug goes back to previous versions.  I cannot understand that Logos does not keep the previous version available just in case of a flop like this one. A program like this one is, like some said, our bread and butter. Logos could have react better.

I'm on Windows. I've talked to someone at Logos and they said they've received a number of calls from Windows users last night and today.  They also said the issue seems to be related to a Windows 10 update.

I have three Windows computers:  Two very similar WIn7 desktops and one Win10 notebook.

The Win10 notebook is running 7.11 fine. It was on the beta channel.

One of the two very similar Win7 desktops can't start 7.11, even with the Ctrl key-click; It flashes "Preparing Library" briefly, then goes away except for the Logos.exe process. The other runs 7.11 fine. The difference between the two is the one that is working was on the beta for quite a while; the one not working upgraded from 7.10.

Me too - I did all the windows updates and .net framework updates and still the same thing.  Anytime I click on a resource, the program disappears and is nowhere to be found.

I have Windows 10 Pro. It worked earlier this morning, but I could not open it in the afternoon. That is BEFORE I installed the Windows update. I just updated windows to see if it would help, and Logos still won't open. I only get the initial blue "Logos 7" pop up, but no login, home screen, etc. Ctrl start won't work either.

And I'm not sure if it made a difference, but I right clicked on the desktop icon and select "open in file location," THEN Ctrl-started the program, holding down Ctrl from the initial double-click until the login screen appeared.

Andrew Batishko (Faithlife) said:

Travis Arnold said:

Actually, it worked when I held Ctrl down the whole time, from initial click until the sign in screen came up.

This is the current workaround to that problem. We are still working to find and fix the cause of this problem.

Nope, not even that works on one of my computers. Win7, SP1. Upgraded from 7.10 in the stable channel.

When I click sign in (after holding the Ctrl key), "Preparing your library" briefly appears and then disappears with no trace except the Logos.exe process in Task Mgr, going back and forth from 25% to 27% of CPU.

Logging enabled with the registry update method (js method failed). Attached is the only log it created.

7282.Logos.log

Andrew, any status updates on this?

Danny Baskin said:

Please give us some idea as to when this issue will be resolved.

Adam posted that "We are working on a Service Release, which we will get out as soon as we can."

Yes.

Such a bummer. I was trying to get a lesson written for tonight. Holding Ctrl doesn't work for me.

As this is apparently the Mother Of All Bugs, while we're waiting, how about letting the ones affected install 7.10 again? On the one of my computers that isn't working, I'm going to have to reinstall anyway, since I can't get 7.11 to start at all (in order to apply a service pack).

I am a computer geek, and do more than a little programming myself. Could you give an idea of what the problem is? Is this something a shiv could fix even as a temporary stop-gap, or is the problem related to library calls? I'm starting to think from reading this thread and others that its a security implementation issue. But that is why I'm asking if you could provide additional information to us out here.