Team OS : Your Only Destination To Custom OS !!

Welcome to TeamOS Community, Register or Login to the Community to Download Torrents, Get Access to Shoutbox, Post Replies, Use Search Engine and many more features. Register Today!

Tips & Tricks How To Enable Group Policy Editor (gpedit.msc) In Windows 10 Home Edition

juanamm

Uploader
Uploader
Power User
✅ Verified Member
Member
Downloaded
5.7 GB
Uploaded
448.6 GB
Ratio
78.11
Seedbonus
134,973
Upload Count
217 (223)
Member for 5 years
How To Enable Group Policy Editor (gpedit.msc) In Windows 10 Home Edition

GPEdit.msc or Group Policy Editor is a configuration manager for Windows which makes it easier to configure Windows settings. Instead of going through Windows Registry, the user can configure different aspects of the Windows Operating System through a group policy editor.

One of the very main differences between Windows 10 Pro edition and Windows 10 Home edition is the networking management capabilities. The other differences include the exclusion of Remote Desktop and Group Policy Editor for Windows 10 Home Edition. In fact, the Group Policy Editor is not available in any Home or Starter edition of Windows, be it Windows XP, Windows 7, Windows 8.1 or Windows 10.

STgRr.png


This is a serious drawback as we need the group policies even for managing settings of the local computer. The group policy is better than changing the settings through Windows Registry which is much riskier. Most of the group policy settings can be reverted easily while Registry editing can have adverse effects on the system.

In this article, we will guide you to install the Group Policy Editor for Windows 10 Home edition. This method can be used in Windows 7 and Windows 8 too.

Method #1: Enable Group Policy Editor using GPEdit Installer

Since the Group Policy Editor is not included in Windows 10 by default, we will need to download the editor first. You may download it from the below-mentioned download link.
Download gpedit_msc.rar:

This is a simple setup file which when run will install and configure the Group Policy Editor in your Windows Home system.

Installing gpedit.msc correctly

If you have 32-bit Windows (x86) then the setup should install smoothly without any problems and you should be able to access the Group Policy Editor through the Microsoft Management Console by going to Run –> gpedit.msc. But if you have 64-bit Windows (x64) then you will need some extra steps after running the installer. Follow the steps below after running the installer:
1. Go to C:\Windows\SysWOW64 folder
2. Copy the following folders and files from C:\Windows\SysWOW64 to C:\Windows\System32
“GroupPolicy“, “GroupPolicyUsers” and gpedit.msc.
This will make sure that you can run the editor from the Run dialog.

Solving common problems running gpedit.msc

In case you are getting “MMC could not create the snap-in” error message while starting gpedit.msc, you may follow the steps below for the solution:

1. Go to C:\Windows\Temp\gpedit\ folder and make sure it exists.
2. Download the following zip file and unzip it to C:\Windows\Temp\gpedit\. This should replace two files x86.bat and x64.bat.
Download x86x64.rar:
Now run x86.bat if you are running 32-bit Operating System and x64.bat if you are running 64-bit Windows 10. Make sure you are running the batch files as Administrator.

After following the above-mentioned steps, you should have a working Group Policy Editor in Windows 10 Home edition. In case of any confusion or problem, you are always encouraged to discuss by commenting below.

Method #2: Enable GPEdit.msc using PowerShell script

If the above method doesn’t work, then you should try this method as it is much simpler and easier to implement. Follow the steps below to enable group policy editor in Windows 10 Home:

1. Download GPEdit Enabler script from below link:
Download gpedit_enabler.rar:
This is a simple PowerShell script which will install the disabled Group Policy features in Windows 10 Home edition.
2. Right-click the downloaded gpedit-enabler.bat file and select Run as Administrator.
3. This will start the installation process. It may take some time depending upon your system performance. When the process is finished, press any key to close the command prompt window.
4. Now to go Run –> gpedit.msc. This should open group policy editor on your Home edition of Windows.
5. Although a restart is not required, if the policies are not working, you should restart the computer once.

Some people complain that although this method enabled the group policy editor, most of the settings don’t work in Home edition. If both the methods fail in your case, you should probably try out the third method discussed below.

Method #3: Using Policy Plus

Policy Plus is a third-party app and an alternative to the built-in Group Policy editor. Its interface is very similar to GPEdit. One major benefit of using Policy Plus is that it comes with a search function where you can search for your required policies.

1. Download Policy Plus from the below-given link:
Download Policy_Plus.rar:
2. Run Policy-Plus.exe. It is a portable app so it will open immediately. You can make changes to the policies exactly how you do it in Windows built-in group policy editor.

SToxj.png


Hopefully, these methods will help you enable gpedit.msc on your system. Your experience and comments are highly appreciated.​
 
Last edited:

pintudada

Member
Downloaded
7 GB
Uploaded
4.9 GB
Ratio
0.71
Seedbonus
2
Upload Count
0 (0)
Member for 7 years
policy plus file is missing in the given mirror
 

Reehal

Member
Banned
Downloaded
21.7 GB
Uploaded
37.1 GB
Ratio
1.71
Seedbonus
5,068
Upload Count
0 (0)
Member for 6 years
@echo off

pushd "%~dp0"

dir /b %SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~3*.mum >List.txt

dir /b %SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~3*.mum >>List.txt

for /f %%i in ('findstr /i . List.txt 2^>nul') do dism /online /norestart /add-package:"%SystemRoot%\servicing\Packages\%%i"

pause





Copy notepad and save.bat then open run as administrator and enjoy
 

pintudada

Member
Downloaded
7 GB
Uploaded
4.9 GB
Ratio
0.71
Seedbonus
2
Upload Count
0 (0)
Member for 7 years
tried each and every step but still not working
 

brahmajivv

Power User
✅ Verified Member
Member
Downloaded
174.8 GB
Uploaded
8.4 TB
Ratio
49.28
Seedbonus
46,840
Upload Count
0 (0)
Member for 7 years

doesnt solve the snap in error, however didnt try Reehal script as i dont want to mess up much on the system files.

*.adm files not available in system32 folder, but all 5 files are already present(might be by exec of x64.bat that dont know) in "%WinDir%\SysWOW64\GroupPolicy\Adm"

Nonetheless above two posts the Method 2 with Powershell script worked like charm..

Many Thanks
 

Reehal

Member
Banned
Downloaded
21.7 GB
Uploaded
37.1 GB
Ratio
1.71
Seedbonus
5,068
Upload Count
0 (0)
Member for 6 years
@echo off
pushd "%~dp0"

dir /b %SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~3*.mum >List.txt
dir /b %SystemRoot%\servicing

\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~3*.mum >>List.txt

for /f %%i in ('findstr /i . List.txt 2^>nul') do dism /online /norestart /add-

package:"%SystemRoot%\servicing\Packages\%%i"

pause
package start for reehal

i already test this file working file after restart your gpedit.msc command are open
 

johnnydu9

Member
Downloaded
3 TB
Uploaded
44 TB
Ratio
14.57
Seedbonus
28,215
Upload Count
0 (0)
Member for 7 years
Method #3: Using Policy Plus

The file you are looking for does not exist!
 
Last edited by a moderator:

juanamm

Uploader
Uploader
Power User
✅ Verified Member
Member
Downloaded
5.7 GB
Uploaded
448.6 GB
Ratio
78.11
Seedbonus
134,973
Upload Count
217 (223)
Member for 5 years
Method #3: Using Policy Plus

The file you are looking for does not exist!

File re uploaded! Works!
Download Policy_Plus.rar:
 
Top