Skip to content

Trouble Installing Patch (KB5056579) on Windows EC2 Instance

0

We are running Windows EC2 instances in production. Instance type is m7i.xlarge and base image is Microsoft Windows Server 2025. We have patch manager setup with default baselines for windows. Patch manager approve patches after 7 days of being released and manually install those patches. But we are having trouble installing this particular update: 2025-07 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Microsoft server operating system version 24H2 for x64 (KB5056579) After this update when we reboot instance its health check starts failing (2/3) and I can see this error (attached screenshot). Are we missing anything in our patching operations ? I have following this practice from few months. I have also tried installing same update on m6i.xlarge but encountered same issue.Enter image description here

asked a year ago295 views

2 Answers
5

Considering below:

  1. Block KB5056579 Temporarily Since you're using Patch Manager with default baselines: • Create a custom baseline that explicitly excludes KB5056579 • Use Update Management in Systems Manager to block this patch until it's stable
  2. Test in Isolated Environment Before applying to production EC2s: • Spin up a test EC2 instance with the same image and patch manually • Monitor health checks and logs post-reboot
  3. Check EC2 Health Dependencies After reboot, if EC2 health checks fail: • Verify network drivers, TPM, and EC2 integration services are intact • Check C:\Windows\Logs\CBS\CBS.log and WindowsUpdate.log for patch-related errors
  4. Use DISM to Repair Run this on the EC2 instance before retrying the patch: DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow
EXPERT

answered a year ago

0

Hey,

Hope you're keeping well.

This patch appears to be causing OS-level issues that prevent EC2 from passing status checks after reboot. I’d recommend creating a custom Patch Manager baseline in Systems Manager that excludes KB5056579 and applying it to your production fleet until Microsoft releases a fix. Spin up a non-production Windows Server 2025 instance with the same AMI and instance type, install the update manually, and review C:\Windows\Logs\CBS\CBS.log and C:\Windows\WindowsUpdate.log for errors. If the issue persists, open a case with Microsoft via your AWS Support plan since the underlying patch is vendor-supplied, and keep your AMIs versioned so you can roll back quickly.

Thanks and regards,
Taz

answered 7 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.