Snap-in failed to initialize

The Snap-in failed to initialize error message can happen in several scenarios. In most cases, it is known to appear when launching the Microsoft Management Console.

The Snap-in failed to initialize error message can also come up when starting the Enterprise Manager and in Internet Information Services (IIS).

The Snap-in failed to initialize message happens when there is a problem with security policies, for example the Local Security Policy, Domain Security Policy, or the Group Policy, or when there is a problem with abandoned registry entry.

The Snap-in failed to initialize error message related to MS Management Console

When the Snap-in failed to initialize message relates to the Microsoft Management Console, it is caused by the system not having access to the System32\WBEM folder.

This can be solved by adding the following parameter to the system environment PATH variable:

%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\system32\WBEM

Go to the My Computer -> Properties -> Advanced -> System Variables and edit the PATH variable.

Snap-in failed to initialize in case of orphaned registry entry

The Snap-in failed to initialize message can also happen when there is an orphaned registry entry because of a program that is associated with the Microsoft Management Console (MMC) snap-in is removed.

In Microsoft Windows 2000 Server, this can be fixed via the following steps:

Ignore the message and start the Microsoft Management Console (MMC)

Click Console

Click Add/Remove snap-in

Click Orphaned snap-in (the one that usually does not have an icon)

Click Remove

Save the changes

In case this still does not help, then ...

Snap-in failed to initialize in case of a problem with DLL registration

The Snap-in failed to initialize message can also happen when there is a problem with DLL registration. If nothing works, make sure the following files exist in your system folder (most likely C:\Windows\system32), and try the following:

Go to the Start menu, click Run, type CMD, hit ENTER and then type and enter the following lines:

• regsvr32 certmgr.dll
• regsvr32 filemgmt.dll
• regsvr32 mycomput.dll

Then type exit and reboot the comuter.

Snap-in failed to initialize related to Internet Information Services (IIS)

You can also get the Snap-in failed to initialize error message when opening Internet Information Services (IIS). In this case, check that it is installed.

Go to the Start menu
   -> Settings
      -> Control Panel
         -> Add/Remove Windows Components 
            -> IIS 
               -> IIS Snap-In

 

The Snap-in failed to initialize error message related to Enterprise Manager

See here: Snap-in failed to initialize (Enterprise Manager) 

Anything else besides the Snap-in failed to initialize? 

Yes, we have many useful guides and tutorials around here. For example, take a look at How to disable Task Manager, or another tutorial called Enable Ctrl+Alt+Delete logon screen. This article is closely related to Do not display last user name. Our article about LinkSys Default Password and the Windows Media Player cannot play DVD message might be handy and help you in hard times as well.

When working in Windows, you might encounter one of the following system messages:

System error 67 has occurred
System error 85 has occured

We encourage you to visit our discussion forum where you can ask any questions you might have and find many more tips.