Microsoft Reduce Customer Effort Center

Our team drives product feedback based on solid data, it drives proactive issue prevention and ultimately, drives improvements around products based on customer feedback.

MMC issues after installing .Net security update

MMC issues after installing .Net security update

  • Comments 6
  • Likes


Unable to open the Microsoft Management Console, MMC fails with the message:

“MMC could not create the snap-in”.

MMC could not create the snap-in. The snap-in might not have been installed correctly.

Name: Server Manger

CSLID: FX:{18ea3f92-d6aa-41d9-a205-2023400c8fbb}




Some customers reported after install .NET update, the issue appeared, i.e

KB 2486109( was published for this issue.

This problem occurs if the .Net Framework 3.0 feature is not enabled and an update for .net framework 3.5SP1 is installed (which could be through the windows update or through a deployment tool).

If the above steps can not resolve it, use this method:


1. Navigated to the following directory:


2. Renamed machine.config to machine.config.old

3. Copy the same file from the working server.



Forum links:


A lot of threads found

Symptom 2:

After installing security update, the  MMC console opens but when you try to do anything inside you may get error "Microsoft Management Console has stopped working".

The following events are logged:

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 14/04/2011
Time: 08:32:53
User: N/A
Computer: cherami.mydomain.local
Faulting application w3wp.exe, version 7.0.6002.18005, faulting module 49e03238, version mscorwks.dll, fault address 0x2.0.50727.5653.

Event Type: Error
Event Source: .NET Runtime
Event Category: None
Event ID: 1023
Date: 14/04/2011
Time: 08:32:53
User: N/A
Computer: cherami.mydomain.local
.NET Runtime version 2.0.50727.5653 - Fatal Execution Engine Error (000007FEF21B6D36) (80131506)



  • If you never installed MS11-028 or have uninstalled it, you should install KB979744-v2 from here or here and then install MS11-028
  • If you still have MS11-028 installed, and your Exchange Management tools are currently broken, you should install KB979744-v2 from here or here


Edit: Please refer to for the resolution.






  • i try to edit machine.config.default  to machine.config.old.default

    buet getting error (you need premissiom to perform this action) try again

    i loged as domain administrator

    Please help

  • I have the same error even after renaming the config file

    I canot open event viewer and server manager

    Pls help

  • Worked for me, but I was already logged in as an Administrator.


  • Nice!!! Worked for me, I can finally can get some real work done.




  • I know this is an old post, but I ran into the same issue and tried everything I could find on the internet regarding this. After working with Microsoft for 3 days we found the fix. Please see below for all the steps that were completed, and finally what solved the issue. This was for a Server 2008R2 machine:

    MMC could not create the snap-in. The snap-in might not have been installed correctly.
    Name: Server Manager
    CLSID: FX:{18ea3f92-d6aa-41d9-a205-2023400c8fbb}

    Name: Event Viewer
    clsid: fx: {b05566ad-fe9c-4363-be05-7a4cbb7cb510} Event Viewer

    Name: Task Scheduler
    clsid: fx: {c7b8fb06-bfe1-4c2e-9217-7a69a95bbac4} Task Scheduler

    Name: Windows Firewall with Advanced Security
    clsid: fx: {b05566ac-fe9c-4368-be02-7a4cbb7cbe11} Windows Firewall with Advanced Security

    Microsoft Server 2008R2 SP1
    HP ProLiant DL380G6

    Replaced C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\machine.config with known working file
    Replaced entire C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\ folder with known working folder

    Ran System Update Readiness Tool for Server 2008 – all reports came back with no error

    Ran c:\Windows\Microsoft.NET\Framework\v3.5\WFServicesReg.exe /r /b

    sfc /scannow was ran, came back clean

    Ran .NET Verifier on all version of .NET, all came back verified successfully

    Reinstalled .NET 3.5 via CLI:
    DISM /online /disable-feature /FeatureName:NetFx3
    DISM /online /enable-feature /FeatureName:NetFx3

    Removed registry keys:
    HKLM\Software\Microsft\OLE\MachineAccessRestriction and

    Restarted “Start DCOM Server Process Launcher” service

    Replaced files dsadmin.dll and dssite.msc located at C:\Windows\winsxs\ with a good know version

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMCSnapIns\FX{b05566ad-fe9c-4363-be05-7a4cbb7cb510}\RuntimeVersion, changing value from "v2.0.40607" to "v2.0.50727"

    Final resolution from Microsoft:
    The Servicing stack of the Operating System was clean as reported by the Sfc output
    Uninstalling/Reinstlaling Visual C++ 2005/2008/2010 with a reboot took out of the picture Visual C++ library components
    The .Net Policy had the correct value under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\Policy\v2.0 - "50727"="50727-50727”
    Uninstalling McAfee didn’t help even after a reboot.
    The Components and Schema hive unloaded after a few reboots

    The IDNA trace that we gathered indicated that we fail due to a bad function pointer most probably returned by a .net component. After applying the Update and a reboot the issue went away which indicates we have a broken/damaged .net component on the server.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment