L10 still crashes
I still can't get L10 to work, and the LogosSetup.exe does not update since it seems to be the most recent release. (Cf here.) I even started with CTRL, and as soon as I sign-in, L10 quietly vanishes. I'm on Windows 11 Home with 16 GB.
Comments
-
Once I figure out what level (if i do) of upgrade, I will do a fresh install. You may want to try that if you didn't.
Macbook Pro M1 - 14.5 - 64GB Ram
Always latest of Logos
0 -
I am trying to avoid that for various reasons. If there's another way, I would like to explore that.
0 -
Could you please collect and post your log files?
Directions are here: https://support.logos.com/hc/en-us/articles/360027869132-How-to-Enable-and-Submit-Log-Files
Andrew Batishko | Logos software developer
0 -
Thanks, Andrew. Here's the zip:
0 -
Hi Lew,
I'm going to reach out to your email associated with your Faithilfe account to request an EventViewer log file. Please follow the instructions and reply with the requested information there.
Thanks!0 -
I am having the same problem. I cannot get any work done since this upgrade! This is not acceptable; Since I was not having this problem with L9, is there any way that I can simply go back to that edition? I don't see any books that I want, or features that I need, from L10 anyway. It is not worth the headache of being unable to do any work at all. I have already submitted two logs since this happened this morning. The last time it happened, I re-opened using the instructions for "Enable Logging." Just now, when I tried to click on an illustration, it did it again!!! Sending another log - My eye is starting to REALLY HURT!!!
0 -
I am having the same problem.
Sorry for your troubles! [:s]
The forums are (mostly) "crowd sourced" user support from fellow users. If you would like help, please create a new thread and provide appropriate details such as:
- What is happening?
- Are there steps to reproduce the issue?
- what Specific OS are you using?
- What specific version of Logos are you using?
You should also provide logs per the instructions in my signature line. If you are sending crash logs that pop up after the app crashes, that is good but it will not help YOU to get your app back up and running.
If you don't want to post in the forums, your best bet is to call Faithlife directly.
0 -
I'm currently working with FL about a fix. I also have become aware of someone else having the same type of issue. I'll let you know what the solution is.
0 -
I believe we found a solution. Originally, I was told to delete the Logos\System folder in %localappdata%. However, because of my installation, my Logos\System folder is somewhere else (in my case,
\). I deleted THAT folder, reinstalled from the MSI file, and restarted Logos. (The System folder gets rebuilt when Logos is started.) That seems to have fixed it.It's working so far. I hope my weird situation can be of use to someone else.
0
