Hi,
What you're seeing with Windows Server 2022 and 2025 is a known behavior in some environments: .NET Framework cumulative updates sometimes don’t install during the same scheduled cycle as the main server updates, even though they’ve been downloaded. It’s understandable this can be frustrating, especially when everything works smoothly on Server 2016 and 2019.
This usually comes down to how newer versions handle update sequencing and prioritization. While server updates may trigger a reboot, .NET updates might wait for a separate cycle unless manually installed or triggered differently. Using tools like WSUS or Windows Update for Business can sometimes help streamline this, and reviewing your GPO settings to ensure .NET updates aren’t being deferred is a good next step.
If you'd like help reviewing your setup or logs, I’m happy to assist further.
If my answer is useful for you, please vote for it.
Best regards,
Quinnie Quoc.