Thanks but I had already tried this but did so again and got the same result MMC opens ok but when I try to load the GP snapin I get the message "MMC cannot initialize the snapin- Name Group Policy Object Editor
What about any other snap-ins? Trying to figure out if it's a problem with MMC itself or just GPOE. Is this a new problem? You could try installing the full Group Policy Management Console
Group Policy Editor is not something i am engaged with very often so hard to say how old the problem is. I have read that .Net Framework v3.0 can cause this problem. thanks for all the attenton and help and if all else fails i will download the 'fix' you mentioned or i might try un-installing and re-installing .Net Framework.
On rare occasions, some snap-ins may not work correctly with MMC 3.0. To ensure that these MMC-based tools work correctly with MMC 3.0, you must install updates. For more information about available updates, see the MMC Download Site at the Microsoft Web site.
"
Yes, I log on as 'Administrator'. The problem is still with me and i have spent hours trying to get an answer. The Microsoft KB is just hopeless and never comes up with the right search results. Someone at Microsoft must know the solution to this problem. I have un-installed .NetFramework 3.5 SP1 but this made no difference. The bottom line is that Group policy Editor is no longer installed on my computer.
Have finally managed to get GPedit running from the command prompt. Here is what I did.
1.) Make sure that the file 'framedyn.dll' is present in the Windows\System32\Web folder. I actually replaced it with a fresh copy from the 'DilCache' folder, then carry out the instructions from this Microsoft KB article.
"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."
This certainly worked for me. Good luck to anyone who has the same problem and thanks once again for the 'support'.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.