Cumulative update 11.2505.1001.22 failing validation

Question

Cumulative update 11.2505.1001.22 failing validation with no detail other than these actual failure statements:

Microsoft.Health.FaultType.Vm.BadOperationalStatus

Microsoft.Health.FaultType.Cluster.ValidationReport.Failed

Update 11.2505.1001.19 applied successfully. Our Azure Local hosts and our VMs are under different subscriptions. Could that be the cause?

Where is this actual issue logged? There is zero detail in the Azure Update Manager screen.

Answer 1

Hi Tracy Watson - A
I understand you're encountering a validation failure with Cumulative Update 11.2505.1001.22 on Azure Local with the errors:

Microsoft.Health.FaultType.Vm.BadOperationalStatus

This typically means one or more VMs are in a non-healthy or transitional state — e.g., paused, saved, shutting down, or not responding.

These could include: Checkpoints, Backup snapshots, VMs that are not "running" or "off"

Microsoft.Health.FaultType.Cluster.ValidationReport.Failed

• This comes from Cluster-Aware Updating (CAU) or Update Manager health checks.
• It indicates that the cluster validation did not pass pre-checks required for safe update rollout.
• Azure Update Manager might not have permission to fully orchestrate updates if: Hosts or VMs are in different Azure subscriptions. https://learn.microsoft.com/en-us/azure/update-manager/troubleshoot?tabs=azure-machines#resolution-4 There's incomplete registration or misconfigured ARC resources.
• Since the Update Manager UI is limited, here’s where to dig deeper: On the Cluster Node (Local Logs)
  1. Event Viewer > Applications and Services Logs > Microsoft > Windows > Cluster-Aware Updating > Operational
  2. C:\Windows\Cluster\Reports – Contains Validation Reports and update logs.
     https://learn.microsoft.com/en-us/azure/azure-local/manage/health-service-faults?view=azloc-2504
• In Azure Portal, Navigate to Update Manager > Machines > [Node Name] > Update Run History and try to open JSON-level detail.
• Check that the Azure Stack HCI host cluster is registered properly and the resource bridge is connected.
• Ensure Hybrid registration and Update Manager extension are present and synced.

Hope it helps!

Let me know if you have any further queries!