Gpedit Installer: Add Group Policy Editor Gpedit.msc to Windows 7 Home and Starter

Juan

Did not work in Home Premium, at least it didn’t worked in mine.

Max

I tried it on two different Windows 7 Home Premium and it would not work, I ran it as Administrator, I tried rebooting, I could not get it to work, thanks anyway
You have a gread website and provide much needed information. thanks..

Rockit

I cannot get it to run on my system either? Is there a service or Win 7 premium feature (in programs and features) that needs to be turned on?

I get a window that says “MMC could not create the snap-in”

Thank You ..

I have been trying to install this for quite sometime now or find a replacement program.

http://www.thewindowsclub.com/about Windows Club

Since the tool doesn’t seem to be working as required, I will have it re-checked.

I suggest you uninstall it and then do a system restore.

Thank you for the feedback.

ErnieK

I cannot try this out as I have Professional on both Pc’s, but have you tried installing whilst in SAFE MODE. It might not install because all system files are up and in use, where as in safe mode only the essentials are installed. Might work and worth a try.
ErnieK

davehc

Andy and I corresponded on this project by Email. It had been successfully employed by members on other forums, and I could not understand the negative feedback here. After investigation, I realised this was, perhaps, for 32Bit only. perhaps a member could confirm it works for 32 Bit?

However, I installed Home premium 64Bit and played with the program. The answer ( at least for me, and I really hope for all) was simple. The installer is unable to locate where to put the GpEdit.msc file.

OK. Try this.

I have zipped Gpedit.msc (64Bit) here: (http://www.filefactory.com/file/cc190fe/n/gpedit.rar ).

Download, Unzip and move it to Windows – System32. Now, try, in the RUN box Gpedit.msc. ”

Investigated totally now. Installed the 32Bit Home.My last info works for both 32Bit and 64Bit. members MUST run the installer, but it cannot find the path so then they manually transfer the GPedit.msc to System32. The installer sets up the .dlls and other items.

Apprehension (LOL) This was premium! Hopefully the basic, but that really is basic!!!!!!

Edit by Admin: You can also download it from here: http://www.thewindowsclub.com/downloads/gpedit1.zip

http://www.thewindowsclub.com Lee Whittington (Lee@TWC

It does run on both x86 and x64 as I have 2 machines running Windows 7 Home Premium and works on both. One thing to note, since the workaround uses an older file for gpedit to get it working, all the settings are not available. Just a matter of playing around till you find the ones that do.

Azeddine

Many thanks Dahvec (and The Windows Club!). I have Windows Home Edit. 64-Bits. I ‘ve just unzipped and run the Gpedit. It installed perfectly at first try…

Rockit

So will there be a updated version that will install on Win 7 premium (32 bit) by itself or do I have to try and sort out which files are new and which are the older ones.

Thank You For Your Effort !!
Rockit

http://www.thewindowsclub.com Lee Whittington (Lee@TWC

Rockit: As of right now this is the only workaround to get gpedit working in Windows 7.

Justin

Is it compatible with other languages versions of Windows? And if so, is it displayed in that language?

Fletch

Is there another location where we can download the .RAR file? My browser thought there was something wrong with that host site. (filefactory)

Thanks…

http://www.thewindowsclub.com/about Windows Club

Fletch: Download it from here: http://www.thewindowsclub.com/downloads/gpedit1.zip

bhavya

I Still cant get it to work..
i installed da prog using the first link–> ‘setup.exe’
den i dwnlded da gpedit.msc and copies it in c:/windows/system32

Now i can find it and run it dem run box in start menu.
But, it still gives da same error… ‘MMC could not create the snap-in’

Can some1 pl help!!!

The reason i want this is coz i cant start runnin da guest account…it has authentication errors…thought i could fix it with this…but it dosent seem to work either!!!

Fletch

Thank you. Working perfect on my 7 Home premium. Thanks again!

Tweakfiend

Just remember …….
If you have installed the “exe” file …. uninstall and remove it and then copy the gpedit.msc file ( not exe ) to System 32 folder
Double click it to run “Gpedit”

Tweakfiend

“create shortcut” against .msc file in System 32 folder and you can run from desktop or start menu without using “run” option

Daniel C. Arendt

This is to report re testing the Windows Club group editor command program for Windows 7 Home Premium edition.

Tested on five month old 64-bit Acer Aspire 5736Z-4148 laptop (4GB RAM installed, Pentium T4500 processor, Mobile Intel(R) 4 Series Express Chipset Family, dual core, and OS Build 7601 Version 6.0…unit has slots for only 2 disks, one of which is “C” with other partitioned by OEM into clean OS uninstaller and clean Home Premium OS installer, both partitioned functions protected); Windows Experience rating constant at 3.4 due to graphics processing not being processor’s strong suit in re, e.g, complex video games/3D motion, and MS diagnostic tool says can’t download Virtual PC or XP Mode ; otherwise Windows Experience ratings are near 6 or 7; due to adding several manually created command box and commercially created log text/thumbnail deleting-type memory/registry utilities, performance is constantly stable with an average free space/virtual/or paging memory of 422 GB (of which about 185 GB can be utilized before noticeable slowing occurs…docs/pics/vids/audio thus always saved to external media). No memory test or CHKDSK or troubleshooter/any known problems; anti-malware is constantly updated VIPRE with scans showing no issues. When added, the group editor utility and all other programs left 3GB installed RAM still available.

While it can be an adventure to get many popular Vista through 7 even simple programs to be ruled “compatible” by the OEM-installed Home Premium 7 edition, I’ve noticed such problems arise chiefly after SP1 or its preceding updates are added.

For example, with just the non-updated original OS boot, the free utility “Eraser” will work, but after a series of updates or SP1, whereas “Eraser” loads and opens it can no longer execute GUI commands; not even Compatibility troubleshooter can then make it run. Event logs tell THAT such failures occur but not WHY. Likewise, ‘WinFX’ video editor (a command box-based conversion utility) converts both audio and video at first but after several OS updates or SP1 it will only convert audio.
The subject laptop does appear able…even in SP1 status…to execute batch commands; I made a plain text doc command to clear all relevant Event Viewer logs, even the MS-created Custom administrative ordinarily not optioned to be cleared, then renamed it with a “.bat” extension and dragged it to desktop; it runs completely and without issues every time it’s clicked. Also, even in SP1 status, the subject laptop easily accommodates the more complex MAGIX Video Pro 3; it appears that at least in SP1 status and even with low-level hardware, the Home Premium 7 can handle involved programs doing one thing at a time. Even a number of Ultimate Windows Tweaker functions work.

Which is why I have no idea why the Windows Club group editor command isn’t working; it loads as a command box which runs with commands then closes, it then appears in Control Panel as an installed program but doesn’t appear in the Start menu/Start search/MMC, doesn’t form/drag as an icon, and no permutated or exact following of Windows Club instructions can get the group editor to do more than sit on the system disk. Obviously renaming from “.msc” would be pointless in present configuration; perhaps some “.txt-to-.bat” listing group editor commands tailored to a user might work?

I suspect some feature of SP1, likely a security update(s), is making even some reliable programs be treated as “programs used by others to gain control of your computer”.

http://www.thewindowsclub.com/about Windows Club

Daniel: Thanks for testing it out and the detailed comment.

Lee@twc

To everyone still having issues with x64:
Try moving the gpedit.dll over with the gpedit.msc and see if it remedies the Snapin error.

Daniel: Have you tried without your security software loaded? I am more inclined to think your issue may be more than just having SP1 installed and it blocking anything as I have SP1 installed on both of my computers and haven’t had an issue with this.

Rockit

Is there a service or Win 7 premium feature (in programs and features) that needs to be turned on? I am running Win 7 32 bit with all of windows updates and Black Vipers Safe Services. I have the games and tablet feature turned off.

I get a window that says “MMC could not create the snap-in” after trying everything posted so far. If I can be of any assistace with troubleshooting this I would be more than happy to assist in anyway I can

Thank You ..

I have been still trying to install this for quite sometime now or find a replacement program.

Daniel C. Arendt

Update: Windows Club Gpedit DID Appear On My Acer!

Yesterday I said on my 64-bit Acer Aspire notebook with Windows 7 Home Premium, the Windows Club group editor download just sat on the disk visible only through Control Panel (and as such it could do nothing).

Today I ran my weekly custom deep (and very slow) VIPRE security scan of the entire computer; I paused the scan when it mentioned a ‘gpedit.msc’ now existing in SysWOW64.

Drilling to the SysWOW 64 file, I found that the Windows Club group editor DID there get installed with Properties showing create date of the day and time I ran WC download; from there, it opens and looks/acts like such editor should; it can even be moved to “desktop”!

So in my case, the Windows Club gpedit download when run ran a command box, the box then disappeared, the installer sat as a few MB on the disk, and the group editor wound up in SysWOW64.

I hope this is helpful to others.

alan watt

Hi
Very interested in GPEdit, but not working for me either in win7 Home Premium. I believe the issue is that the installer is not working correctly for me – my user name in win 7 is “alan watt” but the space seems to cause a problem as the installer is showing invalid parameter “alan”. Be pleased to know if this is the problem. rgds

SA Jack

Glad to see that GPEdit can be installed on Win 7 configurations that were not initially provided this tool. I do have a question with respect to running sfc /scannow. My question is will sfc cause any problems with GREdit? A few years ago, I was able to install GPEdit on my Win XP Home edition. It worked fine. However, if memory serves me right, I think that running sfc either disabled or removed GPEdit; possibly because it saw the program as NOT being part of XP Home. Has anyone run sfc on a Win 7 Home Basic/Home Premium unit where GPEdit has been installed? And if so; did GPEdit survive the scrutiny of MS. -SA Jack

James_39

This worked great for me on Win 7 Home Premium / SP1. I had to manually create a shortcut to the executable to my desktop:

C:\Windows\SysWOW64\gpedit.msc

Anthony

It works well on my Windows 7 Home Premium Edition 64 Bit

It just missed some parts to be done though.
As I watched the installation goes, I notice that the file was copied into
\Windows\SysWOW64

so when at first I tried to run the gpedit.msc, it says that there were no such file. But then just do this :

Add to your Environment Variables
Open through :
1. Right Click Computer, click on properties
2. Click on Environment Variables…
3. Search “Path” from the System Variables box,
4. add the following text (without quotes) :
“;C:\WINDOWS\SysWOW64″
5. close all the open windows
6. try to run gpedit.msc from the run box

I hope this will help you guys

Fox_on_ca

I have win home premium 32 bit and I am getting the “MMC could not create the snap in” error. I downloaded the zip file from The Windows Club. Extracted all to System32 and physically moved the msc file to System32. Ideas?

Anonymous

How to avoid the “MMC could not create the snap in” error.

davehc: There’s a rather common bug in the installer above. It will not work properly if your username contains spaces. Anytime %username% is included in the batch files, it should be “%username%”.

Regular users: Until this is fixed, You need to update the directions. If your username contains spaces, then create a new user with administrator access named, for example, gpedit; then log in as that user to run the installer.

Anonymous

dave, Here’s hoping you have this set to email you.

I’ve got some information on what’s going wrong with your gpedit installer. See my other post on the page. There’s a mistake in the .bat file.

Benefreire

did not works on x64 systems