none
Windows 10 - Event 1058, 1030; wait for network?

    Question

  • Issue:

    I'm encountering issues with group policy processing where startup scripts seem to instantly fail with Event 1030 and an ErrorDescription of "The system cannot find the file specified." The client event log just gets a string of 10 or so red errors on this event type. As far as I've been able to tell, this is only happening on our Windows 10 wireless Surfaces. Windows 7 and Window 10 desktops do not seem to be affected.

    Preceding the slew of Event 1030 events are typically 1 to 2 events of ID 1058: Network access is denied. The event message typically looks like:

    The processing of Group Policy failed. Windows attempted to read the file \\domain\SysVol\domain\Policies\{42ECCD9C-764E-4A3D-8596-A974851F7183}\gpt.ini 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:
    a) Name Resolution/Network Connectivity to the current domain controller.
    b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
    c) The Distributed File System (DFS) client has been disabled.


    Notes and Troubleshooting:

    • The permissions are fine and the paths are accessible
    • DCDiag tests are clean on the 2 2008R2 domain controllers
    • TheFRS, DFSR, DNS, and Directory Service event logs are clean

    Other Observations:

    If I disable the policies generating the 1058 errors, different policies take their place. These policies appear to be the first in the order of inheritance. That is to say that it seems like the first policies that should be processed are the ones that fail. If I unlink those policies then the failures arise from the next policy(s) down the line.

    It seems to me that group policy is being processed before its completely ready to do so. Like the networking on the device is not yet ready to go out and communicate with a DC.

    I already have "Always wait for the network at computer startup and logon" enabled. I also have tried putting a value of 100 seconds for "Specify startup policy processing wait time". The issue persists.

    Any ideas? I'm not sure what else to try.

    Thursday, October 22, 2015 2:59 AM

Answers

  • See if this helps:

    GPOs do not apply on Windows 10 Enterprise x64

    "Support confirmed that there is a bug in Windows 10 and they will provide a hotfix one day they have fixed it. Until now the only Workaround is to disable the UNC hardening for netlogon and sysvol Shares in the registry."


    Rolf Lidvall, Swedish Radio (Ltd)

    • Marked as answer by itangir Wednesday, October 28, 2015 4:22 AM
    Thursday, October 22, 2015 7:10 AM

All replies

  • See if this helps:

    GPOs do not apply on Windows 10 Enterprise x64

    "Support confirmed that there is a bug in Windows 10 and they will provide a hotfix one day they have fixed it. Until now the only Workaround is to disable the UNC hardening for netlogon and sysvol Shares in the registry."


    Rolf Lidvall, Swedish Radio (Ltd)

    • Marked as answer by itangir Wednesday, October 28, 2015 4:22 AM
    Thursday, October 22, 2015 7:10 AM
  • > *The processing of Group Policy failed. Windows attempted to read the
    > file
    > \\domain\SysVol\domain\Policies\{42ECCD9C-764E-4A3D-8596-A974851F7183}\gpt.ini
    > from a domain controller and was not successful.
     
    Sysvol replication is broken, probably due to a Journal Wrap Error.
    Check NTFRS/DFSR eventlogs and repair.
     
    If everything seems ok, simply do a D4 restore on the PDC and afterwards
    a D2 restore on all other DCs.
     

    Greetings/Grüße, Martin

    Mal ein gutes Buch über GPOs lesen?
    Good or bad GPOs? - my blog…
    And if IT bothers me - coke bottle design refreshment (-:
    Thursday, October 22, 2015 8:08 AM
  • Thanks Rolf!

    I've tested the registry workarounds you linked on a few devices and it at least appears to have fixed the issues I was experiencing. Hopefully those results continue to be the case on the others.

    Wednesday, October 28, 2015 4:24 AM
  • Thanks Rolf!

    I've tested the registry workarounds you linked on a few devices and it at least appears to have fixed the issues I was experiencing. Hopefully those results continue to be the case on the others.

    No problem, only glad to help. When it comes to Windows 10 it seems like MS has been prioritizing the consumer version. Enterprise versions/environments are still not quite ready/fully tested. 

    Rolf Lidvall, Swedish Radio (Ltd)

    Wednesday, October 28, 2015 8:44 AM
  • Rolf - Have you heard of any news on a permanent fix for this yet please?
    Tuesday, April 05, 2016 9:18 PM
  • Rolf - Have you heard of any news on a permanent fix for this yet please?
    There is more info in the thread I posted in my first reply.

    Rolf Lidvall, Swedish Radio (Ltd)

    Wednesday, April 06, 2016 7:18 AM
  • Ok.... So we are all in the dark of when there will be a fix...

    I am however still confused as although hardening may be on when it shouldn't be surely hardening should work??

    Friday, April 15, 2016 3:22 PM