SCOM 2012 R2 console issue with latest KB3185331


  • This post just to share my bad experience with the latest Windows update (October 2016).

    My server OS is Windows Server 2012R2(up to date at least until yesterday LOL) and my SCOM 2012R2 revision is CU11 (7.1.10226.1239)

    Yesterday, my server has been updated with latest KB. (KB3185331 & KB3188743) The first one ( is the issue (the second one, is a Silverlight update and isn't guilty as I tough at the beginning). Once installed and the server restarted, the management console  becomes unstable and finally crashes. Especially, when you select a dashboard view in monitoring.The only way to fix this was to uninstall KB3185331. So, at time I write these lines, DO NOT install latest KB3185331 on your SCOM server.

    Thursday, October 13, 2016 6:52 AM


All replies

  • The October "Security and Quality" updates also cause Operations Manager 2012 R2 Update 11 management console to crash on Windows 10 (1607) and Windows 8.1. We get a crash as soon as you click on Windows Computers under Monitoring.

    Thursday, October 13, 2016 7:17 AM
  • Exactly, we got the same issues and removed both updates to resolve the errors.

    KB3192391 & KB3185330 is related to the ntdll.dll crash.

    2008 R2:

    • Edited by TomvBr Thursday, October 13, 2016 9:22 AM
    Thursday, October 13, 2016 8:59 AM
  • +1 to this issue

    My system is only like CU4 or something like that, so the problem goes back much further than CU11 as well.

    Thursday, October 13, 2016 12:35 PM
  • Have the same problem here too, glad I'm not alone.   Windows 10 Enterprise (with October 2016 updates) and SCOM 2012R2 UR11.   I have not patched my SCOM servers yet so its just my workstation console that's broken.   Removing update KB3194798 on Windows 10 resolved the issue with the console crashing as there is no update KB3185331 for 10.

    App crash from the windows event log

    Faulting application name: Microsoft.EnterpriseManagement.Monitoring.Console.exe, version: 7.1.10226.1239, time stamp: 0x57bd213f
    Faulting module name: ntdll.dll, version: 10.0.14393.206, time stamp: 0x57dac931Exception code: 0xc0000374
    Fault offset: 0x00000000000f73f3
    Faulting process id: 0x2aec
    Faulting application start time: 0x01d22562f7567d41
    Faulting application path: C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Console\Microsoft.EnterpriseManagement.Monitoring.Console.exe
    Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
    Report Id: b98edeb9-463f-4725-9969-fe06f00ca0c6
    Faulting package full name: 
    Faulting package-relative application ID: 

    • Edited by golemb Thursday, October 13, 2016 3:56 PM adding more information
    Thursday, October 13, 2016 3:14 PM

  • I'm getting the same thing. Remote management console is crashing on Monitoring > Windows Computers.

    Removed KB3185331, KB3185279, & KB3188743, each one at a time, still crashing.  I haven't allowed the updates to the core systems so they remain unaffected.

    UPDATE:  I just uninstalled KB3192392 and the problem went away.


    • Windows Server 2012 R2 6.3 9600
    • System Center 2012 R2 Operations Manager Console 7.1.10226.1239 (remote console)

    UPDATE:  I allowed the updates back to our servers, which installed.  Added Hotfix: .  Problem resolved.  Thanks Ganiuro & MS

    Thursday, October 13, 2016 4:56 PM
  • Confirmed this is affecting SCOM 2016 RTM as well.

    Faulting application name: Microsoft.EnterpriseManagement.Monitoring.Console.exe, version: 7.2.11719.0, time stamp: 0x5798acae
    Faulting module name: ntdll.dll, version: 6.3.9600.18438, time stamp: 0x57ae642e
    Exception code: 0xc0000374
    Fault offset: 0x00000000000f1b70
    Faulting process id: 0x1ad0
    Faulting application start time: 0x01d225a05e90914c
    Faulting application path: C:\Program Files\Microsoft System Center 2016\Operations Manager\Console\Microsoft.EnterpriseManagement.Monitoring.Console.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: e0a91c19-9193-11e6-80f7-005056bb73ae

    Removing KB3185331 fixes.

    Thursday, October 13, 2016 10:43 PM

    NO ETA yet

    Monday, October 17, 2016 1:43 PM
  • Same issue here on SCOM 2012R2, UR7, server is 2012R2. I'm not at work but will update tomorrow.

    "Fear disturbs your concentration"

    Monday, October 17, 2016 5:07 PM
  • Monday, October 17, 2016 10:41 PM
  • By the way, the problem is every where the SCOM console is install.

    I had the remove the KBs on all my RDS servers and SCVMM servers to have the console working.

    I placed a call to MS and they are aware of the issue but have no solution for now.

    Tuesday, October 18, 2016 3:03 PM
  • We had the issue, too, uninstalling KB3192392 fixed it.

    "Fear disturbs your concentration"

    Tuesday, October 18, 2016 3:39 PM
  • MS has acknowledged it

    Our DSE says a couple of days for the fix.

    "Fear disturbs your concentration"

    Tuesday, October 18, 2016 4:19 PM
  • I've successfully installed the latest patches (including KB3185331) then applied the hotfix found here: and all seems now OK. On my side, this issue is gone. THXS Microsoft ;-)

    Wednesday, October 19, 2016 7:00 AM
  • has fixed the console on Windows Server 2012 R2. Mysteriously there seems to be a patch for every OS except Windows 10 version 1607, which remains unpatched. The console does crash on 1607.
    Wednesday, October 19, 2016 7:11 AM
  • I've successfully installed the latest patches (including KB3185331) then applied the hotfix found here: and all seems now OK. On my side, this issue is gone. THXS Microsoft ;-)

    Thanks for the update.
    Wednesday, October 19, 2016 11:42 AM
  • We're on Rollup 9 (SCOM 2012 R2, version 7.1.10226.1177) and I can confirm that I had to uninstall all three KBs mentioned here before it resolved the problem.

    Initially I uninstalled KB3185331 and KB3188743, rebooted, and was still getting the same problem (this is on Server 2012 R2). I then uninstalled KB3192392, as suggested KCStix, and it's working now. 

    Monday, October 24, 2016 5:12 PM
  • Anybody got this working on windows 10 1607?
    Tuesday, October 25, 2016 5:45 AM
  • Windows 10 version 1607 and Windows Server 2016 still do not have a fix.

    The German manageability and monitoring engineers' blog ( still says "This hotfix does not include a fix for Windows 10 1607 and Windows 2016. The product group is working on that as well with high priority, but there is no ETA yet. I will update this post as soon as there is a release date publicly available."

    Tuesday, October 25, 2016 6:51 AM
  • Running the console in "Windows 8 Compatibility" helps a bit, but not for all views.
    • Edited by Osterberg Thursday, October 27, 2016 7:11 AM
    Thursday, October 27, 2016 7:11 AM