WSUS Sync Failures

Question

A dependency of the update was not found on the server and was not provided by the upstream server.

Answer 1

Thanks, I've been dealing with that problem now too. The error is with the "Windows Insider Dev Channel" product. On all four WSUS servers that I take care of, a synchronization error started to appear and all I had to do was to disable this product.

I would be happy if Microsoft would do something about this.

Answer 2

Have you tried unchecking all of the products, saving, and then checking only 1 product like Windows 10, 1903 and later and then trying to manually sync? We've seen before in the past where it was a product that was causing the sync errors. If it is successful, go in and check a few at a time and sync again manually. Eventually you will either end back up where you were and all syncs are successful, or you will find the product that is causing the sync issue.

Answer 3

@Shayfer A. Mosness
Thanks for your posting on Q&A.

Please help to confirm whether the downstream WSUS is in the Autonomous mode or in the Replica mode. Please help to confirm whether the failed to sync updates are available in the upstream WSUS.
Reference link:
https://learn.microsoft.com/de-de/security-updates/windowsupdateservices/18127467#on-a-downstream-wsus-server-check-that-the-updates-are-available-on-the-upstream-wsus-server

Follow the below steps to confirm whether the failed updates are available on the upstream WSUS:

To troubleshoot this issue, on the downstream server, make a note of the title of the updates for which download failed. These will be visible on the Updates page, and marked with a red X. Then, check if these updates exist on the upstream server (look at the Updates page. If they do not match, do one of the following, depending on which updates you need:

Specify the missing updates on the upstream server, and then synchronize from the update source.

On the downstream server, cancel the updates that are not on the upstream server, if these updates are no longer needed. Then decline the old updates on the downstream server.
If the missing updates (according to the downstream server) are actually available on the upstream server, then the error is transient, meaning the update might have been downloaded to the upstream server after it was requested by the downstream server. This issue will resolve itself the next time the downstream server synchronizes to the upstream server.

Best regards,
Rita

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 4

There is no downstream or upstream servers. It is a single WSUS server that is syncing with Microsoft Updates

Answer 5

We are experiencing this problem as well and a ticket has been opened with Microsoft.

Just adding some detail here in case anyone else is searching for them.

While this is a WSUS problem, it also impacts CM/SMS/SCCM/MECM as well.

WSUS SoftwareDistribution.log messages associated with this problem:

• Bad Update Revision # (with reference Update IDs that do not exist.
• CatalogSyncThreadProcess: report subscription One or more updates failed to import to local database.
• System.Data.SqlClient.SqlException (0x80131904): invalid update identity in XML for update

CM/SMS/SCCM/MECM Microsoft.UpdateServices.Internal.BaseApi.SynchronizationInfo and wsyncmgr.log messages associated with this problem.

• DependencyNotFound, System.Data.SqlClient.SqlException (0x80131904): invalid update identity in XML for update
• ImportUpdateError
• Error Number:50000,State:1,Class:16