JSI Tip 7261. When you open a security policy related MMC snap-in, you receive 'Snap-in failed to initialize'?

When you open a security policy related snap-in, like Local Security Policy, Group Policy, or Domain Security Policy, the snap-in does NOT open, and you receive a message similar to one of the following:

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


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


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


Snap-in failed to initialize.
Name: <unknown>
CLSID:\{8FC0B734-A0E1-11D1-A7D3-0000F87571E3\}
This behavior is symptomatic of NOT have the %SystemRoot%\System32\WBEM folder in your PATH environment variable.

To resolve the problem

1. Right-click My Computer and press Properties.

2. Select the Advanced tab.

3. Press the Environment Variables button.

4. Double-click PATH in the System variables area.

5. Modify the string so that it includes %SystemRoot%\system32\WBEM after the %SystemRoot%\system32;%SystemRoot%; string. If additional folders are present, a ; should separate %SystemRoot%\system32\WBEM from the folder that follows it.

6. Press OK and OK.

NOTE: See tip 8498 » When you open a security policy related MMC snap-in, you receive 'Snap-in failed to initialize'?



Hide comments

Comments

  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Publish