Problem after installing Security Update for MS .NET Framework 4

Today I was prompted by Windows Update to install an "important" security update for .NET Framework 4. I installed it, and a few minutes later started Logos4. It took twice as long to start Logos4 (over a minute, instead of the normal 25-30 seconds), and shortly after Logos4 started, I received the following error message:

Visual C# Command Line Compiler has stopped working.

Problem signature:
Problem Event Name:    APPCRASH
Application Name:    csc.exe
Application Version:    8.0.50727.4016
Application Timestamp:    49cc8b7c
Fault Module Name:    ntdll.dll
Fault Module Version:    6.0.6002.18005
Fault Module Timestamp:    49e03821
Exception Code:    c000012f
Exception Offset:    00009eed
OS Version:    6.0.6002.2.2.0.768.3
Locale ID:    4105
Additional Information 1:    9d13
Additional Information 2:    1abee00edb3fc1158f9ad6f44f0f6be8
Additional Information 3:    9d13
Additional Information 4:    1abee00edb3fc1158f9ad6f44f0f6be8

I re-booted my computer, with the same result. I'm running Vista Home Premium SP2, with all Windows Updates applied.

Logos4 still seems to be working OK. I'm not aware of any other programs affected. I can still run programs from the Windows "Run" command box.

Find more posts tagged with

Comments

Fred Chapman

Do you have Logos Diagnostic Logging enabled?

http://wiki.logos.com/Diagnostic_Logging

Doug Trick

https://community.logos.com/discussion/comment/182312#Comment_182312

Thanks for the very prompt reply. I'd not used
Diagnostic Logging before, but I did just now.

Here's the zipped .log
file.7752.Logos4.zip

Dave Hooton

https://community.logos.com/discussion/comment/182354#Comment_182354

Doug

If you don't get a response from a Logos developer then take this matter to Tech Support on Monday, referencing this thread.

Doug Trick

https://community.logos.com/discussion/comment/183365#Comment_183365

Thanks, Dave. On Friday afternoon, I did call Tech Support. They were unable to find a solution, and concluded that it's a problem with .NET Framework, and not specifically with Logos software. So I uninstalled Logos4, as well as all .NET Frameworks (via Windows "Uninstall a program"), and then to be sure, I ran the Aaron Stebner Cleanup Tool for .NET Framework. I rebooted, and re-installed Logos4 (along with its Prerequisites), but then it wouldn't run at all. (Up to this point, Logos4 would run, but it wouldn't syncronize over the Internet).

Well, I had created an image of my Windows partition several days ago, the evening before installing Windows Updates last week (along with the .NET Framework 4.0 Update which I think was what caused the problems) - so I backed up my data, restored the partition (basically returned my entire C: drive to what it was 4 days previously), and the problem has now gone away. Of course, Windows Updates offered up the various patches from last Tuesday (but this time for some reason there was no offer of the .NET Framework 4.0 patch!). So I did accept the updates, and it's all good now (apparently).

So thanks anyway for the suggestion. I'm sure glad that I had a recent backup image of my drive. -Doug

Dave Hooton

https://community.logos.com/discussion/comment/183516#Comment_183516

I'm sure glad that I had a recent backup image of my drive. -Doug

Always a good thing to have!