Third-party software updates that have content published to the local Windows Server Update Services (WSUS) server may fail to download in the Configuration Manager Console.
This occurs under the following circumstances:
1. The site is installed using Configuration Manager current branch, version 1806 or later.
2. A third-party updates catalog is imported and published using the third-party software updates feature.
3. An update from the catalog has had corresponding content published through the console.
4. After content is published, a metadata-only revision for the same update is released in an updated catalog from the catalog provider and synchronized.
Once these steps occur, third-party software updates that were revised may fail to download from the local SUP.
Note This issue does not occur when updates are imported and published using System Center Updates Publisher (SCUP).
A preventative fix for this issue is planned for the next release of Microsoft Endpoint Configuration Manager, current branch. Additionally, the following preventative update is available for customers using Microsoft Endpoint Configuration Manager current branch, version 1910.
KB 4552430 Third-party update category synchronization resets to default in Configuration Manager
Third-party catalog providers can issue a new update to replace, rather than revise, existing updates when making metadata-only changes which will avoid this issue entirely.
Customers can also use SCUP to publish third-party update revisions until such time as a fix is available in a new release of Configuration Manager.
Updates that are in this state may need to be removed from the top-level Software Update Point (SUP) using the WSUS PowerShell cmdlets or SDK to allow them to be resynchronized.