gpedit.msc
).gpedit.msc
on Windows 7 64 bit Home Premium.C:WindowsTempgpedit
folder.%username%:f
with '%username%':f
icacls %WinDir%SysWOW64gpedit.dll /grant:r %username%:f
icacls %WinDir%SysWOW64gpedit.dll /grant:r '%username%':f
/online
used to tell it to apply to the running OS/norestart
tells it to not auto rebootgpedit
here.regedit
. The correspondences, including the different values, are documented on gpsearch.azurewebsites.net. It is apparently maintained by a Microsoft employee, so it's pretty reliable.%WinDir%SysWOW64GPBAK
.%WinDir%SysWOW64
folder. Namely the gpedit.dll
, fde.dll
, gptext.dll
, appmgr.dll
, fdeploy.dll
.%WinDir%System32
folder and remove or replace the gpedit.msc
that was manually copied over. You may want to delete gpedit.msc
from the %WinDir%SysWOW64
folder also.%WinDir%SysWOW64GroupPolicy
, %WinDir%SysWOW64GroupPolicyUsers
folders are created and modified by the script as well. There are reverses to be made here.%WinDir%SysWOW64
folder as well.Start Menu -> Windows Administrative Tools -> Local Security Policy
app was now present. We couldn't get the gpedit.msc
to load directly from command line until Resetting the Installation from Settings -> Updates -> Recovery
.%SystemRoot%servicingPackages
Microsoft-Windows-GroupPolicy-ClientExtensions-Package*.mum
and Microsoft-Windows-GroupPolicy-ClientTools-Package*.mum
.mum
files and one by one run the following dism
command using the Package File Names.Y
key to restart and finish adding any remaining packages.gpedit.msc
gives a missing token error. Otherwise, it may be better to avoid re-registering the dll. To correct a missing token error, try navigating to %WinDir%System32
and run this command taken from this social.technet.microsoft.com article:Reset This PC
for a clean gpedit.msc
. Back up your files first.