2025.03 Feature Update

Perform the following steps to unblock the stuck 2025.03 solution update on Azure Local and gather data for support.

1. Check where the update is stuck
   1. In the Azure portal, open the Azure Local resource.
   2. Go to the Updates blade and open the failed or in-progress 2025.03 update run.
   3. Select View details on the failing or long-running step and note:
      • Step name
      • Machine/node where it is stuck
      • Failure message or whether it is just running for a long time
2. Try a controlled retry of the update
   • If the portal shows the update as failed or retryable:
     1. In the update run view, select Try again.
     2. Let the retry run and monitor step progress.
   • If using PowerShell instead of the portal, resume the specific version (replace the version string with the 2025.03 version actually shown in your environment):

          Get-SolutionUpdate | ? Version -eq "10.2302.0.31" | Start-SolutionUpdate
     

   • If the previous run failed only due to readiness checks in Warning state and you have validated that the warnings are acceptable, resume with warnings ignored:

          Get-SolutionUpdate | ? Version -eq "10.2302.0.31" | Start-SolutionUpdate -IgnoreWarnings
     

3. Verify readiness and system health
   • Ensure that system health and update readiness checks are passing or only show acceptable warnings before retrying:
     • Critical checks must be resolved before proceeding.
     • Warnings can be bypassed with -IgnoreWarnings but should be reviewed carefully.
   • If the issue was caused by power, hardware, or similar interruptions:
     1. Restore power and hardware health.
     2. Run a system health check.
     3. Resume the update as above.
4. Run Azure Local Support Diagnostic Tool
   • On a node, open an elevated PowerShell session and run a diagnostic sweep across the cluster to detect known issues that can block or slow updates:

          Invoke-AzsSupportInsight -ComputerName (Get-ClusterNode).Name
     

   • Review the generated HTML report and data bundle for any update-related or node-health issues and remediate them.
5. Check for known Azure Local issues that can affect updates
   • Confirm whether any of the known issues apply to the environment, for example:
     • Windows Defender Attack Surface Reduction rule Block Process Creations originating from PSExec & WMI commands set to Block, which causes Azure Local Solution Update to fail. If this matches the environment, follow the Defender-related troubleshooting guide referenced under Security known issues.
     • Add/Repair server image-version mismatches or recalled images if add/repair operations were involved during the update.
   • If any known issue matches the symptoms, apply the documented workaround, then retry the update.
6. Collect logs for support
   • From the Azure portal, in the update run details, use How to collect logs to download the update diagnostic logs.
   • Optionally, use the Support Diagnostic Tool to create a support data bundle for updates:

          New-AzsSupportDataBundle –Component <Component>
     

     (Use CTRL+SPACE after -Component to list available components.)
7. Open a Microsoft support ticket
   • If the update remains stuck after retries and remediation:
     1. In the update run details, select Open a support ticket.
     2. Attach the collected logs and any Invoke-AzsSupportInsight output.
     3. Include the failing step name, node, and any error messages from the update details.

These steps provide an end-to-end path: identify the failing step, retry safely, validate readiness and node health, account for known issues, gather diagnostics, and escalate to Microsoft Support with the right data if the update still does not progress.

References:

• Troubleshoot solution updates for Azure Local
• Known issues in Azure Local
• Use the Support Diagnostic Tool to troubleshoot Azure Local issues