.NET Framework Patching Failing

Wajd Mariam 0 Reputation points
2025-06-12T19:48:39.9733333+00:00

Hello,

I am having a problem with installing "Security and Quality Rollup for .NET Framework 3.5, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows Server 2012 R2 for x64 (KB5050185)" patch. I have tried manual patching and it failed as well.
The CBS log files did not give any useful information about the root cause.

Any recommendations on how to approach this issue? Anything specific I should look for?

Thanks a lot for the help!

Windows Server 2012
Windows Server 2012
A Microsoft server operating system that supports enterprise-level management, data storage, applications, and communications.
1,662 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Mark Dicks 540 Reputation points
    2025-06-13T10:49:03.9966667+00:00

    Hope you doing well Wajd Mariam. A few things you can try:

    Check Prerequisites and Environment

    • .NET Framework Version: Make sure the exact version(s) required by the patch are installed and correctly registered.
    • Windows Update Service: Ensure that the Windows Update service and its dependencies are running properly.
    • Disk Space: Confirm you have enough disk space on the system drive.

    Run the System Update Readiness Tool (CheckSUR)

    On Windows Server 2012 R2, run the System Update Readiness Tool or use the DISM tool to scan and fix component store corruption:

    DISM /Online /Cleanup-Image /CheckHealth
    DISM /Online /Cleanup-Image /ScanHealth
    DISM /Online /Cleanup-Image /RestoreHealth
    

    This can repair corrupted files that might be blocking the update.

    Manually Reset Windows Update Components

    Sometimes the Windows Update agent gets stuck or corrupted:

    • Stop services: wuauserv, cryptSvc, bits, msiserver
    • Rename or delete these folders:
      • %windir%\SoftwareDistribution
      • %windir%\System32\catroot2
    • Restart the services and try the patch again.

    Since CBS logs didn’t help, check:

    • C:\Windows\Logs\DISM\dism.log
    • C:\Windows\WindowsUpdate.log (use Get-WindowsUpdateLog cmdlet to generate readable logs on Server 2012 R2)

    Just check if any of those solve your issue, or if you find additional messages. There are a few other things to try if none of the above work, or if you've already tried them.

    0 comments No comments

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.