Windows Time service not synchronizing after FlyOOBE upgrade

I used the release from early January 2026 to upgrade a Windows 10 Pro system to Windows 11 (v10.0.26200.8655) Since then, my Windows Time service (w32time or w32tm) fails to synchronize with the error "no time data available".

• w32tm /monitor succeeds
• w32Time configured for type=NTP
• No GPO present
• DNS is OK
• Other clients on my LAN can sync time with no issue
• SFC and DISM completed
• Service has been unregistered/registered
• Debug log repeatedly shows: NtpProvider: Created 0 sockets. ** NTP sample vector is empty. No new NTP sample is available.

Has anyone else noticed or experienced this? I have manually set the date/time to "close enough" and in the grand scheme of things this is a minor inconvenience.