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^
- 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^
- 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^
- 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
- KB5065426 (OS Build 26100.6584) slow logins like KB5062553 (OS Build 26100.4652) - Microsoft Q&A
- Netlogon event ID 5719 or Group Policy event 1129 - Windows Server | Microsoft Learn
- Turn on automatic logon in Windows
- Enabling debug logging for the Netlogon service
- Applying Group Policy troubleshooting guidance
- Troubleshoot domain controller location issues in Windows
- Collect data to analyze and troubleshoot Group Policy scenarios