Does Logos 8 still run on Windows 7? (I can't get past the splash screen)
I haven't tried to run Logos for quite a while. But today (April 9, 2020), I tried to open it and get nothing beyond the initial splash screen, which remains only seconds & then disappears. Nothing else happens.
In Windows' Task Manager, I see two "Logos.exe" processes running, but only momentarily. Then they exit.
I gather from the Forums here that Win 7 is no longer supported. But... does that imply that it no longer even launches?
Thanks for any tips,
Curt
Comments
-
The .exe file is tagged as 8.12.0.17.
Last time I accessed it was March 19.
And maybe I should add that I've tried holding down the Ctrl key while starting, and it has a curious behavior. Every-other attempt (with Ctrl held down) behaves exactly the same: splash screen, then exit. But the alternate attempts result in no display at all. HOWEVER, every once in a while (maybe every 6th attempt or so), I get a crash notification -- i.e., a small dialog window reading "Logos Bible Software has stopped working. Windows is collecting more information about the problem. ..."
0 -
welcome to the forums Curtis. Any reason why you have not taken advantage of the free upgrade that Microsoft is making available to Windows 10? https://www.microsoft.com/en-us/software-download/windows10 if you have a legitimate Windows 7 Lisence key.
Mission: To serve God as He desires.
0 -
Curtis McCorkle said:
I gather from the Forums here that Win 7 is no longer supported. But... does that imply that it no longer even launches?
Hi Curtis,
Since Windows 7 is no longer supported by Microsoft, it is becoming increasingly out of date as time goes by. This means few and fewer Windows 7 users will be able to run Logos 8, so it is not surprising if it fails to launch for any Windows 7 user.
This issue is described in more detail here.
0 -
Lynden,
Thanks for the idea -- though I'm afraid it doesn't appear to be free. In the past, I should have paid more attention to Microsoft's offerings, as I gather that there was a free upgrade for quite a while, but that it ended a couple years back.
But unless you see something on that (or another) Microsoft page that I don't see, then it isn't free.
I suppose the best solution is just to buy a new Win10 PC. I reckon it's not a terrible idea.
-Curtis
0 -
Joe,
Thanks for the reply. I do notice that the initial post from that link seems to imply that existing Logos installations should probably keep on working. Further, in the following discussion, that is the strongly-held interpretation of the original post.
And then, there's the fact that my own Logos installation on Win7 did indeed continue to work. At first.
But now it fails. I therefore wonder: what changed? Is it just me, or is this a widespread occurrence?
Given the lack of other people posting here, I guess it must be just me. But that is a distinct part of my question -- so probably I should make that explicit:
Hey, Logos Forum, is there anyone else whose Logos installation on Windows 7 recently stopped functioning? Does it give you the splash screen and then just exit? Have you found any solution, short of going to Windows 10?
Thanks again,
Curtis
0 -
Curtis McCorkle said:
Hey, Logos Forum, is there anyone else whose Logos installation on Windows 7 recently stopped functioning? Does it give you the splash screen and then just exit? Have you found any solution, short of going to Windows 10?
Curtis, just to let you know, you're probably not alone ... not being ignored.
In my case, I stayed on W7 but don't trust the security, and no need to 'do something' for L8. I basically remained on L7, pulled it off the net, and happy every since. For you, I assume that L8 is tangling with W7 recently (and FL doesn't do W7).
"If myth is ideology in narrative form, then scholarship is myth with footnotes." B. Lincolm 1999.
0 -
Denise,
Ah! That gave me an idea: try to start Logos while disconnected from the internet.
Alas, it makes little difference. The splash screen stays open a couple seconds longer, that's all.
:-(
0 -
Curtis
some logs might help, but starting normally; which means you first enable logging as per the linked article.
Dave
===Windows 11 & Android 13
0