Fix- Failed to open the Group Policy object on this computer problem in Windows 10 / 11

Some usesrs are facing this issue , that they are unable  to open group policy. There may be many reasons behind it. If the DNS server doesn’t function properly on a computer the user may see this error message “Failed to open the Group Policy object on this computer” when they try to use Local Group Policy Editor. The main purpose of the DNS server is to log system error in the DNS event log. To solve the issue follow this easy fix on your computer.

Before proceeding make sure you have admin rights before the fix described below.

Fix- Rename Machine in GroupPolicy folder-

Renaming the Machine folder in Group Policy folder will solve the issue.

1. Launch the Run window by pressing Windows key+R.

2. In the Run window, type “system32“‘ and hit Enter.




3. When the System32 folder opens up, click on “View“.

4. Then choose the “Options” settings.


View Options


5. After that, go to the “View” tab.

6. After that, check the option “Show hidden files, folders and drives“.


View Show Hidden


7. Finally, click on “Apply” and then click on “OK“.


Apply Ok


8. Scroll down and double click on the “Group Policy” to access it.


Dc Group Policy Folder


9. In the Group Policy folder, right-click on the “Machine” folder and click on “Rename” to rename the folder.


Machine Rename


10. Set the name of the folder as “Machine.old“.




Close File Explorer window.

Restart your computer. After restarting your computer, try to modify any policy from the Local Group Policy Editor.  The error message won’t pop up on your computer.

10 thoughts on “Fix- Failed to open the Group Policy object on this computer problem in Windows 10 / 11”


    I found a MORE SIMPLE SOLUTION that worked. My personal laptop had been joined to a secure government domain, and when I left the job regaining admin rights to my own PC took some effort. I had received same error message described in this thread. To regain ability to edit to my own Group Policy I followed this:

    “The solution is to delete the contents of the folder “c:\windows\system32\grouppolicy”. You can then open the Group Policy Editor successfully.”

    I inspected contents of folder first and saw several years worth of logs and files from my old employer. So I proceeded to delete the contents as instructed. When I re-opened gpedit.msc the error had disappeared and new subfolders plus gpt.ini file were automatically written into the folder. They all turned out to be empty but the result was that I had control of my Group Policy was fixed.

    Credit goes to:

Comments are closed.