Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

MMC Snap-in will not load most processes and throws an error on Windows 2008R2 x64. It gives the error:

mmc could not create the snap-in. CLSID: FX:{18ea3f92-d6aa-41d9-a205-2023400c8fbb} when opening server manager.

It also gives similar errors opening the event viewer, etc. I think that the .NET Framework is messed up but I can't narrow down the exact cause. Has anyone else seen this issue? I have a dmp file of mmc.exe but haven't been able to get anything meaningful out of it.

share|improve this question

migrated from Oct 17 '12 at 13:20

This question came from our site for professional and enthusiast programmers.

Check out this thread. It sounds like a corrupted update.

share|improve this answer
Yeah I Saw that but the weird thing is all of my system scans pass with flying colors. I have another machine that works and it doesn't have any references to that update. I am guessing because i'm on 2008R2 and not just 2008. – Tammy Jan 4 '11 at 16:02
Based on that and this:… it seems that this is often caused by a problem with a .net installation (more specifically a corrupted machine.config). In most cases, people seem to simply rebuild the machine; however, if that is out of the question (and you have some free time) would it be possible to uninstall and reinstall .net? – Bobby D Jan 4 '11 at 20:06
Well I think I figured out what is going on. Our application has a windows group that is assigned permissions on the GAC folders. When I delete the group the snap in breaks. The weird thing is that administrators still have access to the GAC according to the permissions but that doesn't seem to apply anymore when the group is deleted. If I go and remove the references to the group on the GAC security it also removes the administrators access. You are locked out of re-installing .NET since Server Manager does not open and its a part of the OS on Windows 2008R2. – Tammy Jan 5 '11 at 20:01

I was having same issue, but it worked just fine, when i removed .Net 3.5 from my system, and just by that removal everything got back to normal .. this looked to be a problem with .net itself, i have not tried to install 3.5 again when i will do that will update the thread

share|improve this answer
CLSID : FX: Snapins can not work without .NET, so you still have other version of .NET installed, isn't it? – rkosegi Oct 17 '12 at 11:46

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 HKLM\Software\Microsft\OLE\MachineLaunchRestriction

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.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.