Azure Local: Hardware Update Stopped Due to NIC Driver/Firmware Mismatch — Guidance Needed

Hi Alex,

First, I want to thank you for your comments!

I have opened tickets to Microsoft and HPE but I'm in a loop with the support (one blaming the other :) ), so I really appreciate your help on this!

You can find the output of the commands you proposed together with more info:

PS C:\Users> Get-SolutionUpdateEnvironment | Format-List *
ResourceId        : redmond
SbeFamily         : ProLiant-Standard
HardwareModel     : HPE ProLiant Compute DL360 Gen12
LastChecked       : 10/26/2026 9:36:05 AM
PackageVersions   : {Solution: 12.2609.1003.7 - last updated on: 09/15/2026 20:45:11 , Services: 10.2609.0.6, Platform: 12.2609.0.3009, SBE: 5.0.2604.21 - last updated on: 08/07/2026 14:37:46 }
CurrentVersion    : 12.2609.1003.7
CurrentSbeVersion : 5.0.2604.21
LastUpdated       : 9/15/2026 8:45:11 PM
State             : UpdateFailed
HealthState       : Failure
HealthCheckResult : {Cluster-Aware Updating Health Check Rule 10, Storage Subsystem Summary, AzureLocal_Network_Test_NetworkAdapter_DriverConsistency,
                    AzureLocal_Network_Test_NetworkAdapter_DriverConsistency...}
HealthCheckDate   : 10/26/2026 7:04:43 AM
AdditionalData    :

PS C:\Users> Get-SolutionUpdate | Format-Table Version, State, HealthState, ResourceId
Version                        State HealthState ResourceId
-------                        ----- ----------- ----------
5.0.2604.21                Installed     Unknown redmond/SBE5.0.2604.21
5.0.2608.10        HealthCheckFailed     Failure redmond/SBE5.0.2608.10
12.2609.1003.7             Installed     Unknown redmond/Solution12.2609.1003.7
12.2610.1004.41 PendingOemValidation     Unknown redmond/Solution12.2610.1004.41

PS C:\Users> Get-SolutionUpdate | Where-Object State -eq "InstallationFailed" | Get-SolutionUpdateRun | ForEach-Object Progress |ForEach-Object Steps
PS C:\Users>

PS C:\Users> Get-SolutionUpdate -Id "redmond/SBE5.0.2608.10" | Start-SolutionUpdate
Confirm
Are you sure you want to perform this action?
Performing the operation "Accept the solution extension license terms provided by HPE. License URI: https://h41380.www4.hpe.com/eula/5200-0656_HPE_EULA_English_v1.0.pdf" on target
"SBE_HPE_ProLiant-Standard_5.0.2608.10".
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"): yes
redmond/SBE5.0.2608.10/543ce710-0757-4087-b3a4-02234aa27e25

PS C:\Users> Get-SolutionUpdate | Format-List ResourceId, Version, State
ResourceId : redmond/SBE5.0.2604.21
Version    : 5.0.2604.21
State      : Installed
ResourceId : redmond/SBE5.0.2608.10
Version    : 5.0.2608.10
State      : HealthChecking
ResourceId : redmond/Solution12.2609.1003.7
Version    : 12.2609.1003.7
State      : Installed

PS C:\Users> Get-CauRun
RunNotInProgress
WARNING: No Updating Run is currently in progress on cluster AzL-Prod-01.PS 

C:\Users> Get-SolutionUpdate | Format-List ResourceId, Version, State
ResourceId : redmond/SBE5.0.2604.21
Version    : 5.0.2604.21
State      : Installed
ResourceId : redmond/SBE5.0.2608.10
Version    : 5.0.2608.10
State      : HealthCheckFailed
ResourceId : redmond/Solution12.2609.1003.7
Version    : 12.2609.1003.7
State      : Installed

As you can see I tried to resume the update it run the healthcheck but then it failed. So, no luck with this.

Other commands that may have useful info:

PS C:\Users> Get-CauReport -Last -Detailed
ClusterName                   : AzL-Prod-01
ClusterResult.Status          : Failed
ClusterResult.StartTimestamp  : 10/13/2026 8:04:20 AM
ClusterResult.RunDuration     : 7:27:32
ClusterResult.NodeResults     : {
                                AZVH-01: Succeeded, ...,
                                AZVH-02: PartiallyFailed, ...,
                                AZVH-03: Canceled, ...,
                                AZVH-04: Canceled, ......}
ClusterResult.RunId           : 8e839863-0e80-4b13-b9cf-58b7c136008e
ClusterResult.ErrorRecordData : MaxFailedNodes limit (0) exceeded.
OrchestratorMachine           : AZVH-05
OrchestratorUser              : CAUAzL-P9r2$
OrchestratorUpdateAccount     :
Plugin                        : Microsoft.HardwareUpdatePlugin
Command                       : Import-Module ClusterAwareUpdating; Invoke-CauRun -ClusterName "AzL-Prod-01" -CauPluginName 'Microsoft.HardwareUpdatePlugin' -CauPluginArguments @{ 'PluginName' =
                                'HPE.CAUUpdatePlugin'; 'HPEInfoJson' = 'C:\CloudContent\Microsoft_Reserved\Update\SBECache\5.0.2608.10\Configuration\SolutionExtension\HPEHelper\hpeinfo.json';
                                'PluginAssembly' = 'C:\CloudContent\Microsoft_Reserved\Update\SBECache\5.0.2608.10\CAUPlugins\01-Custom\HPECAUPluginUpdater.dll' } -MaxFailedNodes 0
                                -MaxRetriesPerNode 3 -NodeOrder @( 'AZVH-01', 'AZVH-02', 'AZVH-03', 'AZVH-04', 'AZVH-05', 'AZVH-06' ) -PreUpdateScript
                                C:\CloudContent\Microsoft_Reserved\Update\SBECache\5.0.2608.10\CAUPlugins\PreUpdateScript.ps1 -PostUpdateScript
                                C:\CloudContent\Microsoft_Reserved\Update\SBECache\5.0.2608.10\CAUPlugins\PostUpdateScript.ps1 -StopOnPluginFailure -SeparateReboots -EnableFirewallRules
                                -ForcePauseAndDrain -FailbackMode Immediate -SuspendRetriesPerNode 5 -Force

PS C:\Users> Get-HealthFault
Severity: Minor failure
Reason         : Failure occurred while trying to install update.
Recommendation : Please check your cluster's update status for details on the failure.
Location       : Cluster
Description    : UpdateFailure
PSComputerName :

PS C:\Users> Get-ClusterNode
Name    State Type
----    ----- ----
AZVH-01 Up    Node
AZVH-02 Up    Node
AZVH-03 Up    Node
AZVH-04 Up    Node
AZVH-05 Up    Node
AZVH-06 Up    Node

About the NIC firmwares:

So, it seems that it updated the firmware on AZVH-02, but not the driver

AZVH-01 -> 26.49.1014 (newer)
AZVH-02 -> 26.49.1014 (newer)
AZVH-03 -> 26.45.1020
AZVH-04 -> 26.45.1020
AZVH-05 -> 26.45.1020
AZVH-06 -> 26.45.1020

I check the iLO portal and all modules have the same firmware versions for AZVH-01 and AZVH-01 compared to the other four hosts. So the SBE package update updated all modules, but not the drivers ...

I think something caused the bitlocker to stop on a reboot while installing the firmware and it couldn't continue to finish deploying the rest of the drivers for AZVH-02. My though is that there must be some switch to ignore that different driver versions and try to install it on AZVH-02 and continue with the update?

I really appreciate your help and if you need more info, please let me know! :)

Best,

Georgi