Fix: Unable to Open Local Group Policy Editor Windows 10
Mục Lục
Fix: Unable to Open Local Group Policy Editor Windows 10
Local Group Policy Editor is a program that manages and configures the system function. Windows systems allow administrators to set their personal Local Group Policy Editor manually. However, hassles may come across at times. You are unable to open Local Group Policy Editor Windows 10. Take a deep breath, here are some general ways provided in the following.
Failed to Open the Local Group Policy Editor Windows 10
When you meet a problem such as unable to open the Local Group Policy Editor Windows 10, it could be for two reasons:
- 1. You are using Windows 10 Home edition;
- 2. Your Windows 10 has been getting into system failure.
To view the system edition, right-click on Menu icon then select Settings. In Settings window, navigate to System About, then you can see the information of Windows specifications in the right pane.
According to different cases, you can locate the corresponding part below to address the issue.
Part 1: Fix unable to open Local Group Policy Editor in Windows Home edition
Windows Home edition does not contain Local Group Policy Editor feature, so it returns an error notification to you. Nevertheless, there are still some workarounds to manage Local Group Policy Editor.
Way 1: Upgrade your editions of Windows 10
You can upgrade to Windows 10 Professional edition. Just download Media Creation Tool to your computer and install it. Follow the wizard you can finish to upgrade your system to Windows 10 Profession edition.
Way 2: Implement Local Group Policy Editor features through Microsoft Manage Console
Step 1: Press Windows + R key to invoke Run dialog then type “mmc” without quotes to open Microsoft Manage Console.
Step 2: Click File then select “Add/Remove Snap-in…” from the drop-down.
Step 3: From the snap-ins list, select the one you want to add then click on Add.
Step 4: The Select Computer or Domain window will popup. You can manage it then click Finish.
Step 5: When you finish the stapes above, you will go back to Microsoft Management Console window. Here, you will see the snap-ins you just added under Console Root.
Step 6: Right-click on the snap-in and select “New Taskpad View…“.
Step 7: Follow the wizard to set the configuration you need.
Part 2: Failed to open Local Group Policy Editor when not using Windows edition
Before solving the problem, you can run “gpupdate /force” to force update Local Group Policy Editor. Relaunch Local Group Policy Editor to check if it returns normally. If you still receive the error, try the solutions to troubleshoot.
Solution 1: Change the value data in Registry Editor
Step 1: Hit Windows key + R to launch Run dialog box.
Step 2: Input “regedit” then click OK to open Registry Editor.
Step 3: Expand the following keys one by one.
HKEY_CLASSES_ROOT/CLSID/{8FC0B734-A0E1-11D1-A7D3-0000F87571E3}/InProcServer32
Step 4: In the right pane, double-click the Default item and input “%SystemRoot%/System32/GPEdit.dll” into the box under Value data.
Solution 2: Change the Environment Variables
Step 1: In Cortana search bar, type Control Panel and hit Enter.
Step 2: Click on Systems in Control Panel window. If you are failed to see the option, click the down arrow next to View by and select Large icons from the drop-down.
Step 3: In the left side, click on Advanced system settings.
Step 4: In System Properties window, click on Advanced tab then tap on Environment Variables.
Step 5: Under System variables, click on Path.
Step 6: Copy and paste the following into the form.
- %Systemroot%/System32
- %Systemroot%
- %Systemroot%/system32/WBEM
Solution 3: Run regsvr32 filemgmt.dll
Step 1: Hit Windows + R then input regsvr32 filemgmt.dll in the box and tap on OK.
Step 2: If all goes well, launch your Local Group Policy Editor. Otherwise, Windows 10 will show you failed to open Local Group Policy Editor error again. It mainly due to the Local Group Policy Editor cannot find the framedyn.dll file. Copy the files to “%windir%/system32/wbem” directory, if you have installed a script in Windows 10.
Related Articles: