Errors from Norton opening Logos and Verbum during update 41.0 Beta 2 (40.0.382)
Windows 11 machine
Norton went haywire again as it did updating 41.0 Beta 1. At least it didn't quarantine any files this time.
There were at least five error messages, I was only quick enough to capture a couple.
Is this just Norton behaving badly or an issue with Logos? If so is there a bug fix coming?
Too soon old. Too late smart.
Comments
-
It sounds like a corrupted system file.
Right click the command prompt, run it as an admin and type sfc /scannow. That will check for corrupted files and repair them. If that doesn't work, try Check Disk by putting chkdsk C: /r into the command prompt. That will check for other disk errors and repair them. There are other possibilities, but those are pretty easy steps that have a good chance of success.Using Logos as a pastor, seminary professor, and Tyndale author
0 -
I think you are correct in stating that Norton went haywire.
We would be interested to see some logs from Beta 2, where logging in ON by default, and some stability fixes have been included. But first tell Norton to ignore the Logos app.Dave
===Windows 11 & Android 13
0 -
@Dave Hooton Logging has been on. Logos and Verbum appear to operating normally now.
Problem only comes up when updating if that is what you are referring to by stability.
I believe I discovered how to get Norton to ignore Logos and Verbum, but know for sure until next update I guess.
Here are logs
Thank you Dave.
Too soon old. Too late smart.
0 -
Thank you @Justin Gatlin for the suggestions. Forgive my ignorance, but what "command prompt" are you referring to?
Too soon old. Too late smart.
0 -
The Windows command prompt. Just go to the Start menu and type "Command Prompt," then right-click it and select "Run as Administrator."
Using Logos as a pastor, seminary professor, and Tyndale author
0 -
The Windows command prompt. Just go to the Start menu and type "Command Prompt," then right-click it and select "Run as Administrator."
@Justin Gatlin Okay, got it. The process didn't find any problems.
Thank you though.
Too soon old. Too late smart.
0
