Server 2025 updates fail with Error encountered and no error code

Hi Chris,

This seems not to be a local DNS or firewall issue but rather a routing problem between your ISP and Microsoft’s edge network. Windows Server Update Services and the Microsoft Store rely on endpoints under *.microsoft.com, so if that traffic is dropped you’ll see both update failures and Store connectivity issues. Let's see if name resolution is working by running nslookup microsoft.com and checking that you get valid IPs. If DNS is fine, the issue is upstream routin - your packets are reaching Microsoft’s carrier edge but not being returned. This is not something you can fix locally, it requires either your ISP to correct their peering with Microsoft or Microsoft to resolve a routing fault on their side. In the meantime, you can test connectivity to update endpoints like windowsupdate.microsoft.com or update.microsoft.com to confirm the scope. If all Microsoft-owned ranges under AS8075 are unreachable, you’ll need to escalate to your ISP with the trace results and have them open a ticket with Microsoft’s NOC. Locally, there’s no supported workaround other than waiting for the upstream routing to be corrected.