WAC 2410 not showing updates on Windows Server 2025.

Windows Admin Center 2410 Cannot Display Updates on Windows Server 2025: Cause, Symptoms, and Workarounds

by

📌 Introduction

Many administrators deploying Windows Server 2025 have reported a new issue where Windows Admin Center (WAC) 2410 fails to display update information for Server 2025 hosts. While WAC continues to manage Windows Server 2012–2022 normally, attempting to open the Updates tool on Server 2025 often results in:

  • an infinite loading spinner,
  • update history errors, or
  • null-value script exceptions.

This article summarizes what is currently known, what the community has verified, the likely technical cause, and the best temporary workarounds until Microsoft releases an official fix.

This guide is intended for systems administrators, cloud engineers, and IT professionals evaluating or managing mixed-version Windows Server environments.

🧭 Scope / Affected Environment

Impacted

(confirmed in community reports)

  • Windows Admin Center 2410 (Desktop or Gateway mode)
  • Windows Server 2025 (observed in at least one environment)
  • WAC Updates extension

Not impacted

(based on available reports)

  • Windows Server 2012 / 2016 / 2019 / 2022
  • Other WAC tools such as:
    • PowerShell
    • Event Viewer
    • Firewall
    • Registry
    • Roles & Features
    • Certificates
    • Remote Desktop

🚨 The Issue

When connecting to a Windows Server 2025 machine and opening Updates, one or more of the following occurs:

  • The update status page spins indefinitely
  • No update categories or history appear
  • Update history shows errors
  • Nothing loads even after several minutes
  • All other tools work normally except Updates

❗ Symptoms and Error Messages

Administrators report the following errors in WAC when selecting:

Updates → Update History

We couldn’t check update history.
RemoteException: Access is denied. (Exception from HRESULT: 0x80070005)
RemoteException: The property ‘ServerSelection’ cannot be found on this object.
RemoteException: You cannot call a method on a null-valued expression.

These errors suggest:

  • WAC is calling properties or objects that do not exist on Server 2025
  • COM/WMI calls are returning null
  • Legacy update properties such as ServerSelection are unsupported
  • The connection itself works — only the Windows Update API call fails

Importantly, this is not caused by credentials, permissions, firewall, or network issues.

🧩 Likely Root Cause (Current Understanding)

Currently strongly suggest that Windows Server 2025 uses an updated or modernized Windows Update architecture. As a result:

  • The WAC 2410 Updates extension still calls older Windows Update COM/WMI interfaces
  • Some of those legacy interfaces (e.g., Microsoft.Update.Session, IUpdateSearcher) appear unsupported or behave differently on Server 2025
  • When WAC attempts to access properties like ServerSelection, the call fails
  • WAC receives null, then throws:
    “You cannot call a method on a null-valued expression”

⚠️ Important Note

Microsoft has not yet publicly documented which exact Windows Update APIs changed in Server 2025, nor have they officially confirmed that legacy COM/WMI interfaces are deprecated.

Therefore, the above represents the most plausible explanation based on community evidence, not an official Microsoft engineering statement.

🔍 Technical Breakdown

Here is what appears to happen internally:

  1. WAC 2410 initiates a legacy Windows Update COM/WMI call
  2. Windows Server 2025 does not support the requested property/object
  3. The call returns null
  4. WAC scripts attempt to read properties from this null object
  5. The page fails, resulting in:
    • infinite spinner
    • property-not-found errors
    • Access Denied (HRESULT: 0x80070005)

This is a compatibility issue, not a configuration problem.

⚠️ Impact on Administration

The following WAC features fail on Server 2025:

  • Checking for updates
  • Retrieving update categories
  • Viewing installed updates
  • Viewing update history
  • Using update workflows that depend on WAC’s update engine

Other remote management tasks in WAC work normally, including:

  • Remote PowerShell
  • Event Viewer
  • Firewall
  • Roles & Features
  • Services
  • Certificates
  • File management
  • Registry editing

Only the Updates extension is affected.

🛠️ Workarounds (Until Microsoft Releases a Fix)

✔ 1. Manage Updates Locally on Server 2025

Use:

  • Settings → Windows Update
  • Or sconfig (for Core installations)

✔ 2. Use PowerShell (Recommended)

Install PSWindowsUpdate:

Install-Module PSWindowsUpdate
Import-Module PSWindowsUpdate

Check updates:

Get-WindowsUpdate

Install updates:

Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -AutoReboot

✔ 3. Use WSUS or Intune

If your environment uses WSUS/Intune:

  • Server 2025 continues to report normally
  • Updates install as scheduled
  • No compatibility issues have been reported with these platforms

✔ 4. Avoid Using WAC Updates on Server 2025 for Now

Continue using WAC 2410 safely for:

  • RDP
  • Certificates
  • PowerShell
  • Services
  • Local users
  • Event Viewer
  • Registry and file tools

Only the Updates tool is affected.

🟦 Microsoft Status / Expected Fix

As of November 2025:

  • Microsoft has not published an official KB or engineering statement confirming this issue
  • No fix version (such as WAC 2411 or later) has been publicly announced
  • The issue is not yet listed in the official Windows Admin Center known issues or release notes

🧾 Best Practices for Administrators

  • Continue using WAC normally for Server 2012–2022
  • Avoid using WAC 2410 to manage updates on Server 2025
  • Standardize update operations using:
    • PowerShell
    • WSUS
    • Intune
  • Script updates for Server 2025 hosts if managing at scale
  • Check WAC release notes monthly for compatibility improvements

Leave a Comment