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

Question

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 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.

I have ran the sfc /scannow, and other things I found in similar posts but nothing has seemed to help. I can't re-install the framework since I can't get to the add/remove windows programs. Any ideas?

Answer 1

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.

Answer 2

Though i m late to comment,but i was having the same issue and it took me some time to search and surf through the net, but this is all due to .NET problem, as i was having .NET 3.5 and 4 installed on the system, and the specifically looked to be coming from 3.5, so when i repaired it does not help any ways, so i remved.net 3.5 and that put my system back into proper state and now i think i will search more on what this .net changes when it is installed and will update if there is any further comment

---

SAM

Answer 3

Though this might be already solved let me tell you what I did to solve this problem. I had exactly the same problem yesterday (June 28th, 2011)

I was able to solve this problem by the procedure below.

1. Navigate to the following directory:

     C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG

2. Copy the 'machine.config' file to desktop just in case before you go to 3rd step.

3. Rename machine.config to machine.config.old which is locating in the directory above.

That's it, nothing else is needed.

Thank you

Answer 4

Hi,

your suggestion worked for me too. After renaming the file to .old everthing works fine .

The only thing that I'm wondering about ist that no new machine.config file was created after starting the server manager.

Thanks

 

Answer 5

Great advice.  I was able to solve the problem by installing all of the latest and greatest software and services patches from Microsoft.  If that had failed, Akira's recommendation would have been my next step.

Answer 6

Wonderfull!! Thanks Akira..

Answer 7

This worked like a charm.   Was considering reinstalling 2008 because it was a fresh installation.

Answer 8

Its work!, Great advice, Thank you

Answer 9

on my server windows 2008 32bit  i can find file only (machine.config.default)

This is the file need to edit ? i try to edit this file to machine.config.old.default but its saying (you need permission.... try again)

 

how i edit this file

 

please help

 

 

 

---

Bino A Thomas

Answer 10

Try to rename this file. It worked for me also on 32bit plattform. File location is just diffrent.

C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config

Answer 11

i renamed the file still not workig for me 

how to solve this issue ????

---

Bino A Thomas

Answer 12

That fixed it!. Not even a reboot required. Thanks. This was wierd. It happened after a clean install from MSDN media which I have done dozens of times before. All I did is add all the updates found by Windows Update after installation.

---

KS

Answer 13

same here.

I just set about installing Terminal Services and started experiencing MMC issues.

I try renaming the machine.config like was suggested here and still the same issue.

Do we need to restart? or what else?

Thanks...

Answer 14

I uninstalled the .Net Framework 3.5 SP1 and reinstalled it and all is well. 

Answer 15

Unfortunately, our system is telling us setup.exe (or the redistributable) "stopped working" when we try this.

Answer 16

Would you mind sharing how you accomplished this?  All I can find is that .Net 3.5 SP1 can only be installed via the Server Manager.  Server Manager won't work with a broken .Net 3.5 SP1.  I cannot find a way around this.  Thanks in advanced!

Answer 17

Thanks to Akira Umehara for the fix!

Worked perfectly just remember to reboot the server after you have renamed the file

Have blogged about it here - http://myworldofit.net/?p=773

Answer 18

@SoHo Integration

Powershell.

> import-module servermanager

> remove-windowsfeature net-framework-core

> add-windowsfeature net-framework-core

I'm having the same issue. Though reinstalling net framework didn't help at all. No snap-in works. I can open an empty MMC, but as soon as I try to add a snap-in it crashes.

Answer 19

Though this might be already solved let me tell you what I did to solve this problem. I had exactly the same problem yesterday (June 28th, 2011)

I was able to solve this problem by the procedure below.

1. Navigate to the following directory:

     C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG

2. Copy the 'machine.config' file to desktop just in case before you go to 3rd step.

3. Rename machine.config to machine.config.old which is locating in the directory above.

That's it, nothing else is needed.

Thank you

This solution fixed my problem.....

Answer 20

I am having the same issue on several servers. 

On one server - replacing this file - machine.config  - with one from a server that was working, fixed that issue.

On 2 other servers, that did not work.

I've tried the renaming option and that did not work on either of the 2 remaining servers.

On one server i have tried the uninstall of .Net 3.5 via powershell - that method has just left me a broken .Net install now, it errors out on the reinstall with an error of 0x80070643, Fatel error.  s

I'm not finding any other solutions at this time. 

Anyone else have a different idea to try?

Answer 21

This Solution fixed my problem too..

1. Navigate to the following directory:

     C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG

2. Copy the 'machine.config' file to desktop just in case before you go to 3rd step.

3. Rename machine.config to machine.config.old which is locating in the directory above.

Thanks

Ruwan

Answer 22

BUMP

I have the same issue, is there a workaround ? The "Rename machine.config to machine.config.old" is not working in my case.

---

...

Answer 23

Its work!, Great advice, Thank you

Regards

Answer 24

thanks! its real cool solution)

Answer 25

Hi all, the renaming solution does not work. Are there any solutions? Really desperate here. Thanks.

Answer 26

It Worked for me.

Thank you.

Gonçalo Cortes

Answer 27

Solution worked for me too.  Thanks so much!

---

__________________ Austin Bynum VPIT TexasBank

Answer 28

Though this might be already solved let me tell you what I did to solve this problem. I had exactly the same problem yesterday (June 28th, 2011)

I was able to solve this problem by the procedure below.

1. Navigate to the following directory:

     C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG

2. Copy the 'machine.config' file to desktop just in case before you go to 3rd step.

3. Rename machine.config to machine.config.old which is locating in the directory above.

That's it, nothing else is needed.

Thank you

THANKS!! Just renamed the file (not even bothered copying it) and ALL WORKS NOW!

Answer 29

Thank You! worked a treat.

Answer 30

Thank you so much, that saved me as well!

Mark

Answer 31

Thanks very much!

Answer 32

I fixed this issue having to go a different route: I had this issue on 3 downstream WSUS servers. I had both the CLSID: FX:{18ea3f92-d6aa-41d9-a205-2023400c8fbb} error on launching Server Manger and also the CLSID: FX:{8b6499ed-0241-e032-6508-da4b1c879d7e} when launching the Update Services console for WSUS.

I could remote manage both the Server Manager and the Update Services console (so I knew both was working) but I could not do it locally on any of the three servers.

I tried the Machine.config rename thing from both the Framework and Framework64 directories of v2.0.50727, I copied a known good machine.config from a known good source, I created a new machine.config from the machine.config.default, and even disabled and re-enabled .NET 3.5.1 via the command line (even though 3.5.1 was not installed prior to this issue on any of the broken servers) all to no avail.

What fixed it for me was:  1) Installing .NET 4   2) rebooting the server and installing either the needed patch KB2533523 or KB2468871 (I had success in two separate instances with each).  This restored not only the functionality of the Server Manger but also the Update Services console. I then installed the remaining 8 patches that were needed and things continued to function normally.

Caveat - in one instance, where I had installed ALL NEEDED PATCHES at once on the local server after installing .NET 4 on the server, Update Services broke and did not give the CLSID: FX:{8b6499ed-0241-e032-6508-da4b1c879d7e} error on launching it, but just a simple "MMC could not launch the snap-in" with no error code. The other odd thing was that Update Services could then not be managed remotely but was shown as an installed role in Server Manger. I noticed in the Registry that the FX:{8b6499ed-0241-e032-6508-da4b1c879d7e} was not present in HKLM>Software>Microsoft>MMC>SnapIns so I exported the Registry key from a known good server and once that was imported the MMC came up fine but had NO WSUS INSTANCES showing on the local server. TO FIX - I had to remove and re-install the WSUS and IIS roles as somehow WSUS and IIS was damaged in the process. This last part was a minor inconvenience compared to wrestling with this for two days and I am just glad it is now fixed and I can access both MMC consoles/tools.

Answer 33

Brilliant. Thank you ! worked like a charm

---

Be real

Answer 34

Though this might be already solved let me tell you what I did to solve this problem. I had exactly the same problem yesterday (June 28th, 2011)

I was able to solve this problem by the procedure below.

1. Navigate to the following directory:

     C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG

2. Copy the 'machine.config' file to desktop just in case before you go to 3rd step.

3. Rename machine.config to machine.config.old which is locating in the directory above.

That's it, nothing else is needed.

Thank you

Спасибо!

Действительно, можно использовать как временный вариант решения проблемы с запуском диспетчера сервера и устранения ошибки "clsid fx 18ea3f92 .."

---

http://www.anodonta.com.ua

Answer 35

Great it worked for me Thanks aton

Answer 36

YES!!  Fixed it for me, too - such an odd problem.

Answer 37

It´s work!!! thanks!!!

Answer 38

You're the man! Solve the problem! Thanks dude.

Answer 39

Checked the security settings.  Tried the machine.config fix.  Nothing worked was going to reinstall but looked for the key on the non working wsus and compared it to to the key on a working WSUS.  There was an empty subkey called Type. Copied this key from the working WSUS server. CLSID: FX:{8b6499ed-0241-e032-6508-da4b1c879d7e} to the non working one and the MMC came up.  I hope this works for someone.  Wasted a lot of time trying to get the answer.

Answer 40

Hi Akira,

Its working but this is not permanent solution if this issue occurred on SQL 2008 server. best option is re install the dot net 3.5 Sp1. System will come to normal mode.

Thanks you 

Chaitesh Ushagama

Answer 41

Hi

I had this problem and solved it by running windows update

Answer 42

The Akira's solution works for me in Vista Home Basic.

C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config

Thanks you

Answer 43

Awesome, This worked!!

Thanks

Answer 44

Thanks you 

Obrigado!

Answer 45

Thank you! Akira. Your suggested workaround worked like a breeze!

PI Product Specialist

Answer 46

MMC Snap-in would not load for me because it was disabled by my administrator. I easily fixed this by following these steps:

=Manual Fix=

1. Open Registry Editor by opening "Run" and typing in "regedit"

2. go to the following Registry Key: "HKEY_CURRENT_USER\Software\Policies\Microsoft\MMC"

3. You should see a key named "RestrictToPermittedSnapins" change the value to "0"

4. Open Event manager and hope that it loads the snap-in's!

Hope this helped some people and sorry if I did now answer your question but this helped me and I just wanted to get this solution out there :)

==============

=Easy Fix UPDATED=

==============

Download the automatic snap-in fixer I made here: http://www.mediafire.com/download/rj69hqpe92fhs4p/Windows_Snap-in_fixer_%7BBy_Callum%7D.rar

-Callum

Answer 47

sorry for Thread necromancy but this Works! Thanks PriitPK Totally worked for me

Answer 48

Thanks a lot man! It worked great. I know this is old post but still excellent.

Answer 49

I tried renaming machine.config to .old in both 32/64 bit .Net folders to no avail. Uninstalling .Net 4.5 via Control Panel fixed the issue

Answer 50

Thanks for the solution.  I actually deleted my machine.config file.  Initially I couldn't bring up the Server Manager.  After trying several times, something kicked in and it started working!  Such an easy fix.

Answer 51

Akira,

Thnx for the Solution, I also found the same on the MS KB "http://support.microsoft.com/kb/2486109"..

But post performing your solution & MS KB solution it didn't worked for me before reboot.

Post reboot it just worked Amazing..

Thnx Again :)

---

Vicky Rajdev

Answer 52

This setting is worked for me.

Thank you,

Prashant Upadhye

Answer 53

Akira, thank you for your help, it worked fine for me too!

Answer 54

Thank you ! This worked for me. 

Answer 55

I got the same type of problem on one my server, I am not able to Eventvwr, Services, Server Manager etc. as all depend on MMC. I ran the command sfc/scannow but no luck it didn't fix the problem.

I have copied the entire folder Microsoft.NET from Location C:\Windows and copied to the effected server and closed all the open window. After that I tried to open the System Manager it open without any issue.

I can now open all the MMC window.

Thanks for your support.

Answer 56

hi

but i have file name like machine.config.comments,machine.config.default

Answer 57

I had the same problem after an upgrade from Server 2003 to Server 2008.

The fix for me was to update .net from 4.5.2 to 4.6

After this update, no more errors

Answer 58

Same problem on server 2012 after power down.

I tried to rename machine.config but it didn't help.

Fixed by installing .NET 4.5.

Answer 59

hi all ,

i was having the same issue and i tried all solutions on the internet i reached to the last page on all search engine with no result even Microsoft support wasn't helpful , they advised to rebuild but finally i solved it by the following

copying c:\windows\assembly     

copy whole this folder from another working server and paste in inside c:\windows   on the the server which has the problem

this will solve

Answer 60

I ran into this issue the other day, spent around 8 hours trying to get it to work. None of the solutions I found online seemed to help, but today I finally managed to solve it.

The issue was a Microsoft Visual C++ 2005 Redistributable package I had installed! If you have a 2005 redistributable try uninstalling that.

Answer 61

I had this issue too when logging in using my domain admin account.

I logged in using the built-in administrator account and was able to open Server Manager with no problem.

I deleted the local profile for my domain admin account and logged back in using my domain admin account, now I can open Server Manager without it crashing.

Hope this helps those who have tried the other solutions.

Randy

Answer 62

this is the only fix that worked

Answer 63

Akira,

Thank you sir your advice above has resolved my problem.. such an easy fix but took me about a week to narrow down it was .Net related until I found your post I had not found a solution.

Keep up the great work.

Answer 64

Copying machine.config from another server worked for me as well. I had this issue on Server 2012 R2 Essentials after installing .NET 4.6.1. I had initially tried copying the config file from another Standard Edition Server, but that did not work. I copied from another Essentials Edition server and had also installed .NET 4.6.2 but I don't think this .NET update really made a difference. I had seen in another thread that rebooting after copying the file was required