Logos 4 crashes upon startup

Hi, Logos 4 (on Windows 7 64bit) consistently crashes a few seconds into startup. The message comes on
Logos Bible Software 4 has stopped working. Windows is checking for a solution to the problem
I should also note that Windows had crashed on me, and this problem seems to have started after I ran the start-up Diagnostics on Windows 7. The diagnostic revealed no problem, and I have also run the Windows trouble-shooter, which also yielded no problem.
So far as I know I have the latest version of Logos 4
Gary Shogren http://openoureyeslord.com
Comments
-
You might have a corrupted database.
Try renaming C:\Users\Gary Shogren\AppData\Local\Logos4\Documents\qrjb4jej.1ik\Guides\guides.db e.g. to guides.old and restart L4.
If it does not work then delete the new guides.db and rename guides.old to guides.db, and contact Logos Support.
Dave
===Windows 11 & Android 13
0 -
Hi Dave, thanks. I don't seem to have exactly that file, but rather guides.db-10.bak and guides.db-journal.
Ahh...no, I see it now. This did the trick, thanks a lot!
Gary Shogren http://openoureyeslord.com
0 -
Gary,
Do you have software that automatically backs up your computer? If so make an exception so that it doesn't back up the Logos 4 folder. Then rename the Guides folder where Dave directed you to the .db file. When that is done restart Logos 4.
0 -
Tommy Ball said:
If so make an exception so that it doesn't back up the Logos 4 folder.
I believe the problem is solved, Tommy. But why do you say not to backup Logos4?
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:Tommy Ball said:
If so make an exception so that it doesn't back up the Logos 4 folder.
I believe the problem is solved, Tommy. But why do you say not to backup Logos4?
Errors
can occur if we are writing to files (like indexing or trying to
update) that are being backed up at the same time. I'm not necessarily saying
one must not backup Logos; obviously that is the user's prerogative, and I
would not tell someone they can't. I suggested turning the back-up off in this case (not having seen the resolution confirmation. . .my apologies) as a troubleshooting measure.0