Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Group Policy event 1058: "The processing of Group Policy failed. Windows attempted to read the file" from a domain controller

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

Event 1058 reads: "The processing of Group Policy failed. Windows attempted to read the file %9 from a domain controller and was not successful." The %9 stands for the file name in the event. The computer could not read that file from a domain controller, so Group Policy settings may not apply until the cause is fixed.

Read the error code on the event's Details tab first. Microsoft's page gives separate checks for code 3 (path not found), code 5 (access denied) and code 53 (network path not found). Test the path as the user or computer that failed, and only then change anything.

What the error means

Microsoft's guidance page lists three possible causes in the event text itself, and says the issue "may be transient": name resolution or network connectivity to the current domain controller; file replication latency, where a file created on another domain controller has not replicated to the current one; and the Distributed File System (DFS) client being disabled.

The page says the Group Policy service logs the name of the domain controller and the error code, shown in decimal on the Details tab of the event in Event Viewer, and that the code and its description narrow the cause.

An older Microsoft page for Windows Server 2003, Windows XP and Windows 2000 shows the same event as a Userenv event with a different wording: "Windows cannot access the file gpt.ini for GPO …". Its error message placeholder may read "The network path was not found.", "Access is denied." or "Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied." That page also says Event 1030, "Windows cannot query for the list of Group Policy objects", is logged alongside it, that client computers and member servers log both when the computer starts, and that domain controllers log them every five minutes.

Both pages are written for Windows Server; the older one names three older operating systems. Neither gives a version range for current releases beyond "Supported versions of Windows Server".

Likely causes

Cause What you see How to confirm
Path not found (error code 3) Event 1058 with "The system cannot find the path specified" Build the gpt.ini path from the event and open it as the failing user or computer
Access denied (error code 5) Event 1058 with "Access is denied" Sign out, restart, sign in with the same domain credentials; check read permission on the path
Network path not found (error code 53) Event 1058 with "The network path wasn't found" Open \\<dcName>\netlogon for the DC named in the event
Name resolution or DNS settings wrong The same events at start-up Check which DNS servers the computer uses
The DFS client is disabled Event text lists the DFS client as a cause Read DisableDFS under the Mup service key; Microsoft's older page gives the value
SMB signing settings differ between client and DC Userenv errors; "The account is not authorized to log in from this station" Compare SMB signing settings; Microsoft's page describes this for older systems
Replication latency of a new policy The event appears for a newly created or edited policy Microsoft's guidance page names replication latency as a cause but gives no test

Prove the cause before changing anything

All of these only read.

Open the Application or System log on the computer that logged the event, and the event's Details tab. Write down the domain controller name, the error code and the policy GUID. Microsoft's guidance page also says the Details tab holds the error code and description, and that the Group Policy operational log can be used to follow one run of processing. Check the User field: Microsoft's page says a valid user name there means the failure was in user policy processing, and "SYSTEM" means computer policy processing.

For error code 3, Microsoft's page builds the path from what the event shows:

\\<dcName>\SYSVOL\<domain>\Policies\<guid>\gpt.ini

Run it as the user or computer whose credentials failed. Microsoft's page notes: "You must run this command as the user or computer whose credentials previously failed." If the file opens, the path and permissions work from where you are.

For error code 53, the page tests the DC's netlogon share:

\\<dcName>\netlogon

Example (illustrative): at contoso.com.au the member server app01 logs event 1058 at every start-up, with error code 53 and the domain controller dc01. From app01, \\dc01\netlogon does not open. The name dc01 is not resolving from that server, so the cause is name resolution on app01, which the table lists as its own row.

For name resolution, Microsoft's older page says computers must use DNS servers that can resolve the SRV records and host names for the Active Directory forest, and that a common configuration error is for client computers to use their internet provider's DNS servers. Check the DNS servers the computer is configured with:

ipconfig /all

Microsoft's page says to "Note the DNS entries that are listed on the screen."

Fix

Fix the cause the error code points to. Microsoft's page lists:

  • Error code 3. The client cannot find the path in the event. Test connectivity to the DC's SYSVOL with the path above.
  • Error code 5. The user or computer lacks permission to the path. Microsoft's page says the user and computer need permission to read the path in the event; it gives no steps for changing permissions. To test credentials, it says to sign out of the computer and restart it, then sign in with the domain credentials used before (the restart step is below).
  • Error code 53. The computer cannot resolve the name in the network path. Identify the DC from the event and try to connect to its netlogon share.

The permission fix on the domain controller is a change to security on the domain controller's SYSVOL folders, and it reaches every computer that reads that policy. Microsoft's page gives no steps for it.

For the sign-out and restart, the step changes nothing in the domain but interrupts the server.

Disruptive step: the restart in the next sentence closes every session and stops every service on the computer. Choose a quiet time, and do it on a server only when no one depends on it.

Sign out, restart the computer and sign in with the same domain credentials, then read the event log again.

There is no change to undo, because the restart changes no setting.

DFS client disabled

Microsoft's older Userenv page is written for Windows Server 2003, Windows XP and Windows 2000, and its DFS step is for those systems; Microsoft's guidance page names the DFS client as the third cause for supported versions of Windows Server but gives no registry steps. The Userenv page says the DFS client must be enabled in the registry on all computers, under the Mup service key, in a DWORD value named DisableDFS, and tells you to open Registry Editor and set it to 0 if it is 1. Whether the same value applies to current Windows is not stated on either page. The commands below are not on the Userenv page; they carry the same key, value and data through the syntax on Microsoft's reg query, reg export, reg add and reg import pages. Check the value first:

reg query "HKLM\SYSTEM\CurrentControlSet\Services\Mup" /v DisableDFS

Microsoft's page says to change the value only if it exists and equals 1; if it is 0 or does not exist, "don't make any change". Run the change below only when the query returned 1. Before you change it, export the key to a new file:

reg export "HKLM\SYSTEM\CurrentControlSet\Services\Mup" C:\Temp\mup-before-dfs.reg

Create C:\Temp first if it does not exist.

Risk: the next command sets DisableDFS to 0 on this computer, which turns the DFS client on. Microsoft's page says to restart the computer if you changed the value.

reg add "HKLM\SYSTEM\CurrentControlSet\Services\Mup" /v DisableDFS /t REG_DWORD /d 0 /f

To undo it, import the saved file:

reg import C:\Temp\mup-before-dfs.reg

Disruptive step: the restart that Microsoft's page asks for after the change closes every session and stops every service on the computer, and the undo needs a restart too. Choose a quiet time.

Restart the computer after the change, and again after the undo if you use it.

Other checks from Microsoft's pages

For name resolution and DNS failures, Microsoft's older page describes checking that the computer uses DNS servers that resolve Active Directory SRV and host records, clearing the DNS cache and registering the computer's DNS names again, and confirming that Client for Microsoft Networks is enabled. Its steps are written with Windows XP, Windows 2000 and Windows Server 2003 dialog screens, so they do not match current Windows.

For SMB signing, the older page says computers may fail to connect to domain controllers when SMB signing is required on the controllers and disabled on the clients, and describes registry values under the lanmanserver and lanmanworkstation parameters for those older systems. The same page says to restart the Server and Workstation services, not the computers. Microsoft's page names no current Windows version for those registry changes. Compare the SMB signing policy on the client and on the domain controller before assuming that page applies.

For error 1030 beside 1058, Microsoft's guidance page says to check that LDAP ports are open, and says to use portqueryUI or telnet for port 389 to check connectivity, and to confirm the client resolves the domain controller's host name.

Confirm the fix

  • Restart Group Policy processing the way your environment routinely does and read the event log again: event 1058 should no longer be logged.
  • For event 1030, Microsoft's guidance page says an event is logged when Group Policy is successful.
  • Run the gpt.ini path test again as the failing user or computer; it should open.

What to watch afterwards

  • Start-up events on member servers. Microsoft's older page says they log 1058 and 1030 at start-up when affected.
  • Domain controllers: Microsoft's older page says they log the pair every five minutes when affected.
  • Any new policy before it has replicated to every domain controller.

Risks and limits

These commands have not been run or lab-tested.

Microsoft's guidance page covers "Supported versions of Windows Server" without listing them. The Userenv page is written for Windows Server 2003, Windows XP and Windows 2000. Permission changes on SYSVOL affect every computer that reads that policy, so record the existing permissions first. A restart interrupts everyone using the machine.

Sources