Deleting Registry.POL file is safe? This will cause any issues with the current Group Policy Settings?

Hello Althaf Asharaf,

Thank you for posting in Q&A forum.
Registry.pol include the registry settings corresponding to Administrative Templates settings.

For local group policy, the registry.pol is under both C:\Windows\System32\GroupPolicy\User (if you set the Administrative Templates user settings) and C:\Windows\System32\GroupPolicy\Machine (if you set the Administrative Templates machine settings).

For domain GPO settings, the registry.pol is under both \dca\SYSVOL\a.com\Policies{3229CA25-D2AF-4E24-93A5-330181BDB946} \User (if you set Administrative Templates user settings within this GPO) and/ or \dca\SYSVOL\a.com\Policies{3229CA25-D2AF-4E24-93A5-330181BDB946} \Machine (if you set Administrative Templates machine settings within this GPO).

Or any other GUID (one GPO has one GUID) like path: \dca\SYSVOL\a.com\Policies{GUID}\Machine and /or \dca\SYSVOL\a.com\Policies{GUID}\Machine.

I want to know, deleting the file will harm the existing policy enabled on the PC's? Since there are on banking environment.

A: I think deleting this file will not harm the existing policy enabled on the PC's. Because after you run gpupdate /force, it should/will recreate registry.pol file on the path.

However, you do not need to delete it usually. Because sometimes when you ran GPUPDATE/FORCE, it will not be success. You should troubleshoot the failed GPUPDATE/FORCE based on the error message you received after you run gpupdate /force. Or you can export gpresult /h on this machine to troubleshoot the failed GPUPDATE/FORCE.

I hope the information above is helpful.

If you have any questions or concerns, please feel free to let us know.

Best Regards,

Daisy Zhou

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.