Why does Microsort Update Catalog fail to include superseded data for old .NET updates

Wallwork, Nathan 0 Reputation points
2025-08-28T15:11:47.1733333+00:00

Ivanti Security Controls shows missing updates, but the updates won't install because they are not applicable. These are all old cumulative updates for .NET, on systems where more recent updates have been applied.

The Microsoft Update Catalog incorrectly shows 'n/a' for superseded data ("replaced by" & "replaces") for old .NET updates.

For instance:

2022-02 Update for .NET Framework 3.5 and 4.8 for Windows Server 2019 for x64 (KB5011257)

2022-09 Cumulative Update for .NET Framework 3.5 and 4.7.2 for Windows Server 2019 for x64 (KB5016713)

2023-06 Update for .NET Framework 3.5 and 4.8 for Windows Server 2019 for x64 (KB5028581)

2023-06 Update for .NET Framework 3.5 for Windows Server 2019 for x64 (KB5029009)

2024-01 Cumulative Update for .NET Framework 3.5 and 4.7.2 for Windows Server 2019 for x64 (KB5033904)

2024-01 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows Server 2019 for x64 (KB5033911)

2024-02 Cumulative Update for .NET Framework 3.5 and 4.7.2 for Windows Server 2019 for x64 (KB5034619)

2024-02 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows Server 2019 for x64 (KB5034624)

There's a discrepancy between the update and the Microsoft Update Catalog. The update can tell that it is not applicable (because a more recent update has already been applied), but the Microsoft Update Catalog shows that the patch has NOT been superseded.

What would it take to get Microsoft to update the Microsoft Update Catalog to include the correct superseded data for old updates?

Alternatively, what is Microsoft's recommended workaround for this problem?


To clarify, this is NOT a local problem. (I suppose I could uninstall recent updates until I'm able to install old updates, then reinstall the recent updates, but that cannot be the right solution.)

The problem exists in Microsoft's Update Catalog, hosted on Microsoft's servers. It incorrectly shows "n/a" for old updates when it should show superseded info.

The problem can be observed by searching https://www.catalog.update.microsoft.com/ for the listed KBs, checking the "package details" tab, and seeing that Microsoft lists "n/a" for old cumulative updates.

The whole point of cumulative updates is that they will be superseded by the next cumulative update. Failing to add superseded data to the Microsoft Update Catalog causes adverse impacts for tools that use that data. For instance, Ivanti Security Controls shows updates as missing because it doesn't know that the updates have been superseded. When we try to install the updates, they fail, because the update can tell that it is no longer applicable. There's a discrepancy between the update (which can tell it is no longer applicable) and the Microsoft Update Catalog (which fails to show the update has been superseded).

Microsoft should update the Microsoft Update Catalog to include superseded data for old updates.

Windows for business | Windows Server | User experience | Other
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Domic Vo 1,015 Reputation points Independent Advisor
    2025-08-28T18:23:20.81+00:00

    Dear Wallwork, Nathan,

    We understand your concern: Ivanti is reporting missing .NET updates that are not applicable to your systems, as newer cumulative updates have already been installed. However, WSUS is not accurately reflecting supersedence relationships for these older updates—showing “n/a” for both “replaced by” and “replaces” fields.

    This behavior can occur when metadata for certain updates is incomplete or not refreshed correctly in the WSUS catalog. Supersedence data is provided by Microsoft Update Services and is expected to reflect accurate relationships between cumulative updates. When this data is missing or outdated, it can lead to false positives in third-party tools like Ivanti.

    I recommend:

    Run WSUS Cleanup Tasks: Use the Server Cleanup Wizard to remove obsolete and superseded updates. This may help refresh metadata and reduce clutter.

    Decline Non-Applicable Updates: Manually decline updates that are not applicable due to newer cumulative patches already being installed.

    Review Update Metadata: You can cross-reference update supersedence using the Microsoft Update Catalog to verify which KBs have been replaced.

    Provide Feedback to Microsoft: If you believe the WSUS catalog is missing critical supersedence data, you can submit feedback via the Microsoft Q&A platform or through your support channel. This helps our product teams prioritize catalog improvements.

    I hope this helps. Just kindly tick Accept Answer that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    Best regards,

    Domic Vo


Your answer

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