Forum Discussion
Windows Admin Center 2410 not updating Server 2025
Hi, I have 3 new 2025 servers all updated and on the domain. Windows Admin center is working fine with all other servers (2012, 2016, 2019, and 2022). For these 3 new servers, I can connect and login through Adm Center and when I choose the "updates" tab the circle in the middle of the screen spins indefinitely.
It never even shows if updates are available or not, it just spins. If I log onto the servers locally, I can see and install updates manually. But when I go back and connect through ADM Center, I just get the spinning circle. I currently only have 3 2025 servers, so for me it appears to be an issue with how they talk to ADM Center concerning updates. (and this makes me hesitate to update other servers)
I've tried RDP, registry, Powershell, etc (all through ADM Center). It ALL works, but updates never do. Additionally the 2025 servers are able to communicate just fine to report update status to our WSUS server.
If I click the "update history" tab on the updates page in Admin Center, I then see an error, but not sure what would be denying anything, when the connection already seems to be made: "Message
We couldn't check update history. Error: (1) RemoteException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (2) RemoteException: The property 'ServerSelection' cannot be found on this object. Verify that the property exists and can be set. (3) RemoteException: You cannot call a method on a null-valued expression. (4) RemoteException: You cannot call a method on a null-valued expression."
I tried to temporarily disable the firewall with no change in behavior. The account I'm using is a domain admin account and also added to the local admin group for testing.
2 Replies
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.
- 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.
I'm having the same issue on one of my Windows 2025 servers with WAC.
