Windows Admin Center 2410 not updating Server 2025

When the Updates tool in WAC spins indefinitely but updates work normally inside the server, it usually points to a permissions mismatch or a missing WMI/DCOM capability for the update provider.

Key factors to check:

• The account used in WAC must have local admin rights and remote WMI access. Even if you can log in and run tools, the Updates extension calls additional APIs that require explicit permissions.
  • Ensure that the Windows Update service and related WMI providers (Microsoft.Update.Session) are running and reachable.
  • If Group Policy points the server to WSUS, WAC must be able to read the server’s WSUS configuration via WMI. A corrupted WSUS policy often triggers the “Access Denied” and “null-valued expression” errors.
  • Temporarily removing WSUS policy on one server and forcing a GPUpdate is a good way to confirm whether WSUS is the blocker.

Since you confirmed RDP, registry and PowerShell work but the update UI does not, this is nearly always a remote provider permission issue and not a server malfunction. Resetting WMI or re-registering update DLLs can also help, but checking WSUS policy is the fastest first step.