Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article explains how to discover and import solution update packages for Azure Local (formerly Azure Stack HCI) deployed in sites with limited bandwidth connections to Azure. You can download Azure Local solution update as a static payload, then copy or transfer it to multiple instances, and import it using PowerShell. Do these actions before you start an update to reduce the amount of data downloaded during the update.
The static payload for a solution update includes the OS security update, extensions, and core agents, which install during the update process. The update process automatically downloads updated container images required for the Azure Arc resource bridge component and Azure Kubernetes Service on Azure Local. These images aren't included in the static payload.
Prerequisites
Make sure you run Azure Local 2411.3 or later to use this feature.
Review About updates for Azure Local to learn more about the update process.
Review Azure Local release information to check which paths are supported.
Solution update bundle
The CombinedSolutionBundle is a zip file that contains the update package for the Azure Stack HCI OS, core agents and services, and the solution extension. The CombinedSolutionBundle is named CombinedSolutionBundle.<build number>.zip, where <build number> is the build number for the release. Use the SHA256 hash to check the integrity of your download.
The following tables list the CombinedSolutionBundle versions and associated SHA256 hashes for existing deployments of Azure Local.
- For 25398.xxxx builds, use the CombinedSolutionBundle to update the OS and solution components for Azure Local.
- For 26100.xxxx builds, use the CombinedSolutionBundle to install a specific Azure Local version.
For more information on the release cadence, see Azure Local release information.
| OS Build | Download URI | SHA256 |
|---|---|---|
| 26100.32370 | 12.2602.1002.501 Availability date: 2026-03-02 |
B7109C8067F7C4D99D1B7A956FC911525384B211BB34BAF13BC68E229BD6F628 |
| 26100.32230 | 12.2601.1002.503 Availability date: 2026-02-02 |
68848F4082C3F1B75D303476193E81A4593316DAABB8C45380AFEFAD94E90E78 |
| 26100.7462 | 12.2512.1002.16 Availability date: 2025-12-16 |
EE8BC57EA3B59B1761B07F99B559F5E6280CDE21C0ECDC939EAC6BC7B8D2F4E6 |
| 26100.7171 | 12.2511.1002.502 Availability date: 2025-12-03 |
497ABE8459F86415B91A7F75741B37975B15A19BFFFEDB1A45F171F49B9CB1F6 |
| 26100.6899 | 12.2510.1002.531 Availability date: 2026-02-17 |
116AEFD4E0513C6CB78A8A67C45FB0F4639067D20801F319F5C1920A981DA0A9 |
| 26100.6584 | 12.2509.1001.22 Availability date: 2025-09-22 |
15771552A97785B7EE291587FE62EE678EDE850E2250A5407EE6738AFEF729B6 |
| 26100.4946 | 12.2508.1001.52 Availability date: 2025-08-29 |
410723EAD2177247932B10AD79978F2E4D8049FBFF70E8F9F94943384B59BB80 |
| 26100.4652 | 12.2507.1001.10 Availability date: 2025-07-25 |
8FAC8A7F52C570682407573F7AAAB79BDBA62299C9F50C3497FD0A10FBF73105 |
| 26100.4349 | 12.2506.1001.29 Availability date: 2025-07-02 |
C8227DF98F97FDE807A2B711206A1FE23531340DC717F89CDA7A324BA0B316C7 |
| 26100.4061 | 12.2505.1001.23 Availability date: 2025-05-28 |
29E5F6732D9B1BD4E0C2667F6FB1D7F43ADF78B4AEA8E34486C7F03DD46D155C |
Note
You might need to wait up to 24 hours after the release for the latest version of the CombinedSolutionBundle and its SHA256 hash to be available.
Step 1: Download Solution update bundle
Download the bundle and note the SHA256 hash from the Solution update bundle table. Run this command:
# Download the CombinedSolutionBundle Invoke-WebRequest -Uri "<download URI>" -OutFile "C:\ClusterStorage\Infrastructure_1\Shares\SU1_Infrastructure_1\import\CombinedSolutionBundle.<build number>.zip"Check the SHA256 hash of the downloaded CombinedSolutionBundle. Run this command:
# Check the SHA256 hash of the downloaded CombinedSolutionBundle Get-FileHash -Path "<path to CombinedSolutionBundle.zip>"
Step 2: Import the Solution update bundle
Create a folder for the update service to discover in the infrastructure volume of your system. Run this command:
# Create a folder for the update service to discover New-Item C:\ClusterStorage\Infrastructure_1\Shares\SU1_Infrastructure_1\import -ItemType DirectoryCopy the CombinedSolutionBundle you downloaded to the folder you created.
Extract the contents of the CombinedSolutionBundle to the Solution subfolder. Run this command:
# Extract the contents of the CombinedSolutionBundle to the Solution subfolder Expand-Archive -Path C:\ClusterStorage\Infrastructure_1\Shares\SU1_Infrastructure_1\import\CombinedSolutionBundle.<build number>.zip -DestinationPath C:\ClusterStorage\Infrastructure_1\Shares\SU1_Infrastructure_1\import\SolutionImport the package into the update service. Run this command:
# Import the module Add-SolutionUpdate -SourceFolder C:\ClusterStorage\Infrastructure_1\Shares\SU1_Infrastructure_1\import\SolutionCheck that the update service discovers the update package and that it's available to start preparation and installation. To discover the updates, run the
Get-SolutionUpdatecommand. The update service discovers updates asynchronously, so you might need to run theGet-SolutionUpdatecommand more than once.If the update returns a state of
AdditionalContentRequired, follow the instructions in Update Azure Local via PowerShell to import the required Solution Builder Extension (SBE) updates. If it doesn't, continue to the next step.Start the update. For more information, see Update Azure Local via PowerShell.
Next steps
Learn more about Understanding update phases
Review Troubleshooting updates
This feature is available in Azure Local 2411.3 and later.