Event ID 1058 Processing of Group Policy failed.Windows attempted to read file \\domain.com\SysVol\ domain.com \Policies\{xx}\gpt.ini from domain controller and was not successful

CptRetro 501 Reputation points

Hello all,

Since a few weeks we observe more and more the phenomenon that GPOs are not processed after the start of a Windows Server 2016. In the process of troubleshooting, we noticed that a gpupdate /force brings an error message stating that \domain\Sysvol etc. would not be accessible. If I check this, I find out that I actually don't have access to the UNC path. However, if you wait a certain amount of time (30-60 minutes), the situation returns to normal and, in addition to functional access, GPO retrieval also works again.

There are also no entries in the event log that indicate an error of a service. Therefore I am looking for some advice here.


Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,567 questions
0 comments No comments
{count} votes

Accepted answer
  1. CptRetro 501 Reputation points

    Hey, we use Citrix App Layering to create the image. We had to open the, so called, platform layer and this solve the issue. During the investigation we found that this is recommended by citrix.

    0 comments No comments

3 additional answers

Sort by: Most helpful
  1. Anonymous

    Please run;

    Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log
    repadmin /showrepl >C:\repl.txt
    ipconfig /all > C:\dc1.txt
    ipconfig /all > C:\dc2.txt
    ipconfig /all > C:\dc3.txt

    then put unzipped text files up on OneDrive and share a link.

  2. Limitless Technology 39,506 Reputation points

    Hello @CptRetro

    Do check out the below link, where similar issues have been discussed and resolved



    --If the reply is helpful, please Upvote and Accept as answer--

    0 comments No comments

  3. CptRetro 501 Reputation points

    Hello all, sorry for my late response. I spent a hole lot of time and it went out, that Citrix Applayering was the cause of that issue. With every new OS Layer it is necessary to open and close the Platform Layer. This solve the problem. Thanks guys