(follow up to last message) after running mmc then add/create a group policy object from the file menu.
If that dosent work then you gpedit.msc file must be corrupt
Main Topics
Browse All TopicsI'm using Windows XP Prof. SP2. I've used the Group Policy Editor before.
Now it doesn't run anymore.
Whenever I try to open the Policy Editor, I get the error message:
Snap-In couldn't be initialized.
Name: Group Policy
CLSID: {8FC0B734-A0E1-11D1-A7D3-0
Then I see the MMC (MS management console) with another error message in the main window: Snap-In-Creation failed. CLSID etc, "maybe the snap-in wasn't installed correctly".
The same happens when I try to run gpedit.msc directly, or try to import this snap-in into MMC.
I tried to install the Adminpak.msi for Windows 2003, it worked, but it didn't change anything.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Tried replacing it, it is NOT corrupt. Windows System Restore replaces it automatically anyway, I checked the file sizes: All identical.
Running MMC from the command prompt or from anywhere else doesn't help as I stated in my initial question. When I try to import snap-ins, the msc file for gpedit hast a different icon, and cannot be importet.
Also the gpedit.dll cannot be registered using regsvr32. I replaced that as well...
Yeah, have done that before, it exists a couple of times. You want me to post all of them? Ok, here we go:
HKEY_CLASSES_ROOT\CLSID\{8
(Standard): %SystemRoot%\System32\GPEd
ThreadingModel: Apartment
HKEY_LOCAL_MACHINE\SOFTWAR
[Contents same as above]
HKEY_LOCAL_MACHINE\SOFTWAR
(Standard): Not set
About: {0FDE5092-AA2A-11D1-A7D4-0
NameString: Gruppenrichtlinie [<-- German for Group Policy]
NameStringIndirect: @gpedit.dll,-1
[Subkey]: NodeTypes
[Subkeys of NodeTypes]:
{8FC0B736-A0E1-11D1-A7D3-0
{8FC0B737-A0E1-11D1-A7D3-0
{8FC0B738-A0E1-11D1-A7D3-0
{8FC0B739-A0E1-11D1-A7D3-0
{8FC0B73A-A0E1-11D1-A7D3-0
{8FC0B73B-A0E1-11D1-A7D3-0
{8FC0B73C-A0E1-11D1-A7D3-0
gpedit.dll seems to be the problem here (as it's registrable, but you're unable to register it). In my XP SP2 system, here is teh GPEdit.dll file version:
FileDescription: GPEdit
FileVersion: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
OriginalFilename: gpedit.dll
ProductVersion: 5.1.2600.2180
Size : 554KB
See if extracting a copy from DLLCache folder (or ServicePackFiles\i386\ folder) helps.
Other possibilities:
JSI Tip 7261. When you open a security policy related MMC snap-in, you receive 'Snap-in failed to initialize'?:
http://www.jsiinc.com/SUBO
"Snap-in Failed to Initialize" Error Message When You Open Microsoft Management Console:
http://support.microsoft.c
Business Accounts
Answer for Membership
by: bjctennistecPosted on 2005-02-12 at 18:13:27ID: 13296142
try and find a working gpedit.msc file and replace the one in the system32 folder
also try running mmc from the run program in the start menu