I'm building a lab with Windows Server 2025 and Configuration Manager 2509. WSUS is installed on the primary site server, and the Software Update Point is configured to synchronize directly with Microsoft Update. Synchronization starts but consistently ends with Result: Failed and Error: ImportUpdateError, while UpdateErrors remains empty. The server is running WSUS 10.0.26100.33158, has no proxy configured, and outbound TCP 443 connectivity to sws.update.microsoft.com has been verified. The WSUS SoftwareDistribution.log repeatedly reports "invalid update identity (AtLeastOne Prerequisite) in XML for update" for several different update GUIDs. Has anyone seen this behavior on Windows Server 2025, and is there a known fix or workaround?
2 Answers
A clean rebuild doesn’t necessarily resolve this. One other lab using Server 2025, SQL Server 2022, and Configuration Manager 2509 saw the same failure on every synchronization. In that case, the first sync ran for roughly 15 minutes, then later attempts failed within about 30 seconds on the same update revision: CF56FF39-8BA5-4177-9265-E30D4DD58CF5/100. Removing and recreating WSUS and its database produced the same result, which points more toward an update metadata or compatibility problem than a damaged local database.
WSUS has been deprecated by Microsoft, so it may be worth treating this as a platform compatibility issue rather than continuing to rebuild the server. There doesn’t appear to be a confirmed repair in the discussion. For longer-term patch management, Windows Update for Business, Autopatch, or Intune may be the direction to consider, although that may not replace the Software Update Point requirements in every Configuration Manager design.
I wasn’t aware WSUS had been deprecated. Thanks—that gives me a better direction for evaluating alternatives while I investigate whether this is a Server 2025 metadata issue.