What are your Thoughts?

*

312 Comments

  1. Ernesto
    November 7, 2018 @ 9:39 PM

    Thanks! It works for me!

    Reply

  2. Roke Beedell
    July 22, 2018 @ 4:10 PM

    Thank you for the Group Policy Editor, but it would be nice if you didn’t bundle it with PUPs like ‘WebToolbar.Win32.RK!O’.

    Reply

    • iTechtics Staff
      July 23, 2018 @ 12:47 PM

      We don’t bundle any products. The installer comes straight from the author itself.

      Reply

  3. diane
    May 31, 2018 @ 6:28 AM

    Hi I tried to download the installed but didn’t work. and it seems C:WindowsTempgpedit folder didn’t exist.

    Thank you

    Reply

  4. aaaa
    March 17, 2018 @ 7:28 PM

    how to add profile picture

    Reply

  5. Ashutosh Sharma
    February 28, 2018 @ 5:14 PM

    Hello, thanks for the group policy. I had an issue with my windows defender. I turned off my virus protection in defender and ran a codec pack at administration level. Now, My defender is not working at all. Its say” Threat service has stopped”.
    and also, when I go to setting of WD(windows defender), the button to on/off virus protection is slight black marked( like I cannot press the button at all).
    I don’t know what happened. From task scheduler, the windows scheduler scan is also vanished. That’s how I ended up at group policy. But I didn’t work either. Please let me know how to fix this. I can send all the screen shots you need to figure the situation out. All you can mail me. I do not want to reset my laptop. I did call to microsoft customer care, but the level 2 people can’t be able to solve it.
    I am waiting for your response.

    Reply

    • Jeremy
      June 19, 2018 @ 8:13 PM

      Did all the stuff for 64 bit and now error box says I don’t have permission

      Reply

  6. Roger
    February 16, 2018 @ 12:35 PM

    Well, tried this and the result is:
    Windows-R: `gpedit.msc` starts the GPEdtitor; BUT, when creating a,e.g., shutdown script, error occurs telling path not available: c:\windows\System32\grouppolicy\scripts\shutdown` Entering this path manually did not work.
    Any more hints on this issue?

    Reply

  7. Bass
    February 8, 2018 @ 6:30 PM

    It worked

    Reply

  8. Bob
    January 15, 2018 @ 9:06 PM

    It is completely unacceptable that this is just not included, I’m so close to just dumping MS and going with Linux

    Reply

    • Phab
      February 9, 2018 @ 10:55 PM

      Enable file and name extensions

      Reply

  9. Kong
    January 15, 2018 @ 5:46 AM

    help i cant find GPEDIT.MSC in sysWOW64 where do i find it? i found gpedit.dll but its a file from years before

    Reply

  10. Kevin
    January 10, 2018 @ 4:50 PM

    Ran the installer and copied the files from “SysWOW64” to “System32” (64-bit)
    Worked flawlessly. Thank you 🙂

    Reply

  11. Raju
    January 1, 2018 @ 3:28 AM

    Thanks so much

    Reply

  12. Shaun
    December 23, 2017 @ 7:10 AM

    Worked perfectly for me. Thanks so much

    Reply

  13. James
    December 8, 2017 @ 5:30 PM

    This works perfectly – I used the gpedit installer, copied the file and folders… Guys – UAC may get in the way of this, which I have disabled. Also, I’m running latest version of windows 10, creators update.

    Reply

  14. Juan José Vizconde
    November 19, 2017 @ 1:17 AM

    Great post, thank you!!

    You can also use PolicyPlus (freeware) to enable the Group Policy Editor for Windows Home Editions.

    Reply

  15. Dodo
    November 13, 2017 @ 5:03 AM

    I followed all of the steps above, including the steps for when it says MCC Couldn’t create the snap in. It did not fix the issue. I will try the other way to enable gpedit. Thanks.

    Reply

    • zero
      November 14, 2017 @ 7:40 PM

      yep. me too.

      Reply

  16. KBell
    November 11, 2017 @ 11:05 PM

    I don’t have gpedit.msc in the sysWOW64 folder, but there is gpedit.dll. Should I copy the dll as is you rename it msc?

    Reply

  17. Tim
    November 8, 2017 @ 4:35 AM

    Thanks it all works. However, when I try add a new policy in the policy definitions, it doesn’t appear in the group policy editor. Any suggestions thanks…

    Reply

  18. Vonni
    October 27, 2017 @ 6:59 AM

    This website barely works itself so wat makes u think the download is gonna work

    Reply

    • iTechtics Staff
      October 27, 2017 @ 11:24 AM

      Hi Vonni, can you tell me what issue are you facing with the website? And I have tried to solution myself, it works.

      Reply

  19. John
    October 11, 2017 @ 5:28 AM

    Followed install
    Received: An attempt was made to reference a token that does not exist” error.
    Then Tried to Open a Command Prompt (CMD) in ELEVATED MODE (run as administrator) and navigate to %WINDIR%\System32 and re-register the required DLL files using the following command:
    For /F %s in (‘dir /b *.dll’) do regsvr32 /s %s
    Still no go!!! Please help.

    Reply

  20. Mike Hellinger
    October 4, 2017 @ 6:18 PM

    Great post!

    To add:

    If you have Windows 10, you can also add gpedit.msc using a batch file with dism command.

    If you have Windows 8.1 or Windows 7, you can also try Policy Plus (freeware).

    Policy Plus also runs under Starter and Home editions.

    Reply

    • Kramned
      March 21, 2018 @ 1:11 PM

      Yes! it worked. Runt the installer again in the first method.. and voila. GPEDIT showed up with no MMC error. Thank you…

      Reply

  21. enzure
    October 3, 2017 @ 7:37 PM

    EUREKA, I try all the steeps, and still not working, then i run the installer from the first step once again and it works

    Reply

    • Reza
      October 11, 2017 @ 12:30 PM

      I do too, and it works
      thank you

      Reply

  22. gio
    August 22, 2017 @ 12:30 PM

    still error could not create snap in

    Reply

  23. gio
    August 22, 2017 @ 2:16 AM

    followed all yr steps but still got error:
    impossible to create snap in.
    .why..??
    win 10 home 64bit ita vers creators update 1703
    pls reply thxs!

    Reply

  24. Meo
    August 18, 2017 @ 2:29 AM

    All seems ok, but going to Computer config -> administrative models -> system -> file system -> NTFS, I can’t find ‘Enable NTFS long paths’, that is my need.

    Reply

  25. TonyH
    August 17, 2017 @ 8:46 PM

    AVG identifies this as malware!!
    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:

    Go to C:\Windows\SysWOW64 folder
    Copy the following folders and files 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:
    Go to C:\Windows\Temp\gpedit\ folder and make sure it exists.
    Download the following zip file and unzip it to C:\Windows\Temp\gpedit\. This should replace two files x86.bat and x64.bat.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.

    Reply

  26. Willie Jennings
    August 9, 2017 @ 8:04 PM

    It seemed to have worked then this:

    MMC could not create the snap in. The snap-in might not have been installed correctly.

    Name: q

    CLSID: {8fC0B734-A0E1-11D1-A7D3-0000F87571E3}

    Reply

  27. Raiz
    July 26, 2017 @ 11:36 PM

    Thanks! This worked

    Reply

  28. nate
    July 25, 2017 @ 7:20 PM

    ok seriously though. sisnce this doesn’t work how do I remove all this crap you just had me put on my computer . where did it install files to and how do I remove them????

    Reply

  29. Dark
    July 25, 2017 @ 7:12 PM

    ya this doesn’t work. MMC could not create snap in and I followed all your steps and even the ones in comments

    Reply

  30. Dark
    July 25, 2017 @ 7:11 PM

    ya this doesn’t work. mmc could not create snap inand I did what you said to do to fix it

    Reply

  31. hdcphu
    July 25, 2017 @ 10:55 AM

    It works. Thank you 🙂

    Reply

  32. Angle
    July 24, 2017 @ 8:31 AM

    Use this method is nothing more than to reduce the expenses, but the computer is harmful, it is recommended to click on this site search vanskeys, than Microsoft affordable.

    Reply

  33. anngle
    July 24, 2017 @ 6:24 AM

    Thanks for sharing. Guys if these keys don’t work for you and you don’t mind spending a little money, then you can visit vanskeys.com to get heap and genuine keys for windows in all versions.

    Reply

  34. John
    July 18, 2017 @ 9:45 AM

    Your ‘zip;’ download has ‘0’ bytes in it, is this a scam? The alternate download site is also useless.

    Reply

  35. deadpool
    July 14, 2017 @ 5:53 AM

    the virustotal is great.! (as are ESET scans)
    but everyone knows that , the odd ducks there that hit are junk a/v scanners.
    false positives. (
    may a/v , (poor) flag any app that changes the reg. in odd places.
    if you use VT 1000 of times you learn how it works, and what to look for.

    known for its wrong hit rates, endless really.
    https://en.wikipedia.org/wiki/Heuristic_analysis

    its like when the doctor ,finds a LUMP, and goes, you gotta lay off popcorn. hehehehe

    Reply

  36. deadpool
    July 14, 2017 @ 5:43 AM

    it works
    but many fail to see,
    download the zip
    extract the setup.exe
    run the setup.exe , watch it install… bla bla…
    then
    at syswow64 folder,
    copy 3 things there, 2 folders and the one file,(far far below) gpedit.msc
    use the control key to select all three. or it will fail.
    then paste all 3 to
    2 places. below, or it will fail.

    windows/system/
    then again
    windows/system32/

    in the run box, gpedit.msc type this, and when it pops, click it.
    i did not need to reboot.

    if scared of a virus.its not, but always be so…
    go to Virustotal.com and scan it, see its ok…!
    zip to check.
    http://www.deviantart.com/art/Add-GPEDIT-msc-215792914

    my example is for win10-64 home.
    if you have pro this is useless. as it already works.

    Reply

    • Ucok
      July 17, 2017 @ 6:19 PM

      what folders and files? i only received setup.exe from the download -_-

      Reply

  37. Tloart
    July 11, 2017 @ 9:34 PM

    Please don’t follow this tutorial. It’s a virus

    Reply

    • iTechtics Staff
      July 12, 2017 @ 1:22 AM

      Can you explain why its a virus? We have checked our files with major antivirus software and they are clean.

      Reply

  38. Jhune
    July 10, 2017 @ 7:51 AM

    Still can’t open windows defender because when i open policy editor i can”t find window 10 it’s “at least windows vista” only in the least.

    Reply

  39. paulo
    June 23, 2017 @ 4:10 PM

    Hi,
    I enabled Group policy and put only notepad.exe, and now, i cant open gpedit.msc again.

    Do you know how to fix this?

    Reply

  40. Jason
    June 12, 2017 @ 8:41 AM

    Thank you, this was quite simple and worked on windows 10 64-bit. I changed settings and now I will wait to see if it works.

    Reply

  41. Rajneesh
    May 31, 2017 @ 9:51 PM

    There were no problems at all in my windows 10 home x64-bit. I only installed setup in archive and just all was done!!!

    Reply

  42. josh
    May 30, 2017 @ 3:50 AM

    i followed all the steps and i did what it said to do in the common problames but at the end of the cmd it said file not found i did run as admin and the file exists sooo i need help sorry if i am a noob XD .

    Reply

  43. Renata
    May 25, 2017 @ 11:40 PM

    I didn’t get it, still not showing the gpedit.msc.

    Reply

  44. Giz
    May 20, 2017 @ 9:30 PM

    any suggestions? I did everything according to the instructions. I did not experience any problems, everything went as it should be. When I run gpedit.msc i see the changes, they are permanent, doesne disappear… and the line – update windows marked as “notify for download …” but unfortunately nothing has changed in the way windows updates … continue to update automatically with no option …

    Reply

  45. Casey
    May 17, 2017 @ 12:25 PM

    do you have a way to donate?

    Reply

  46. Sandy
    May 12, 2017 @ 10:08 PM

    Perfect! Installed on W10 and experienced no “common problems”. Thank you kindly!

    Reply

  47. Mr. NomNom
    May 10, 2017 @ 4:57 AM

    Omg, Thanks to Mr. Mickster676. I followed all the steps and… It’s Work! [Insert Mr. Robot hackerman meme here]

    Reply

  48. Joon Moon
    May 2, 2017 @ 12:07 PM

    Still not working even though after replacing .bat files.

    Reply

  49. Joon Moon
    May 2, 2017 @ 11:40 AM

    Hi there! I have a problem regarding the files “GroupPolicy” and “GroupPolicyUsers”, I opened C:\Windows\SysWOW64 after installation and found neither of the two. I’ve only found “gpedit.msc” file. Why is that? Will it still works?

    Reply

  50. alice
    April 30, 2017 @ 3:52 AM

    Install of GPEDT – Perfect
    Run as Admin through Command prompt:
    Computer Configuration -> Administrative Templates -> Windows Components -> Data Collection and Preview Builds
    —>Data Collection is not one of the options available to me

    Am I missing something?

    Reply

  51. Mickster676
    April 29, 2017 @ 2:11 AM

    first try this;
    John Valdez
    MARCH 30, 2017 @ 10:43 PM
    Search “cmd" and run as admin.
    Type: cd/ then enter
    Type: cd windows then enter
    Type: cd temp then enter
    Type: cd gpedit then enter
    Type: x64.bat then enter

    If you some parts fail ( dont install do this)… this one worked for me xD

    D. Admin
    OCTOBER 29, 2016 @ 5:31 AM
    To everyone experiencing errors installing the snap in, the following might be of some importance to you:

    You are more than likely experiencing errors because the program itself lacks the permissions to write to the required folders in ‘C:\Windows’, regardless of your account being an “administrator" account. The permissions for an account categorized as ‘Administrator’ when you create the account only gives access to useful areas of the system, but not the elevated permissions required to perform certain tasks.

    1.) Under ‘C:\Windows’, perform the following:

    Right Click > Properties > Security Tab > Advanced Button

    A window launches that lists the folder permissions. There might actually be two different sets of permissions listed for “Administrator" depending on the subfolder you are in. Your administrator account is limited when it comes to the OS folders.

    To allow the install to successfully copy the files and folders to the proper locations, you must perform the following:

    2.) From an admin account, launch an elevated command prompt. There are several ways to do this:

    a.) Windows Key > Type ‘cmd’ > Right Click ‘cmd’ shortcut > Run As Administrator

    b.) Right Click Start Menu > Click ‘Command Prompt (Admin)’

    If you are successful, a command prompt will launch with the home directory of cmd.exe, which is ‘C:\Windows\system32’

    3.) At the prompt, type ‘net user administrator /active:yes’

    If you are successful the console will print a line telling you so. This will activate the master ‘Administrator’ account that belongs to the system for these such cases. (You cannot run some programs from this account, specifically many of the UWP apps for Windows 10.)

    4.) Log out of your current ‘Administrator’ account.
    5.) When you are returned to the user login screen you should now see a new account titled ‘Administrator’. Click it to login and wait for the environment to be setup by Windows for the first run.

    6.) ****IMPORTANT**** DO NOT Right Click > Run as Administrator for the downloaded files. It will run the programs under the incorrect admin settings that are assigned to a general admin account (the admin account you were using before), thus having no effective permissions.

    Run the above programs to install gpedit.msc and the associated DLLs.
    Run the appropriate BAT for you system architecture from the x86x64 package in ‘C:\Windows\Temp\gpedit’

    7.) Sign out of the ‘Administrator’ account.
    8.) Login to your previous admin account that you were using before.
    9.) Launch an elevated command prompt as an administrator as listed in step 2.
    10.) Type ‘net user administrator /active:no’ to shut off the ‘Administrator’ account. If you forget to do so, it will leave your system vulnerable to attack.

    Reply

  52. Yazan
    April 22, 2017 @ 9:45 PM

    guys you are awesome!! I did not think that I will find such simple quick solution directly !!

    Reply

  53. vickie
    April 20, 2017 @ 5:05 AM

    Thank you SO much! I have been trying to find this for a few months now, and your solution was well explained and works easily.

    Reply

  54. Regla Garcia
    April 15, 2017 @ 3:24 AM

    I upgraded Windows to windows 10 and I also installed Cortana and I’am having a big problem on delete this from my computer if someone could Please HELP me I will really appreciated
    Thank you and have a bless day

    Reply

  55. John Valdez
    March 30, 2017 @ 10:43 PM

    Search “cmd” and run as admin.
    Type: cd/ then enter
    Type: cd windows then enter
    Type: cd temp then enter
    Type: cd gpedit then enter
    Type: x64.bat then enter

    Reply

  56. Juley
    March 28, 2017 @ 6:12 AM

    my Win10 does now sleep and lock, but does not wake. I have to restart.

    Reply

  57. Rob
    March 24, 2017 @ 2:40 PM

    I miss the next branch : Computer Configuration > Administrative Templates > System > Device Installation > Device Installation Restrictions. What to do?

    Reply

  58. Ninja Turtle
    March 23, 2017 @ 10:48 PM

    Followed all steps to the letter, did not work for me.
    I upgraded 8.1 to 10, french , x64 family edition 🙁

    GPedit gives me a 1 liner chineese mumbo characters! and nothing else…

    Reply

  59. BillGates
    March 20, 2017 @ 9:44 PM

    Windows 10 Home x64, getting error?

    “MMC could not create the snap-in”

    You have to run the x64.bat file in an Admin Command Prompt. It will not work if you right-click the bat file and run as Admin. Sounds stupid but that is Windows for ya.

    Reply

  60. abby
    March 10, 2017 @ 8:59 PM

    it really works. You just have to run the batch file using command prompt run as administrator.

    Reply

  61. treecat
    March 10, 2017 @ 1:46 AM

    Thanks Bonzai for reiterating Skar’s solution. After following the steps above, this final solution worked for me.
    As Skar suggested “opening command prompt (cmd) as an administrator and opening the C:\Windows\Temp\gpedit\ folder and running x64.bat (I have 64 bit system). Now, gpedit works fine…."

    Reply

  62. Ed
    March 7, 2017 @ 5:03 PM

    I can not remove Cortana from my system. I hate it. I did not ask for it. Screw you.

    Reply

  63. Cdn_bushwhacker
    March 4, 2017 @ 6:01 AM

    I had the same error message. I hadn’t run the setup.exe as Administrator. Then I got the “MMC could not create the snap-in" in the Group Policy Editor when it did run. Then followed the instructions to replace the “x64.bat” – ran as Administrator as I’m using Win10 x64 Home. Worked!

    Reply

  64. chas hanson
    March 2, 2017 @ 6:22 PM

    Mistah Bonzai has the solution for me look down the list , run the cmd prompt as administrator, navigate to windows/temp/gpedit then type in x64.bat

    Reply

  65. abishek thakur
    March 2, 2017 @ 1:06 PM

    aosme its works
    thanks

    Reply

  66. Asmeer Abubackar
    February 27, 2017 @ 9:21 PM

    I couldn’t able to open gpedit even after the following steps.
    What should i do to get the group policy editor.

    Pls reply me now.

    Reply

  67. Sebby Frick
    February 25, 2017 @ 5:10 AM

    god damn you idiots IT DOSENT WORK AND WHY TF IS HARDER TO WORK ON X64 SYSTEMS, HUH. I WANT AN ANSWER AND I WILL BAN THIS SITE THROUGH GHOSTERY.EVERYONE HAS X64 SYSTEMS

    Reply

  68. Alex
    February 24, 2017 @ 7:06 AM

    Window 10 is horrible product possible only in the market effectively monopolized and corrupted.

    Reply

  69. Ejaz Ahmad
    February 22, 2017 @ 9:59 PM

    After following all the steps still showing MMC could not create the snap-in….Please help me out.

    Reply

  70. Abhishek
    February 18, 2017 @ 8:29 PM

    I couldn’t able to open gpedit even after the following steps.
    What should i do to get the group policy editor.

    Reply

  71. Maria
    February 18, 2017 @ 5:43 PM

    after doing this step “Download the following zip file and unzip it to C:\Windows\Temp\gpedit\. This should replace two files x86.bat and x64.bat." still I m getting “MMC could not create the snap-in"

    Reply

  72. jay-jay
    February 16, 2017 @ 10:08 PM

    after following all instructions. i glanced in the end thread of cmd “cannot find file specified”. i ran gpedit.msc and that’s the end result. so it didn’t work. even the bat files didn’t work. i followed every thing step by step. solutions pls?

    Reply

  73. Jack
    February 15, 2017 @ 7:55 PM

    I have two identical PC systems at home, Windows 10 prof, build 14393, 64 bit.
    one PC works great with the patch! The other does not work with the user names displayed on login screen.
    No error messages using gpedit.msc editor, works OK. Script parameters look like it is not being executed.
    Are there any log files or folders/files/permissions to check?
    Thanks,
    Jack

    Reply

  74. John
    February 14, 2017 @ 6:24 PM

    still showing MMC could not create the snap-in after following the instructions….

    Reply

  75. Mistah Bonzai
    February 12, 2017 @ 8:53 AM

    As Skar suggested “opening command prompt (cmd) as an administrator and opening the C:\Windows\Temp\gpedit\ folder and running x64.bat (I have 64 bit system). Now, gpedit works fine….” Did the trick for me.

    Reply

  76. amita
    February 9, 2017 @ 6:29 PM

    after doing this step “Download the following zip file and unzip it to C:\Windows\Temp\gpedit\. This should replace two files x86.bat and x64.bat.” still I m getting “MMC could not create the snap-in”

    Reply

  77. Alexander
    February 4, 2017 @ 1:46 PM

    When i install this package based on Windows 10 Homme x64bits, and call gpedit.msc and next “Computer Configuration > Administrative Templates > Windows Components > Windows Update>Configure Automatic Updates” on the windows where i give “enable” and “Notify for download and notify for install” i see underneath an inscription “Supported on: Windows server 2003, XP SP1, 2000 SP3” – never written “Windows 10”. Configuration and setting which do not affect the system and Windows continue to Automatic updates. Whether it’s the installation package for gpedit.msc on Windows 10 or you give other links…

    Reply

  78. seb
    January 31, 2017 @ 6:14 PM

    how to uninstall this?

    Reply

  79. Seb
    January 31, 2017 @ 6:13 PM

    How to unintall this?

    Reply

  80. Viridel
    January 27, 2017 @ 5:15 AM

    Using the Admid-CMD system, I show that I have 4 files where “Access Denied” – unfortunately, I can’t review which files are the ones blocked:

    … skipping to where it fails, everything else was Successful
    Successfully processed 6 files; Failed processing 0 files
    1 file(s) copied.
    1 file(s) copied.
    1 file(s) copied.
    1 file(s) copied.
    1 file(s) copied.
    1 file(s) copied.
    Access is denied.
    0 file(s) copied.
    Access is denied.
    0 file(s) copied.
    Access is denied.
    0 file(s) copied.
    1 file(s) copied.
    Access is denied.
    0 file(s) copied.
    1 file(s) copied.
    1 file(s) copied.
    1 file(s) copied.
    1 file(s) copied.
    1 file(s) copied.
    1 file(s) copied.

    C:\Windows\Temp\gpedit>

    Reply

    • Mickster676
      April 29, 2017 @ 2:07 AM

      D. Admin
      OCTOBER 29, 2016 @ 5:31 AM
      To everyone experiencing errors installing the snap in, the following might be of some importance to you:

      You are more than likely experiencing errors because the program itself lacks the permissions to write to the required folders in ‘C:\Windows’, regardless of your account being an “administrator" account. The permissions for an account categorized as ‘Administrator’ when you create the account only gives access to useful areas of the system, but not the elevated permissions required to perform certain tasks.

      1.) Under ‘C:\Windows’, perform the following:

      Right Click > Properties > Security Tab > Advanced Button

      A window launches that lists the folder permissions. There might actually be two different sets of permissions listed for “Administrator" depending on the subfolder you are in. Your administrator account is limited when it comes to the OS folders.

      To allow the install to successfully copy the files and folders to the proper locations, you must perform the following:

      2.) From an admin account, launch an elevated command prompt. There are several ways to do this:

      a.) Windows Key > Type ‘cmd’ > Right Click ‘cmd’ shortcut > Run As Administrator

      b.) Right Click Start Menu > Click ‘Command Prompt (Admin)’

      If you are successful, a command prompt will launch with the home directory of cmd.exe, which is ‘C:\Windows\system32’

      3.) At the prompt, type ‘net user administrator /active:yes’

      If you are successful the console will print a line telling you so. This will activate the master ‘Administrator’ account that belongs to the system for these such cases. (You cannot run some programs from this account, specifically many of the UWP apps for Windows 10.)

      4.) Log out of your current ‘Administrator’ account.
      5.) When you are returned to the user login screen you should now see a new account titled ‘Administrator’. Click it to login and wait for the environment to be setup by Windows for the first run.

      6.) ****IMPORTANT**** DO NOT Right Click > Run as Administrator for the downloaded files. It will run the programs under the incorrect admin settings that are assigned to a general admin account (the admin account you were using before), thus having no effective permissions.

      Run the above programs to install gpedit.msc and the associated DLLs.
      Run the appropriate BAT for you system architecture from the x86x64 package in ‘C:\Windows\Temp\gpedit’

      7.) Sign out of the ‘Administrator’ account.
      8.) Login to your previous admin account that you were using before.
      9.) Launch an elevated command prompt as an administrator as listed in step 2.
      10.) Type ‘net user administrator /active:no’ to shut off the ‘Administrator’ account. If you forget to do so, it will leave your system vulnerable to attack.

      Reply

  81. Vlad
    January 23, 2017 @ 5:00 PM

    I have to do some more moves doing the same way:
    Program appmgr.dll was also missing, and I should to copy it from installed OS to the WOW folder. Then run X64.bat once more. And that was it – succesfull!

    Reply

  82. Vladimirs Žguļovs
    January 23, 2017 @ 5:00 PM

    I have to do some more moves doing the same way:
    Program appmgr.dll was also missing, and I should to copy it from installed OS to the WOW folder. Then run X64.bat once more. And that was it – succesfull!

    Reply

  83. Vladimirs Žguļovs
    January 23, 2017 @ 5:00 PM

    I have to some more moves doing the same way:
    Program appmgr.dll was also missing, and I should to copy it from installed OS to the WOW folder. Then run X64.bat once more. And that was it – succesfull!

    Reply

  84. Daryl
    January 23, 2017 @ 6:12 AM

    I followed instructions step by step but when I run gpedit.msc I get this error msge “An attempt was made to reference a token that doesn’t exist” I run win 10 64bit.

    Reply

  85. Abraham
    January 18, 2017 @ 8:04 AM

    I had followed all what had mentioned in this article, I still have the “MMC could not create the snap-in" error. What’s wrong???

    Reply

  86. Nate g
    January 10, 2017 @ 10:37 AM

    Ok so i believe i had the install go according to plan. I get the snapin to run. Its the outdated looking version. I assume that it is running correctly.

    Now the problem im having is how do i get the windows 10 templates on here. I attempted to get them from microsoft but the tables available were in a different format and was not compatible.

    Is it supposed to be antiquated? Is there a way to reverse the xml tables into the supprted format? Is there another option?

    My reason for going through this is that i got hit with an adware trojan and it decimated my group policies within my registry.

    Ive seen others mention the problem of not having the applicable templates but no responses to the fact.

    Reply

  87. Martin
    January 8, 2017 @ 7:47 AM

    Right-clicking on the bat file for x64 and running as admin did not work for me either, but Skar’s idea of doing the cmd prompt as admin and running it worked fine.

    Now to find an article on how to use the darn thing……

    Reply

  88. Al Weber
    January 7, 2017 @ 7:56 PM

    Thanks for this article.

    Reply

  89. Barry
    January 6, 2017 @ 2:01 PM

    For those having difficulties with the simple instructions. PLEASE SEE the comment by D Admin below dated October 29, 2016. If you follow what it says there it will work. Pay careful attention to steps 4-6. In Step 4, where is says “Log out of your current ‘Administrator’ account” it means to simply log off of your existing windows account. (Do NOT be confused and RESTART your computer.) If you click on START, there should be an icon for your windows account on the left side of the screen above the 4 icons for power, settings, file explorer, and documents. Right click on that icon and choose “Sign Out” to get to the initial Win login screen.

    This will bring you to “Step 5” where you will see a new account “Administrator”. Click on it to login. It will be a new account and so be patient because Windows will have to set up the account before you will be able to use it.

    For “Step 6” I had to go to /Windows/users/ and go into my regular account user name directory and then to ‘downloads’ directory in there to find the original downloaded installation file. Since you are in the “master admin” account you can go into any user directory.

    Once I found the downloaded install file I simply followed the original instructions and then – since I have a 64bit Win installation – I copied and pasted the two directories and the gpedit.msc file into the System32 directory.

    After completing those steps the gpedit program worked without any more errors!

    Then I logged out of the Administrator account (Step 7) and back into my regular Windows account (Step 8) and completed the rest of the steps.

    I thought I would add this little bit of extra context in case some might benefit from it. 🙂 🙂 Cheers!

    Reply

  90. skar
    January 4, 2017 @ 7:43 PM

    Thx for the wonderful article. But even after following all the steps gpedit.msc was not working…I solved it by opening command prompt (cmd) as an administrator and opening the C:\Windows\Temp\gpedit\ folder and running x64.bat (I have 64 bit system). Now, gpedit works fine….I think instead of directly running x86.bat or x64.bat in the last step…run it in cmd as an administrator…

    Reply

  91. Ev
    January 3, 2017 @ 2:50 PM

    Thanks a lot! It works well. Keep making good tutorials!!:)

    Reply

  92. Peli
    December 31, 2016 @ 1:47 AM

    Still have an MMC error.
    File is not a valid MMC console or has been created by an earlier MMC version.

    Reply

  93. James Frahm
    December 25, 2016 @ 3:59 AM

    This worked perfectly on Windows 10 Insider Preview build 14986!!
    Thanks a bunch.

    Reply

  94. Shawn
    December 24, 2016 @ 8:12 AM

    I in stalled this editor to Disable Cortana; there are many ways to do this through “hacks” and so forth but, using the local group policy editor is the only way to prevent the program from running in the background and eating a little CPU and memory up, as well as privacy concerns! I had issues at first but, login as admin from tips in the article completed a successful install. My problem is after all that I do not see a search file in gpedit.msc like the Windows 10 Pro editions have. My console and capabilities differ. Looks like an older edition from XP? Is there an update or fix for this. Please, see this video for info on the disable procedure for Cortana.
    https://www.bing.com/videos/search?q=How+to+disable+cortana+properly%3f&&view=detail&mid=483EEDA8C9BC01FDE57A483EEDA8C9BC01FDE57A&FORM=VRDGAR
    Thanks for all the work and a great management console.

    Reply

  95. raff
    December 23, 2016 @ 9:43 PM

    i have the same problems like many others here, followed the instructions, but still get told “MMC snapin not working”. can anybody help, please?! have been trying for weeks now to solve the path length issue which would be very important. it’s drivin me insane!

    Reply

  96. Jimmie
    December 23, 2016 @ 3:30 AM

    followed everything six times; still no honey. i have also activated net framework 3.5, still nothing. help.

    window 10 Home 64 bit/ build -???? (does it really mater?)

    again help – also is there another way to do what needs to be done without going into the registry?

    Reply

  97. Ray
    December 20, 2016 @ 6:25 AM

    Running gpedit.msc as Administrator from System32 folder gives me an error:

    An attempt was made to reference a token that does not exist.

    Reply

  98. Ray
    December 20, 2016 @ 6:23 AM

    Running gpedit.msc on Win10 Home Ed (64bit) from System32 folder gice me an error message:
    An Attempt Was Made to Reference Token That Does Not Exist.

    Reply

  99. Tin Tin Htwe
    December 16, 2016 @ 3:32 PM

    i followed all step mentioned above, still i am getting MMC could not create the snap-in.