Windows Server login took 736 seconds after update reboot - NETLOGON 5719 and GPClient delays

2026-11-20T05:31:19.33+00:00

We have a Windows Server joined to an Active Directory domain. After installing recent Windows updates and rebooting, the server booted successfully, but logging in took an extremely long time.

Observed events:

  • Winlogon reported:
    • "GPClient is taking long time to handle the notification event (Logon)"
    • GPClient took approximately 736 seconds to complete logon processing.
  • System log contained:
    • NETLOGON Event ID 5719
    • Secure session could not be established with a Domain Controller during startup.
  • Group Policy printer processing generated:
    • RPC Server Unavailable (0x800706ba) errors.

Questions:

  1. Has anyone observed similar behavior after recent Windows Server updates?
  2. Could delayed network adapter or Hyper-V virtual switch initialization cause NETLOGON 5719 and lengthy GPClient processing during startup?
  3. Are there recommended diagnostics to collect if the issue reoccurs?
Windows for business | Windows Server | Directory services | Deploy group policy objects
0 comments No comments

2 answers

Sort by: Newest
  1. Daniel Micomyiza 0 Reputation points Independent Advisor
    2026-11-20T06:00:57.81+00:00

    Hello Udukumbura,

    Welcome to Microsoft Q&A and thank you for providing the details of the issue.

    Based on what you describe, the issue seems to be the network not ready when the server started.

    • this pattern is common after a reboot, but I can't confirm a known issue with the update without its KB number. Please check the Windows release health page for it.
    • Network or Hyper-V switch timing: If the network adapter or the virtual switch initializes late, the server contacts the domain controller too early, and each failing Group Policy item then adds to the delay.

    if it happens again you can try these Diagnostics:

    • Compare timestamps in the System log (NETLOGON, NlaSvc, Hyper-V-VmSwitch) and in the GroupPolicy Operational log.
    • Run gpresult /h report.html, nltest /sc_verify:<domain>, and dcdiag after logon.
    • Capture a startup network trace with netsh trace start capture=yes persistent=yes, then reboot and run netsh trace stop.

    In the meantime, it is worth reviewing whether the "Always wait for the network at computer startup and logon" policy is configured, and whether the print servers used by the printer policies are reachable.

    Useful Microsoft references:

    If you find this information helpful, please click Accept Answer. This helps other

    community members identify useful solutions to similar issues.

    Thank you for choosing Microsoft Q&A.

    Was this answer helpful?


  2. AI answer

    2026-11-20T05:32:27.75+00:00

    The evidence fits a startup network-readiness race—Netlogon and Group Policy attempted domain-controller communication before the network path was usable—so first update the physical/virtual NIC stack and make startup policy processing wait for domain connectivity, then capture correlated logs during the next reboot.

    Microsoft does not document an update issue matching the exact combination of a 736-second GPClient delay, NETLOGON 5719, and printer processing error 0x800706ba. A reported Windows 11 build regression is not sufficient evidence for an unspecified Windows Server version or KB.^1^

    Address startup network readiness

    Microsoft documents NETLOGON 5719 and Group Policy failures when Netlogon starts before the adapter, switch, DHCP, 802.1X, or other network-access components are ready. A Hyper-V virtual switch or virtual NIC initializing late could therefore produce the same sequence, although these events alone do not prove it was the cause.^2^

    1. Update the complete NIC path
      • Install the current vendor-supported physical NIC driver and firmware on the Hyper-V host.
      • Update the guest integration components through the supported servicing mechanism.
      • Check for NIC teaming, VLAN, DHCP, 802.1X/NAC, or switch link-negotiation delays.
      • For a physical switch port connected to a server, enable the vendor’s edge/PortFast equivalent where the network design permits it. Microsoft identifies current NIC drivers or PortFast as the primary resolution for this startup condition.^2^
    2. Enable synchronous startup processing
      • Open the applicable GPO.
      • Go to Computer Configuration → Administrative Templates → System → Logon.
      • Enable Always wait for the network at computer startup and logon.
      This delays logon until startup Group Policy processing completes and a network with domain-controller connectivity is available.^3^
    3. If the server has a variable but measurable startup delay, configure Computer Configuration → Administrative Templates → System → Group Policy → Specify startup policy processing wait time based on the observed time required to obtain DC connectivity.^2^

    Avoid adding registry timeout values initially. Options such as ExpectedDialupDelay apply only to particular conditions—for example, when the machine already has an IP address but NAC/NAP quarantine delays DC access. Registry changes also require a backup first.^2^

    Prepare diagnostics before the next reboot

    Enable both traces before reproducing the issue:

    md %windir%\debug\usermode
    reg add "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Diagnostics" ^
     /v GPSvcDebugLevel /t REG_DWORD /d 0x00030002 /f
    nltest /DBFlag:2080FFFF
    

    GPSvc verbose logging can affect performance and consume disk space, so leave it enabled only while reproducing the problem. Netlogon writes to %windir%\debug\netlogon.log.^4^

    After the delayed logon, collect:

    gpresult /h %TEMP%\GPResult.htm
    gpresult /r > %TEMP%\GPResult.txt
    wevtutil epl System %TEMP%\System.evtx /ow:true
    wevtutil epl Application %TEMP%\Application.evtx /ow:true
    wevtutil epl Microsoft-Windows-GroupPolicy/Operational %TEMP%\GroupPolicy.evtx /ow:true
    

    Also preserve:

    • %windir%\debug\usermode\gpsvc.log
    • %windir%\debug\netlogon.log and netlogon.bak
    • Hyper-V host System and Hyper-V virtual-switch-related event logs covering the same interval
    • A packet trace started before reboot, if the behavior is reproducible

    These Group Policy exports are Microsoft’s recommended support-data set.^5^

    Correlate timestamps for:

    • First usable IP address and default gateway
    • DNS/SRV resolution
    • DC discovery
    • LDAP/RPC connection attempts
    • Hyper-V vNIC/vSwitch link-up
    • Printer GPO start, timeout, and completion

    For DC Locator validation, use ipconfig /all, DNS lookups, DC service-port tests, and—if needed—a simultaneous packet capture between the member server and DC.^6^

    Disable tracing afterward:

    nltest /DBFlag:0x0
    reg add "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Diagnostics" ^
     /v GPSvcDebugLevel /t REG_DWORD /d 0 /f
    

    If the issue recurs despite immediate DC connectivity, collect TSS on the affected member with .\TSS.ps1 -Scenario ADS_AuthEx and, where possible, .\TSS.ps1 -Scenario ADS_Auth on the DC, then open a Microsoft Support case with the exact Server edition/build, installed KB, traces, and event exports.^7^


    References

    1. KB5065426 (OS Build 26100.6584) slow logins like KB5062553 (OS Build 26100.4652) - Microsoft Q&A
    2. Netlogon event ID 5719 or Group Policy event 1129 - Windows Server | Microsoft Learn
    3. Turn on automatic logon in Windows
    4. Enabling debug logging for the Netlogon service
    5. Applying Group Policy troubleshooting guidance
    6. Troubleshoot domain controller location issues in Windows
    7. Collect data to analyze and troubleshoot Group Policy scenarios
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.