Cannot run GPEDIT.msc snap in 3

[PaulBarron]

I am trying to look at my local computer policy. When i try to run GPEDIT.msc I get a problem though.

It comes up with;

Snap-In creation failed

The snap-in was not created, it may not be installed properly

Name:Group Policy
CLSID:{8F30B734-A0E1-11D1-A7D3-0000F87571E3}

Can anyone tell me how to get around this. Surprisely enough I couldn't find anything about this on microsoft.com

Thanks

 

[wolluf]

Are you running Pro or Home? (its not available for Home, but if I run the gpedit.msc from Pro in Home, I get Snap-in Failed to Initialize, Name unknown, same CLSID as you, then Snap-in creation failed). Don't know if this sheds any light - would suspect a registry problem if you're running pro.

 

[mb34124]

Have you been able to get anywhere with this problem? I have searched google and have found other people with the same problem.

 

[linney]

See if these offer any clues


297064 - Error Message "Snap-in Failed to Initialize" When You Use Microsoft Management Console

http://support.microsoft.com/default.aspx?scid=kb;en-us;297064&FR=1&PA=1&SD=HSCH

305831 - "MMC Snap-In Failed to Initialize Disk Management Extension" Error Message Starting Disk Management

http://support.microsoft.com/default.aspx?scid=kb;en-us;305831&FR=1&PA=1&SD=HSCH

 

[mb34124]

linney,
Your solution didn't fix my problem, but got me going in the right direction! I tried opening the secpol.msc from the MMC and got a dll error. Now I know which dll is causing the problem. It said it can't find framedyn.dll.
I tried registering framedyn.dll with this line...
regsvr32 c:\WINDOWS\system32\wbem\framedyn.dll

...but got the following error.
c:\WINDOWS\system32\wbem\framedyn.dll was loaded, but the DllREgisterServer entry point was not found.
This file can not be registered.

Thanks for your help! Got any other ideas?

 

[linney]

Microsoft Knowledge Base Article - Q319114
"Application Has Failed to Start Because Framedyn.dll Was Not Found" Error Message When You Open the System Properties Dialog Box"

http://support.microsoft.com/default.aspx?scid=KB;EN-US;q319114

 

[vdubincali]

PaulBarron, I ran into a similar problem after uninstalling a program that removed necessary pathing in the environment variable section of the system. Try this: Go to the control panels/system/advanced/environment variables and ensure that the following is at least there... %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem...the wbem is probably the one that is missing. add it and your problem should go away, please let me know if this helps! -vdubincali

 

[HGaudini]

Thanks, That path statement did the trick. I forgot to even check that, until you brought it up.

Many Thanks...