What is Support Doing to Recover Hyper-V Node from KB5062557?

Hello MrMJFisher**,** I am Henry and I want to share my experience about your issue.

I see that after installing the update KB, the node entered quarantine. Now you'd like to roll back the KB update, so here are the DISM-based procedure you can refer.

Step 1: Isolate the Node

From a working node in the cluster or a management server, run this command in an elevated PowerShell to formally pause the failing node. Replace 'NodeName' with the name of your failing node Suspend-ClusterNode -Name 'NodeName' -Drain

Step 2: The DISM command requires the full package name, not just the KB number. Run this command to get it from the failing node.

Invoke-Command -ComputerName 'NodeName' -ScriptBlock { DISM.exe /Online /Get-Packages | findstr "5062557" }

The command will output the package identity. You must copy the entire package name. It will look similar to this: Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5936.1.7

Step 3: Uninstall the Update Package with DISM

Use the package name you just copied to remove the update.

1. Store the full package name you copied into a variable. Replace the text in the quotes with your actual package name. $PackageName = "Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5936.1.7"
2. Run the remote uninstall command. Invoke-Command -ComputerName 'NodeName' -ScriptBlock { param($Package) DISM.exe /Online /Remove-Package /PackageName:$Package /Quiet /NoRestart } -ArgumentList $PackageName

Step 4: Reboot the Repaired Node: Restart-Computer -ComputerName 'NodeName' -Force

Step 5: After the node has rebooted and is back online, bring it back into active cluster service. Run these commands from a working node.

• Start-ClusterNode -Name 'NodeName' -ClearQuarantine
• Resume-ClusterNode -Name 'NodeName'

Hope this clears things up!