SCOM Console crashes after October Windows cumulative updates – Resolved


There is an issue where after patching your Windows Server or Workstation machine with the monthly cumulative updates – you might see you SCOM console crash with an exception.


This affects SCOM 2012 and SCOM 2016



Log Name:      Application
Event ID:      1000
Faulting application name: Microsoft.EnterpriseManagement.Monitoring.Console.exe, version: 7.2.11719.0, time stamp: 0x5798acae
Faulting module name: ntdll.dll, version: 10.0.14393.206, time stamp: 0x57dac931




The KB article explains the issue:   

System Center Operations Manager Management Console crashes after you install MS16-118 and MS16-126



We have released updated patches for each OS now, including the latest branch of Windows 10 and Windows Server 2016.


Smaller individual hotfixes are available for:

  • Windows Vista
  • Windows 7
  • Windows 8.1
  • Windows Server 2008
  • Windows Server 2008R2
  • Windows Server 2012
  • Windows Server 2012 R2

At the following location:

(The Microsoft catalog requires Internet Explorer, FYI)


The fix was applied to the latest cumulative update for Windows 10 and Windows Server 2016:

For Windows 10 RTM:

For Windows 10 version 1511:

For the latest Windows 10 version 1607 and Windows Server 2016:


The Windows 10 and Server 2016 updates are available right now via Windows Update.

Comments (15)

  1. Curtiss says:

    Golly, what do i do if I’ve already installed the hotfix and the console keeps crashing

  2. Naman Puneet says:

    Hi Kevin,
    Would we see the problem on 2007 r2 consoles as well? Security patches were installed last weekend and the console crashes every time we try accessing the Web Applications under the Monitoring Pane.

    1. Kevin Holman says:

      I have no idea on SCOM 2007R2 anymore…. as I don’t support that or even keep it in my lab. It makes sense that it would affect it, since this is a HTML rendering issue…. it could affect ANY console application that uses HTML.

      1. Paul Arnold says:

        FYI, the KB3200006 patch fixed my SCOM 2007 R2 console.

        1. Naman Puneet says:

          Thank You Kevin, Paul. I will install the KB as suggested.

          1. Paulo Novoa says:

            Great ! Working fine…!!

  3. Kris Dakin says:

    This saved me opening a MS case. Thanks Kevin

    1. Kevin Holman says:

      If I had a nickel………………………… 🙂

      Glad it helped.

  4. derr says:

    Hi Kevin,

    Do I need to apply this patch fix KB3200006 to all Non-SCOM server as a fix to MS16-118?

  5. Lee Bowman says:

    Is this fix going to appear in the Windows 7 Cumulative Update Rollup? eg the December Update Preview?

  6. Rini says:

    When i go to the link i see the following for Windows Server 2012 R2

    – Update voor Internet Explorer 11 voor Windows Server 2012 R2 (KB3200006) Windows Server 2012 R2 Update

    Though the name is different and says its for Internet Explorer 11 is this still the right hotfix?

    1. Anthony Ashmead says:


      Yes for Server 2012 and 2012 R” it is an IE update.


  7. Andy Barzyk says:

    I am experiencing this issue running Windows 10 (1607). I have my OS fully patched to no avail. The download site does not have anything for Win 10.

  8. Yusuf Mangera says:


    Is their a fix for this yet?

    I’m running the SCOM 2016 console on Windows 10 x64 (Creators update – 1703)

    event logs

    Application: Microsoft.EnterpriseManagement.Monitoring.Console.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.BadImageFormatException
    at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(System.ComponentModel.IComponent, System.EventHandler`1, System.Object, Microsoft.EnterpriseManagement.ConsoleFramework.ConsoleJobEventArgs)
    at Microsoft.EnterpriseManagement.ConsoleFramework.ConsoleJobsService.JobThread(System.Object)
    at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
    at System.Threading.ThreadPoolWorkQueue.Dispatch()


    Faulting application name: Microsoft.EnterpriseManagement.Monitoring.Console.exe, version: 7.2.11822.0, time stamp: 0x5894b8b3
    Faulting module name: KERNELBASE.dll, version: 10.0.15063.0, time stamp: 0x461a0ff5
    Exception code: 0xe0434352
    Fault offset: 0x0000000000069e08
    Faulting process ID: 0x556c
    Faulting application start time: 0x01d2c7eddebae3d8
    Faulting application path: C:\Program Files (x86)\System Center Operations Manager 2016\Console\Microsoft.EnterpriseManagement.Monitoring.Console.exe
    Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
    Report ID: fa917c1d-9525-4191-8a39-4d3e382817f5
    Faulting package full name:
    Faulting package-relative application ID:


    Application ‘C:\Program Files (x86)\System Center Operations Manager 2016\Console\Microsoft.EnterpriseManagement.Monitoring.Console.exe’ (pid 13536) cannot be restarted – Application SID does not match Conductor SID..

Skip to main content