how do i fix 31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini error on gpupdate /force command

Question

So when i tried to run the command gpupdate /force on my doamin client computer it spits out a error
Windows attempted to read file \hq.Jatechdesk.lu\sysvol\hq.Jatechdesk.lu\polices{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. group policy settings may not be applied till this issue is resolved.

I have gone to the path where the {31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini file is located and tried to change to permissions for access for Authenticated Users and System,
that does not work.

thigns i have tried doing to fix this issue

1. change file perms
2. deleted the gpt.ini file, then gpupdated /forced the laptops connected to the domain controller, then gone back and added the file back and gp updating it again.
3. changing the Version inside the ini file to version 1, 5, 2, and 4
4. deleting the {31B2F340-016D-11D2-945F-00C04FB984F9} folder but i cant because i need administrators perms even though im doing it as a Domain administrator.
5. i have tried dcgpofix command in powershell as administrator but it says access denied.
6. changing dns settings
7. turning DFS on and Off
8. CHDSK the whole server
9. taking ownership of {31B2F340-016D-11D2-945F-00C04FB984F9} folder to try and Delete it, this also failed
10. sharing the {31B2F340-016D-11D2-945F-00C04FB984F9} and gpt.ini file and giving authenticated users full access including domain ad and system.
11. replacing the gpt.ini file code.
12. replacing the gpt.ini file with another gtp.ini file that works
13. smashing the laptop lol
14. changing the file share perms for the GPT.ini file only.
15. Renaming the gpt.ini file name to GPT.ini instead of gpt.ini
16. removing the registry.vol file and gp updating and adding the file back again.
17. removing the laptop from the domain and adding it back.

i think the only way to fix this is to demote the domain controller and then re premote it and start fresh from scratch.

if anyone can help me fix this feel free to contact me on discord or here.

Answer 1

Do you have any healthy DC in the environment. If so you can perform non-authoritative restore on the broken DC
https://learn.microsoft.com/en-us/troubleshoot/windows-server/group-policy/force-authoritative-non-authoritative-synchronization