Fix Group Policy event 1058 (cannot read gpt.ini from SYSVOL) and event 1030: what error codes 3, 5 and 53 mean, how to test the gpt.ini path, check SYSVOL, DFS and LDAP connectivity, and confirm with gpupdate.
Home › Guides › Group Policy events 1058 and 1030
Last updated 18 November 2026
gpt.ini from a domain controller's SYSVOL share and failed. Open the event's Details tab: it names the DC and gives an error code (in decimal). 3 = path not found, 5 = access denied, 53 = network path not found.Test the exact path from the event as the user or computer that failed, fix what blocks it, then run gpupdate /force. Group Policy is working again when the last Group Policy event in the System log is one of 1500, 1501, 1502 or 1503.
Event 1058 (source Microsoft-Windows-GroupPolicy, symbolic name gpEvent_GPT_NOTACCESSIBLE):
The processing of Group Policy failed. Windows attempted to read the file %9 from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: 1. Name Resolution/Network Connectivity to the current domain controller. 2. File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). 3. The Distributed File System (DFS) client has been disabled.
Event 1030:
The processing of Group Policy failed. Windows attempted to retrieve new Group Policy settings for this user or computer. Look in the Details tab for error code and description. Windows will automatically retry this operation at the next refresh cycle. Computers joined to the domain must have proper name resolution and network connectivity to a domain controller for discovery of new Group Policy objects and settings. An event will be logged when Group Policy is successful.
Older Windows versions logged the same failures from source Userenv in the Application log: 1058 as Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,... ending in The network path was not found., Access is denied. or a Configuration information could not be read from the domain controller message, and 1030 as Windows cannot query for the list of Group Policy objects. Microsoft notes that clients and member servers typically log the pair at startup, while domain controllers log them every five minutes. Look up both IDs, and 1129 and 1500 to 1503, in the Windows Event ID Lookup.
| Code (Details tab) | Meaning | What Microsoft says to check |
|---|---|---|
| 3 | The system cannot find the path specified | The client can't find the path in the event. Test reading gpt.ini over the full network path (below). The archived TechNet page adds that this can be caused by the DFS client not running. |
| 5 | Access is denied | The user or computer doesn't have permission to read the path. On the DC, make sure they can read it; sign out, restart, and sign in again with the same domain credentials to test. |
| 53 | The network path wasn't found | The computer can't resolve the name in the path. Try connecting to \\<dcName>\netlogon using the DC name from the event. |
\\<dcName>\SYSVOL\<domain>\Policies\<guid>\gpt.ini from the DC name, the domain name and the policy folder GUID in the event.type \\<dcName>\SYSVOL\<domain>\Policies\<guid>\gpt.ini. Microsoft notes you must run this as the user or computer whose credentials failed.Also make sure the policy folder holds a USER folder, a MACHINE folder and a Gpt.ini file. If any is missing, Microsoft says computers are likely to keep logging these errors.
net share on each DC and look for SYSVOL and NETLOGON, or check them all at once with Microsoft's loop:
For /f %i IN ('dsquery server -o rdn') do @echo %i && @(net view \\%i | find "SYSVOL") & echoFor /f %i IN ('dsquery server -o rdn') do @echo %i && @wmic /node:"%i" /namespace:\\root\microsoftdfs path dfsrreplicatedfolderinfo WHERE replicatedfoldername='SYSVOL share' get replicationgroupname,replicatedfoldername,state
States: 0 Uninitialized, 1 Initialized, 2 Initial Sync, 3 Auto Recovery, 4 Normal, 5 In Error. For any DC not at 4, check the DFS Replication log for warning 2213 (replication paused after a dirty shutdown) or 4012 (stopped because replication failed for longer than MaxOfflineTimeInDays, which is 60 when content freshness is on).SysVol not ready in netlogon.log and keeps Netlogon paused until DFSR initial replication of SYSVOL completes; only then does it share SYSVOL and NETLOGON.Microsoft says reinitializing DFS Replication for SYSVOL is unnecessary in most cases and can cause data loss if done incorrectly, so find out why replication stopped first and back up SYSVOL before any recovery.
nslookup that the _ldap._tcp.<domain-dns-name> records are registered and point to the right servers. If your AD domain isn't published in public DNS, the same SRV query in the DNS Lookup (which asks public resolvers) comes back empty, which is what a client pointed at ISP DNS sees.GetLdapHandle: Failed to connect <DC> with 81.DisableDFS under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Mup: if it exists and is 1, set it to 0 and restart.Get-GPPermission -Name "TestGPO" -All lists the permission level of every security principal on a GPO.gpupdate /force gpupdate /force /target:computer gpresult /h %Temp%\GPResult.htm
/force reapplies all settings (by default only changed settings are applied); /target limits the refresh to computer or user settings; /wait defaults to 600 seconds. Then check the System log for 1500 to 1503. The archived TechNet page notes Group Policy applies at startup and sign-in and then every 90 to 120 minutes, so an old event may not reflect the current state.
For detail, turn on Group Policy Service logging with the commands Microsoft gives, run gpupdate /force, read %windir%\debug\usermode\gpsvc.log, then turn it off:
md %windir%\debug\usermode reg add "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Diagnostics" /v GPSvcDebugLevel /t REG_DWORD /d "0x00030002" reg add "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Diagnostics" /v GPSvcDebugLevel /t REG_DWORD /d "0x00000000" /f
Search gpsvc.log for lines like GetLdapHandle with the Regex Tester, and keep the Group Policy cmdlets in the PowerShell Cheat Sheet.
Look up 1058, 1030, 1129 and 1500 to 1503 in the Windows Event ID Lookup, keep gpupdate, gpresult and Get-GPPermission in the PowerShell Cheat Sheet, check a client against the DC subnet with the IPv4 Subnet Calculator or IPv6 Subnet Calculator and test gpsvc.log search patterns in the Regex Tester. Related guides: Netlogon event 5719, the trust relationship between this workstation and the primary domain failed and KRB_AP_ERR_MODIFIED.
Windows tried to read a policy's gpt.ini file from a domain controller's SYSVOL share and failed. Microsoft's listed causes are name resolution or network connectivity to the DC, replication latency (the file hasn't replicated to that DC yet), or a disabled DFS client.
They are on the event's Details tab, in decimal. 3 is the system cannot find the path specified, 5 is access denied (permissions on the path), and 53 is the network path wasn't found (the computer can't resolve the name in the path).
Build \\dcName\SYSVOL\domain\Policies\guid\gpt.ini from the DC name, domain and policy GUID in the event and read it from a command prompt. Microsoft says to run the test as the user or computer whose credentials failed; the event's User field shows SYSTEM for computer policy.
Windows couldn't retrieve new Group Policy settings from a domain controller. Microsoft's checks are name resolution and open LDAP ports (389) on the firewall, the client and the domain controller. Windows retries at the next refresh cycle.
Run gpupdate /force and check the System event log. The archived Microsoft page says Group Policy is working when the last Group Policy event is 1500, 1501, 1502 or 1503.
Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.