The processing of Group Policy failed, Event ID 1058

Processing of Group Policy failed Event ID 1058

Error message Group Policy Processing Failed, Event ID 1058 occurs in Windows Server, when the operating system can not read the file from a domain controller. The Group Policy service reads information from the Active Directory and the sysvol share located on a domain controller. However, the lack of network connectivity or permission problem prevents Group Policy from applying to the user or the computer.

The error message might look like

Type of event: error
Event Source: Userenv
Event Category: None
Event ID: 1058
Computer: TWC-ASH-Post01
The description:
Windows can not access the gpt.ini file for GPO cn = {18C553C9-0D15-4A3A-9C68-60DCD8CA1538}, cn = strategies, cn = system, DC = LBR, DC = CO, DC = ZA. The file must be present at the location . (Access is denied.) Group Policy processing has been discontinued.

Group Policy Processing Failed, Event ID 1058

If you read the event log, you will find that because the service could not read the policy, it was not possible to apply it. The good news is that this is only a temporary problem. In addition to the network problem, this may also be due to the latency of the file resolution service and the disabling of the DSF client.

When checking logs, if you check under the Details tab of the error message in the Event Viewer, any of these error codes can be present: error code 3, error code 5, and error code 53. Follow these suggestions to resolve the problem.

  1. The system does not find the specified path – error code 3
  2. Access denied – Error Code 5
  3. The network path was not found – Error Code 53

After any of these methods, if you need to troubleshoot a network, see our Network Troubleshooting Guide.

1) The system does not find the specified path – error code 3

It occurs when the DFS client does not run on the client computer because it can not find the path specified in the event. To test client connectivity to the sysvol of the domain controller:

  1. Look for the name of the domain controller available in the details of the error event.
  2. Check if the fault has occurred while processing the user or the computer
    • User Policy Processing: The User the event field will display a valid user name
    • Processing of the IT policy: the User the field will display "SYSTEM".
  3. Then you must compose a complete network path to the gpt.ini file. The format should be like SYSVOL <field> Policies <guid> gpt.ini. All of this will be available in the event log.
    • <DCName>: Name of the domain controller
    • <field>: This is the name of the domain,
    • <guid>: This is the GUID of the policy folder.

After that, make sure that you can read the gpt.ini file using the full network access path you created in the step above. You can do it from the command prompt or Windows. Make sure to try it with the user or the computer whose credentials previously failed.

2) Access is denied – Error Code 5

If the error code is 5, there is a problem with the authorization. When the user or the computer does not have the appropriate permissions to access the specified path in the event. The resolution is simple, make sure that the user or the computer has the permission.

Log off and restart the computer, and then log on to the computer with the previously used domain credentials. If this does not work, be sure to assign the domain controller authorization.

3) The network path was not found – error code 53

The error code 53 means that the computer is not able to resolve the name in the provided network access path. You will need to use the same computer or user to check if you can manually access the network path.

  1. Identify the domain controller used by the computer available in the Error event
  2. Then, connect to the netlogon share on the domain, that is, try to directly access the path <DCName> netlogon. where <DCName> is the name of the domain controller in the error event.
  3. If the path does not resolve, there is a problem with the path that needs to be fixed. If you are sure the path is correct, check with permission.

Post this; you must check if everything is fine. The best way is to launch the gpudate command in the prompt. When the gpupdate command is complete, open the Event Viewer to see if the error persists.

Leave a Reply