This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I tried to upgrade my SBE but failed with below error. Anyone know about this error and how to fix this? Is executing the Invoke-CauRun -ForceRecovery is safe?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 79%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3END%3C/text%3E%3C/svg%3E)
Hello @Handian Sudianto ,
It looks like your SBE upgrade is failing on the Cluster-Aware Updating (CAU) step because CAU detected leftover state from a previous run. That’s exactly what the error message says:
“Cannot complete this operation because leftover state from a previous Updating Run has been detected. Use Invoke-CauRun -ForceRecovery to recover from this state.”
Here’s what you can do:
Inspect the current CAU runs
Import-Module FailoverClusters
Get-CauRun –All
- Look for any runs in “Running” or “Partial” states—those are the leftover ones.
Recover the CAU state
- Once you verify there are no other maintenance tasks in progress, run:
```yaml
Invoke-CauRun –ForceRecovery –ClusterName <YourClusterName>
```
- This will clean up the stale run state and bring CAU back to a healthy baseline.
Re-run the SBE upgrade
- Go back into the Azure portal or rerun your solution upgrade PowerShell, and the SBE CAU steps should now progress past the block.
Is it safe? Yes, ForceRecovery is a supported way to clear out stuck CAU state—just make sure:
• No other CAU jobs or failover operations are running • Your cluster is healthy and all nodes are up • You collect logs if it fails again (SBE logs under C:\ProgramData\AzureStackHCI\Update\SBE-logs, and the cluster event log)
If you still hit errors on the vendor plugin scan or run step, you might need to:
• Check your hardware vendor’s SBE plugin version and prerequisites (for example, the Dell TSG doc if this is a ThinkAgile system) • Engage the vendor to validate that their plugin isn’t dropping files or leaving partial state
Hope that helps! Let me know if you run into any other errors after recovery.
Reference list • Troubleshoot solution updates for Azure Local: https://docs.microsoft.com/azure/azure-local/update/update-troubleshooting-23h2 • Solution Builder Extension states and how to check/install: https://docs.microsoft.com/azure/azure-local/update/solution-builder-extension • Troubleshoot Azure Local upgrade (CAU guidance, logs): https://docs.microsoft.com/azure/azure-local/upgrade/troubleshoot-upgrade-to-23h2 • TSG SBE | 23H2 | Unable to install SBE update from Dell Plugin: https://supportability.visualstudio.com/WindowsCloud/_wiki/wikis/WindowsCloud.wiki/1542202/Components/Hybrid%20Services/23H2%20deployment%20and%20management/Updates/TSG%20SBE%20%7C%2023H2%20%7C%20Unable%20to%20install%20SBE%20update%20from%20Dell%20Plugin
Was this helpful?
Now i found that VM in one node is stucking either in restoring or starting.
I try create a new vm then power on the VM but stuck in starting state.
Issuing the Invoke-CauRun -ForceRecovery beside this command is safe, is there any downtime? Will the node rebooted?
Also can i know in this state the SBE already updated in all nodes?