WSUS initial configuration fails with SqlException 50000 invalid update identity

재웅 최 5 Reputation points
2026-06-15T08:40:15.2533333+00:00

Subject: WSUS initial configuration fails with SqlException 50000 invalid update identity

We are experiencing a WSUS initial configuration/synchronization issue on Windows Server 2022 Standard, version 21H2, OS build 20348.5256.

During the WSUS Configuration Wizard at the “Connect to upstream server / Download update information from Microsoft Update” step, SoftwareDistribution.log repeatedly shows the following errors:

SqlException occurred. Number 50000 and message invalid update identity in XML for update {GUID}

SqlException occurred. Number 50000 and message invalid update identity (AtLeastOne Prerequisite) in XML for update {GUID}

The product list is also incomplete or abnormal. “Windows 11” is not listed as a normal product, while items such as “Windows 11 Dynamic Update” and “Windows 11 GDR-DU” appear.

Actions already taken:

  • Reinstalled WSUS role.
  • Recreated SUSDB/WID.
  • Completed wsusutil postinstall successfully.
  • Updated the WSUS server to Windows Server 2022 build 20348.5256.
  • Confirmed Microsoft Update connectivity is available.
  • The issue still occurs during the initial WSUS configuration wizard.

Attached logs:

  • SoftwareDistribution.log

WSUS_MS_Support_Important_Extract.txt

Please confirm whether this is a Microsoft Update metadata/catalog issue affecting WSUS synchronization, and advise if there is a workaround or server-side fix.

Windows for business | Windows Server | Devices and deployment | Install Windows updates, features, or roles

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Brian Huynh 3,815 Reputation points Microsoft External Staff
    2026-06-16T02:32:49.2133333+00:00

    Hello 재웅 최, thank you for posting in the Microsoft Q&A community.

    The error message invalid update identity (AtLeastOne Prerequisite) in XML for update means that WSUS is attempting to parse update metadata downloaded from the Microsoft Update servers and insert it into the local SUSDB. However, the SQL stored procedure rejects it due to a malformed prerequisite schema. Because you have already completely recreated the SUSDB and WID database to ensure a clean start, this indicates a server-side catalog metadata issue currently present on Microsoft's end. When the WSUS Configuration Wizard encounters this XML block, it hard-fails and halts the setup process.

    To initialize your server, the most effective solution is to skip the GUI Configuration Wizard, which gets permanently stuck on these exceptions, and initiate the synchronization via PowerShell. PowerShell handles catalog exceptions and will skip the problematic metadata block to finish building your product tree.

    Please close the WSUS Configuration Wizard, then open PowerShell and run the following commands to start the sync:

    $wsus = Get-WsusServer
$wsus.GetSubscription().StartSynchronization()

    You can monitor the progress directly in the WSUS Console under the Synchronizations node, or by running ($wsus.GetSubscription()).GetSynchronizationProgress()

    If the initial sync process still hangs or fails, you can aggressively clean up any orphaned or corrupted metadata blocks leftover in the database before trying again. Run the following commands to perform a safe cleanup and restart the core services:

    Invoke-WsusServerCleanup -CleanupObsoleteUpdates -CleanupUnneededUpdateFiles -CompressUpdates -DeclineExpiredUpdates -DeclineSupersededUpdates

    net stop wsusservice
net start wsusservice
iisreset

    I will need some more data to isolate the failing update block. Please provide the output of your recent synchronization history by running this command:

    $wsus.GetSubscription().GetSynchronizationHistory() | Select-Object -First 5

    Additionally, please check the Event Viewer under Windows Logs > Application for any Event ID 10032 or Event ID 364 from the source Windows Server Update Services. Sharing those details will help us identify the specific update GUID causing the block.

    Official Microsoft Documentation references: https://learn.microsoft.com/en-us/powershell/module/updateservices/invoke-wsusservercleanup

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.