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

I join the several others* who cannot restart Logos once the latest update is applied (7.11.0.0023). Rebooting the computer didn't fix it. Starting Logos while holding the CTRL key was only a temporary fix. The circle just keeps turning while Logos uses 25-50% of my system resources.

* See also "Logos Hanging With Latest Update" (https://community.logos.com/forums/t/154784.aspx ).

I appeal to the Logos tech team to recommend a fix as soon as possible. As a Biblical Studies professor, Logos is my bread and butter in the classroom. Thanks in hope,

Craig Broyles

PS I wouldn't want to have to call in sick tomorrow

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.

[Y][Y][Y]

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

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

Try the command Set Use Ngen to Yes and restart Logos. Thereafter you don't need to use the command.

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

Open with CTRL key held and try again

Try the command Set Use Ngen to Yes and restart Logos. Thereafter you don't need to use the command.

Thanks, Dave. What I was asking is whether we still needed to use that command considering this part of the release notes:

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

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

What happens if you hold CTRL until sign in screen appears then let go and select sign in? Does a blank screen appear? If so you can work with this screen i.e. open resources. You cannot, however, jump to full screen or load layouts. You can, however, re-size this screen.

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

I am another one who cannot use this new version. It crashes on start up.

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

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

Does this seem to be a windows only problem or is it showing in MAC as well?

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.

No, there is more problems left even after the system restore. Some tool buttons also stop Logos, like Psalm Explorer, Bible Browser, etc.

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.

Startup

• (Windows only) Added support for Windows 10 Fall Creators Update’s Controlled Folder Access. If Controlled Folder Access is turned on Logos Logs will now be saved in  %LOCALAPPDATA%\Logos\Logos Log Files and %LOCALAPPDATA%\Logos Log Files. Thread

Could this be a factor? Anyway I'm holding off updating for now.

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.

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

We've got a fix for this. We will be shipping an update soon, but I'm not sure yet of the exact timing.

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 use Windows 7 Pro and am having the problem.

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.

Mike, you are definitely experiencing the same problem. This will be fixed as soon as we can get an update to you.

Thanks!

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.

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

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.

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.

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

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

We've got a fix for this. We will be shipping an update soon, but I'm not sure yet of the exact timing.

Thank you very much!

Andrew, any status updates on this?

Andrew, I've never been so frustrated with Logos in the many years I've used this product. Many of us rely on Logos daily for our work and have made a considerable financial investment in its resources. It's not unreasonable to expect it to work without repeated crashing. Please give us some idea as to when this issue will be resolved.

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."

Andrew, I've never been so frustrated with Logos in the many years I've used this product. Many of us rely on Logos daily for our work and have made a considerable financial investment in its resources. It's not unreasonable to expect it to work without repeated crashing. Please give us some idea as to when this issue will be resolved.

Are you able to use the web app to do work in the meantime?

Andrew, I've never been so frustrated with Logos in the many years I've used this product. Many of us rely on Logos daily for our work and have made a considerable financial investment in its resources. It's not unreasonable to expect it to work without repeated crashing. Please give us some idea as to when this issue will be resolved.

I would love to give you a solid time for when we can resolve the issue. Unfortunately, we haven't been able to recreate the problem for ourselves, and we're still trying to collect information that will help us understand what is causing the problem. We will get an update as quickly as we can.

Andrew, can we send you any files from our computers that would help - like a log file or a dump file?

Yes.

Andrew, I am having the same problem after Logos update and a Windows 10 update.

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

Do they know how to reproduce the problem?

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

Hi Vance,

I'm sorry you are having problems, we are working very hard to get this fixed. You might try app.logos.com as a workaround until we are able to release an update.

Hey, I know we just got past the 500 year anniversary of the Reformation and so I don't want to rock the boat, but all you Catholics out there can ask St. Isidore of Seville to join in prayer for a faster resolution to this issue.  Pope St. John Paul II declared St. Isidore of Seville the patron saint of computer programmers.  Non-Catholics are free to join in too - it's a 2000 year long tradition!

Do they know how to reproduce the problem?

We have been able to determine the cause of the problem. So far we've reproduced two instances of the problem, and fixed one of those. We are currently working through all the possible places where the problem could occur.

Unfortunately, we won't be able to release an update today. I'm so sorry for the disruption in all your work patterns. Fixing this is a very high priority for us, and hopefully we'll have good news of a release soon.

Thank you for your hard work and we will keep praying for you.

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 prefer to use Verbum, because it seems to be faster than Logos for me. However, Verbum is still crashing when I open a saved layout even though I entered the Update Now command.

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.

Last week I updated my iTunes and similar. Plus Apple's error message was a bad download. Turned out to be a missing updated C redistributable from MS. 

I don't automatically update anything. 

Could you give an idea of what the problem is?

It appears to be a hang in WPF layout introduced in .NET 4.7. (Grid-based UI that worked fine in Logos 7.10 on .NET 4.5 can now hang in Logos 7.11 on .NET 4.7 with no changes in our application code.)

Since this (from our initial investigation) seems to be in Microsoft's code, the exact mechanism of the failure is not fully clear to us yet.

We've removed Logos 7.11 from automatic updates for Windows users while we continue to investigate.

I have Logos 7.11 and .net 4.7 and Windows 8.1 and Logos seems to work fine so far.

Microsoft seems t have .net 4.7.1 available, I don't know whether it is any better.