Workaround: Restart the network Adapter
Microsoft has suggested a temporary workaround for those affected and Administrators can restore the expected behavior by restarting the network Adapters this can be done manually in various ways e.g. with the following command via PowerShell
PS C:\> Restart-NetAdapter *
The problem is that the error reoccurs each time the Windows Server 2025 acting as a domain controller is restarted. Microsoft suggests creating the workaround to restart the network adapters as a scheduled task that restarts the network adapter each time the domain controller is restarted