@CWooldridge
I have found this issue beginning in Nov 2022, even with Windows Server 2022. It rared its ugly head after that kerberos fix that November that broke the world. After that, there was a hotfix that fixed it on 2022, 2019, 2016, etc. I noticed this began again in the early vNext 2025 builds. It's still there as of the build available today, even after all the hotfixes apply after updating. Obviously the bandaid for now is restart-netadapter * - or specify your NIC name, if you're concerned about it restarting the wrong NIC, to run at startup via Task Scheduler. This really isn't a fix, but a mere stopgap to allow this to operate properly as it becomes a domain controller. Let's hope someone from MS is paying close attention and addresses this. I've tried all the registry keys, etc, and that does not work. In fact, I think 2025 completely ignores the AlwaysExpectDomainController as everyone swears is the fix. I think they still have problems. This appears to be a nasty conflict between NLA, Windows Defender Firewall, and something hanging in the OS upon the NIC initialization. Also, setting service dependencies isn't the answer either. This should work out of the box. Glad I'm not the only one having this issue.
