Crash: Logos 4 crashes after Microsoft Windows Updates

Logos Bible Software 4.6a SR-5 (4.61.0.3387) running on Windows XP with latest updates (until 12/31/13)

Windows Update installed the following updates today (1/12/2013) and afterwards Logos4 crashes while trying to start up. Since I remember that some time ago Logos was incompatible with certain MS .NET updates, I've noted updates to .NET software:

KB2393802, KB2729450 ( .net 2.0), KB890830 (MRT), KB982168 (.net 3.5), KB2742597, KB2757638, KB2742607 (.net 1.0 SP3), KB2656352 (.net 2.0), KB982524, KB2736416, KB956572, KB2758694, KB2604092 ( .net 2.0), KB2687499, KB2756918 (.net 3.0), KB2742596 .net 2.0

I did a system restore to before the updates and Logos 4 is now running. I've also disabled the Windows Update Service.

At this time I cannot afford to buy a new computer to upgrade Windows.

I'd like some help. Do I have to run with Windows Update turned off from now on in order for Logos4 to work or is there another solution?

Find more posts tagged with

Comments

Dave Hooton

Windows Update installed the following updates today (1/12/2013) and afterwards Logos4 crashes while trying to start up.

Logos 4 may have crashed for other reasons. If you still have the crash log please upload it - see http://wiki.logos.com/Diagnostic_Logging for details of uploading and where to look for the logos4Crash.txt file.

I'd like some help. Do I have to run with Windows Update turned off from now on in order for Logos4 to work or is there another solution?

Choose to be notified about Windows Updates without them being downloaded (in Control Panel). You then choose what updates to install.

Jim

https://community.logos.com/discussion/comment/451481#Comment_451481

I appreciate your time in responding to my post..

Logos 4 may have crashed for other reasons.

I went through this experience twice. Each time the updates were installed, Logos4 failed to complete its startup. When I remove just those updates, Logos4 runs fine.

I did not save the crash reports since I didn't realize they are erased when logos starts up. I don't really want to spend half a day repeating the whole thing again unless Logos is at a total loss for this happening.

Choose to be notified about Windows Updates without them being downloaded (in Control Panel)

This is the normal mode I operate in, but it doesn't solve anything unless I know exactly which update set needs to be avoided.

Dave Hooton

https://community.logos.com/discussion/comment/451533#Comment_451533

I did not save the crash reports since I didn't realize they are erased when logos starts up.

Crash reports are not erased except by another crash report. You could upload the latest + logos4error.log as that is cumulative and should have all crashes.

Dave Hooton

https://community.logos.com/discussion/comment/451533#Comment_451533

Choose to be notified about Windows Updates without them being downloaded (in Control Panel)

This is the normal mode I operate in, but it doesn't solve anything unless I know exactly which update set needs to be avoided.

You could avoid all .NET updates!

Jim

https://community.logos.com/discussion/comment/451564#Comment_451564

You could avoid all .NET updates!

Ah. I see your point.

Jim

https://community.logos.com/discussion/comment/451558#Comment_451558

Crash reports are not erased except by another crash report. You could upload the latest + logos4error.log as that is cumulative and should have all crashes.

I thought I read in the wiki that they were overwritten, but I must have read it wrong. Here's my file:3463.Logos4Error.log

Dave Hooton

https://community.logos.com/discussion/comment/451648#Comment_451648

I'm sure Bradley can decipher this:-

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Configuration.ConfigurationErrorsException: An error occurred creating the configuration section handler for system.serviceModel/bindings: Could not load type 'System.Security.Authentication.ExtendedProtection.Configuration.ExtendedProtectionPolicyElement' from assembly 'System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. (C:\Documents and Settings\Jim McDaniel\Local Settings\Application Data\Logos4\System\Logos4.exe.Config line 34) ---> System.TypeLoadException: Could not load type 'System.Security.Authentication.ExtendedProtection.Configuration.ExtendedProtectionPolicyElement' from assembly 'System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.

As you are running OK, it is moot to say that it is fixable OR that I'm running stably on all the latest .NET updates in Win XP. But it might be useful for the next time!