Listen to this Post
Introduction:
Microsoft recently resolved a critical issue in Windows Server 2019 that caused cluster service disruptions and VM instability. The August 2025 patch (KB5063877) addresses these problems, but admins must first install a prerequisite Servicing Stack Update (KB5005112). This article provides actionable steps to secure affected systems and prevent downtime.
Learning Objectives:
- Understand the impact of the Windows Server 2019 cluster and VM instability bug.
- Learn how to apply the necessary patches (KB5005112 and KB5063877) correctly.
- Discover best practices for testing patches in staging environments before production deployment.
1. Check If Your System Is Affected
Verified PowerShell Command:
Get-WindowsUpdateLog | Select-String -Pattern "KB5062557"
Step-by-Step Guide:
1. Open PowerShell as Administrator.
- Run the command above to check if the problematic July 2025 patch (KB5062557) is installed.
3. If found, proceed with patch remediation.
2. Install the Required Servicing Stack Update (KB5005112)
Manual Download & Install via Microsoft Update Catalog:
- Download KB5005112 from Microsoft Update Catalog.
2. Run the installer with elevated privileges:
wusa.exe "C:\Path\to\KB5005112.msu" /quiet /norestart
3. Reboot the server if prompted.
3. Apply the August 2025 Patch (KB5063877)
Windows Update Command:
Install-Module -Name PSWindowsUpdate -Force Import-Module PSWindowsUpdate Get-WindowsUpdate -KBArticleID KB5063877 -Install -AcceptAll -AutoReboot
Step-by-Step Guide:
1. Ensure KB5005112 is installed first.
- Use the above PowerShell command to install KB5063877 automatically.
- Alternatively, deploy via WSUS or manually from the Microsoft Catalog.
4. Verify Patch Installation Success
Windows Event Log Check:
Get-WinEvent -LogName System | Where-Object {$_.Id -eq 7031} | Select-Object -First 10
What This Does:
- Checks for Event ID 7031 (unexpected VM restarts).
- If no recent errors appear, the patch was successful.
5. Workaround for Unpatchable Systems (Temporary Fix)
Disable BitLocker on CSV Volumes (If Possible):
Disable-BitLocker -MountPoint "C:\ClusterStorage\Volume1"
Note: This is a temporary mitigation—apply the official patch as soon as possible.
6. Best Practices for Future Patch Management
Automate Patch Testing with PowerShell:
New-PSSession -ComputerName "StagingServer" -ScriptBlock { Install-WindowsUpdate -KBArticleID "KBXXXXXXX" -AcceptAll }
Why This Matters:
- Test patches in a staging environment before production rollout.
- Avoid unexpected downtime due to untested updates.
What Undercode Say:
- Key Takeaway 1: Always verify prerequisite patches (like KB5005112) before applying critical fixes.
- Key Takeaway 2: Automate patch validation in staging environments to prevent production failures.
Analysis:
This incident highlights the risks of untested patches in clustered environments. Microsoft’s dependency on Servicing Stack Updates (SSUs) means admins must follow strict update sequences. Organizations using BitLocker with CSV volumes should prioritize this patch to avoid VM instability.
Prediction:
Future Windows Server updates may introduce more dependency checks to prevent similar issues. Expect Microsoft to enhance patch validation tools, reducing manual admin intervention. Admins should adopt automated patch management solutions to stay ahead of critical vulnerabilities.
By following these steps, sysadmins can secure their Windows Server 2019 clusters and prevent disruptive VM crashes. Stay vigilant on Patch Tuesday updates to avoid unplanned outages.
🔗 Relevant Links:
WindowsServer Microsoft PatchTuesday SysAdmin Cybersecurity
🎯Let’s Practice For Free:
IT/Security Reporter URL:
Reported By: Phuong Nguyen – Hackers Feeds
Extra Hub: Undercode MoN
Basic Verification: Pass ✅
