Solve the inability to run gpedit.msc (group policy) method

                                                                                                                                                                                         

Sometimes, due to the Trojans in the machine and other reasons, the group policy can not be used, and we urgently need to run the group policy to set up, what should I do? Reinstalling the system, of course, is one of the methods (^.^), but there is a simple method
Why not use it? Here is a brief description of several solutions that cannot run gpedit.msc (group policy). >Methods
.

Method one:
Start → Run → Enter regedit, open the registry editor, find the registry key HKEY_CURRENT_USER\\Software\\Policies\\Microsoft\\MMC, please set the value of RestrictToPermittedSnapins Set to 0. Method 2:
Start →Run → Enter regedit, open the registry editor, find the registry key HKEY_CURRENT_USER\\Software\\Policies\\Microsoft\\Mmc\\{8FC0B734-A0E1-11D1-A7D3-0000F87571E3 }\\Restrict_Run and HKEY_CURRENT_USER\\Software\\Policies\\Microsoft\\MMC\\{0F6B957E-509E-11D1-A7CC-0000F87571E3}\\Restrict_Run Set the value of Restrict_Run to 0, and restart computer
after the modification. Method 3:
Start →Run → Enter regedit, open the registry editor, find the default in the registry key HKEY_CLASSES_ROOT\\CLSID\\{8FC0B734-A0E1-11D1-A7D3-0000F87571E3}\\InProcServer32 Change to: %SystemRoot%\\System32\\GPEdit.dll, restart after modification. Method 4:
Check the environment variables: a, click “ start & rdquo; menu b, open & ldquo; control panel & rdquo; c, open in the "control panel" “ system & rdquo; d, in <;System Properties" Click on “Advanced" Label e, click “environment variable" button f in the "Advanced" tab, "system variable" in "environment variable" The variable value in the box is named Path. The value of the modified variable is: %Systemroot%\\System32; %Systemroot%; %Systemroot%\\system32\\WBEMMethod 5:
Start →Run →Enter regsvr32 filemgmt.dll Method 6:
This error can occur if Group Policy cannot find framedyn.dll. If you use an installation script, make sure the script is placed in the %windir%\\system32\\wbem directory in the system path. By default, %windir%\\system32\\wbem already exists in the system path. If not, try copying the Framedyn.dll file from the \\windows
\\system32\\wbem directory to the \\windows
\\system32 directory. Attachment: If the MMC items mentioned in Method 1 and Method 2 are not found in your Computer
registry, then create them manually. Or directly copy and paste the following content into Notepad, and save it as a file with the suffix .reg, double-click to run the .reg file.
Windows Registry Editor Version 5.00[HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy Objects\\LocalUser\\Software\\Policies\\Microsoft\\MMC][-HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy Objects\\LocalUser \\Software\\Policies\\Microsoft\\MMC\\{8FC0B734-A0E1-11D1-A7D3-0000F87571E3}]"Restrict_Run"=dword:00000000[HKEY_CURRENT_USER\\Software\\Policies\\Microsoft\\MMC][-HKEY_CURRENT_USER\\Software\\Policies\\Microsoft\\ MMC\\{8FC0B734-A0E1-11D1-A7D3-0000F87571E3}]"Restrict_Run"=dword:00000000[HKEY_CURRENT_USER\\Software\\Policies\\Microsoft\\MMC]"RestrictToPermittedSnapins"=dword:00000000For %%i in (C:\\windows \\system32\\*.dll) Do regsvr32.exe /s %%iFor %%i in (C:\\windows\\system32\\*.ocx) Do regsvr32.exe /s %%i