"Snap-in failed to initialize"

"Snap-in failed to initialize" error message when you open Microsoft Management Console

When you try to open a Microsoft Management Console snap-in that involves security policies (such as Local Security Policy, Group Policy, or Domain Security Policy), the console may not open, and you may receive an error message similar to one of the following error messages:

Error message 1

Snap-in failed to initialize.
Name: Group Policy
CLSID: {8FC0B734-A0E1-11D1-A7D3-0000F87571-E3}

Error message 2

Snap-in failed to initialize.
Name: Resultant Set of Policy
CLSID:{6DC3804B-7212-458D-ADB0-9A07E2AE1FA2}

Error message 3

Snap-in failed to initialize.
Name: Software Installation (Computers)
CLSID:{942A8E4F-A261-11D1-A760-00C04FB9603F}

Error message 4

Snap-in failed to initialize.
Name: <unknown>
CLSID:{8FC0B734-A0E1-11D1-A7D3-0000F87571E3}
Cause
This behavior occurs because the PATH environment variable does not include the %SystemRoot%\System32\WBEM folder.
To resolve this behavior, add the %SystemRoot%\System32\WBEM folder to your PATH environment variable. To do so, follow these steps:
  1. Right-click My Computer, and then click Properties.
  2. On the Advanced tab, click Environment Variables.
  3. Under System Variables double-click the PATH environment variable .
  4. Type:
    %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\system32\WBEM
    Note If other system variables appear, do not remove them.
  5. Click OK, and then click OK.

Source

Posted in , ,


0 Response to ""Snap-in failed to initialize""

Post a Comment

Subscribe to: Post Comments (Atom)