Dear Adeel Mohammed,
The issue you are seeing with KB5121645 for .NET Framework on Windows Server 2019 x64 is not a local corruption problem but rather a catalog and distribution gap. The cumulative update KB5120238 installs fine because it is part of the monthly rollup, but the .NET Framework CU is published separately and requires a distinct installer package. If the Microsoft Update Catalog does not list a downloadable file for KB5121645, it usually means the package has not yet been published or has been temporarily pulled. That explains why “check for updates” also does not surface it, even after resetting SoftwareDistribution and repairing the component store.
The correct approach is to verify the official Microsoft Update Catalog again for the specific KB number and product (Windows Server 2019 x64, .NET Framework 4.8 or 3.5 depending on what is installed). If the entry is missing, there is no supported manual installer available until Microsoft republishes the package. In this case, the only reliable path is to wait for Microsoft to release the standalone .NET CU or bundle it into the next monthly rollup. Attempting to force install from another OS build or extracting files from a different KB is not supported and can break servicing.
If my answer is useful for you, please hit Accept the answer to support me.
Thank you,
HL.