Logos 30 Beta 1 crashes on startup

Logos 30.0 Beta 1 crashes on startup. I restarted my computer and started Logos. I get the splash screen , but no layout. I am using Windows 10.

This is definitely not what I need when I am preparing to teach on 1 Peter 5:8-9 tomorrow morning! I am not sure what the practical application of "resisting the devil" means in the age of digital Bible study and sermon preparation.

Logs files are attached: 5460.LogosError.log

Find more posts tagged with

Comments

Harry Hahne

This version was working fine until I restarted the computer.

Harry Hahne

https://community.logos.com/discussion/comment/1276914#Comment_1276914

Is there any way to revert to the previous version?

Kevin A

Harry you could try holding the CTRL key on launch, that might give you some success logging in. You could also try installing Verbum with a minimal library and the resources you need to get you through until the end of the beta.

You could follow some of methods here (https://wiki.logos.com/Quick_Installation_onto_multiple_computers) that might help you reinstall an older version of Logos without having to download all your resources again.

And there is always the web https://app.logos.com

Good Luck :yes:

Harry Hahne

https://community.logos.com/discussion/comment/1276924#Comment_1276924

I did try starting with the Ctrl key with no success. It is odd that this version worked fine until I restarted the computer.

I am limping by with the Web app for my teaching preparation for Sunday.

Harry Hahne

https://community.logos.com/discussion/comment/1276917#Comment_1276917

Is there any way to revert to the previous version?

For the moment, I reverted to the official version 29 stable release by installing Verbum. Hopefully Logos 30 beta 2 will work on my computer.

Bradley Grainger (Logos)

Logs files are attached: 5460.LogosError.log

*** Application Crash ***
Program Version: 30.0 Beta 1 (30.0.0.0006)
Windows Version: 10.0.17763.0
.NET Framework Version: 7.0.10

It looks like you are using Windows 10 1809 ("Redstone 5"), v10.0.17763.10.

Microsoft stopped supporting that version of Windows three years ago: https://learn.microsoft.com/en-us/lifecycle/products/windows-10-home-and-pro

Logos only runs on supported versions of Windows 10 (or Windows 11); please run Windows Update and update to the latest version of Windows 10.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1276953#Comment_1276953

(Technically, you should only need to update to Windows 10 1903 to fix this problem, not 22H2, but since that is also unsupported by Microsoft you didn't officially hear that from me. 😀)

Harry Hahne

https://community.logos.com/discussion/comment/1276954#Comment_1276954

(Technically, you should only need to update to Windows 10 1903 to fix this problem, not 22H2, but since that is also unsupported by Microsoft you didn't officially hear that from me. 😀)

I suspected a change in the system requirements was the problem, but there was no warning to this effect. It would be good for the Logos updater to refuse to update to version 30 if the Windows version will not support the update. This used to be the case, such as when I tried to update an old computer from Logos 7 to version 8. When Logos 30 is release, the current behavior may end up trashing some user's Logos installation without warning, as it did mine.

Note that the Logos Minimum System Requirements support page (https://support.logos.com/hc/en-us/articles/360007506971-Logos-Minimum-System-Requirements) says that only Windows 10 Anniversary Update (version 1607) is required. So I assumed I was fine. I have not done the Windows update on this particular computer, because it would disable other software that I rely on and the disk space is limited. But Logos version 30 may force me to make a choice.

John

https://community.logos.com/discussion/comment/1276964#Comment_1276964

But Logos version 30 may force me to make a choice

Best Buy has Macbooks $250 off right now [8-|]

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1276964#Comment_1276964

It would be good for the Logos updater to refuse to update to version 30 if the Windows version will not support the update.

I agree. Your bug report helped us find a problem with that system. (So beta testing worked, I guess?) It may be too little, too late, but v30 Beta 2 should not install on your system because it's not supported.

Note that the Logos Minimum System Requirements support page (https://support.logos.com/hc/en-us/articles/360007506971-Logos-Minimum-System-Requirements) says that only Windows 10 Anniversary Update (version 1607) is required.

That page is out of date. It should have the same system requirements as https://support.logos.com/hc/en-us/articles/360007391412-About-Free-Support.

Again, thanks for testing and finding this documentation bug. I'll pass it along to our team and apologise for the inconvenience.

Dave Hooton

https://community.logos.com/discussion/comment/1276967#Comment_1276967

Note that the Logos Minimum System Requirements support page (https://support.logos.com/hc/en-us/articles/360007506971-Logos-Minimum-System-Requirements) says that only Windows 10 Anniversary Update (version 1607) is required.

That page is out of date. It should have the same system requirements as https://support.logos.com/hc/en-us/articles/360007391412-About-Free-Support.

It is a bit rude supporting only the latest release of Logos/Verbum (on a 6 week cycle) whilst potentially supporting 3 releases of Windows/MacOS (each Windows on a 12-24 month cycle). Especially if FL insist that e.g. v28.2 will not be supported if 28.3 is the latest!

EDIT: As no versions are in Maintenance (and has been so for some time), why are Maintenance items still being listed?

Mark Barnes (Logos)

https://community.logos.com/discussion/comment/1277035#Comment_1277035

It is a bit rude supporting only the latest release of Logos/Verbum (on a 6 week cycle) whilst potentially supporting 3 releases of Windows/MacOS (each Windows on a 12-24 month cycle). Especially if FL insist that e.g. v28.2 will not be supported if 28.3 is the latest!

What we're really saying here is that if a user contacts us with a problem in an outdated version, we'll ask them to update their software as a first troubleshooting step. That's usually what we (and MVPs!) have done in practice anyway.

why are Maintenance items still being listed?

That should be fixed in the next few days.

Dave Hooton

https://community.logos.com/discussion/comment/1277093#Comment_1277093

why are Maintenance items still being listed?

That should be fixed in the next few days.

Change noted.

What we're really saying here is that if a user contacts us with a problem in an outdated version, we'll ask them to update their software as a first troubleshooting step.

In Unsupported (following the tables) the statement "You may be required to update before receiving assistance." would only explicitly cover the items listed as such in the first Table. But there is an obvious gap between "Logos 9.17 SR-2 and earlier" and "The latest stable version" which could be explained under Supported, together with clarification of "current generation".

Harry Hahne

https://community.logos.com/discussion/comment/1276953#Comment_1276953

t looks like you are using Windows 10 1809 ("Redstone 5"), v10.0.17763.10.

Microsoft stopped supporting that version of Windows three years ago: https://learn.microsoft.com/en-us/lifecycle/products/windows-10-home-and-pro

Microsoft is still giving support on this version of Windows for enterprise customers until January 9, 2024 and extended support continues until 2029: https://learn.microsoft.com/en-us/windows/release-health/release-information#windows-10-current-versions-by-servicing-option. So if your policy is to only install Logos on supported versions of Windows, Logos should still install and run on older versions of Windodws for at least a few more months.

It is very bad form for Logos to install a software update that will not run on a currently supported version of Windows. At minimum, it would be good to give a notice to current users about this forthcoming change. Ideally the update should not install at all on an unsupported system. I can understand the policy when there is a major version upgrade, but not mid-cycle during a minor bug-fix release.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1277467#Comment_1277467

support on this version of Windows for enterprise customers

We support consumer versions of Windows.

Ideally the update should not install at all on an unsupported system.

That was a bug in v30 Beta 1 that will be fixed in v30 Beta 3. Thanks for your participation in the beta programme to find and report this bug so we could fix it.

Harry Hahne

https://community.logos.com/discussion/comment/1277476#Comment_1277476

support on this version of Windows for enterprise customers

We support consumer versions of Windows.

I can understand why you might choose this policy. However, most colleges and seminaries supply computers to their faculty and staff, so the enterprise support date for Windows becomes more relevant.

The school IT staff usually control when to update the OS software. In the past I have seen them choose not to update to the latest version of the OS, for example, if an update would break critical software or if it introduces bugs or if it won't work with certain drivers.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1276954#Comment_1276954

(Technically, you should only need to update to Windows 10 1903 to fix this problem, not 22H2, but since that is also unsupported by Microsoft you didn't officially hear that from me. 😀)

Logos 30 Beta 4 will relax the unofficial requirement to Windows 10 1703 (so it should now install and run on your Windows 10 1809 computer). We still strongly recommend running a supported consumer version of Windows 10 (or 11) for the best experience.