HPIA BIOS update bricking HP Z2 Mini G9's - anyone else experiencing this ?

[Ben762]

Hi all,

I use HPIA within our SCCM task sequence to update everything at build time with the command line :

HPImageAssistant.exe /Operation:Analyze /Category:All /Selection:All /Action:Install /Silent /ReportFolder:"<folder>" /debug /LogFolder:"<folder>"

This has been working fine for a while across our fleet - but these are first Z2 Mini G9's.

Recently we got some new HP Z2 mini G9's into the environment and after the HPIA steps runs, on the next reboot, we get the dreaded flashing red lights (and beeps) of death.

Initially i thought "faulty machine" - but it has happened on 3 in a row.

i managed to get one back using emergency BIOS recovery - and can see from the HPIA logs that it appears to be
Launching 'C:\ProgramData\HP\HP Image Assistant\HP Z2 Mini G9 Workstation Desktop PC\sp163086_HPZ2G9WorkstationSystemBIOS\install.cmd'

I will admit that HPIA has been fairly "set and forget" for me so far - so i havent really had to troubleshoot something like this.

Has anyone else had this ? Is there something i need to do to make this work, or is it perhaps something not quite right with HPIA for this model or ?

[Dragora]

Hi Ben762

Based on the information, this is likely a model-specific issue with how the HP Z2 Mini G9 Workstation interacts with the HP Image Assistant (HPIA) for its BIOS update.

Here is a breakdown of potential causes and the recommended solution:

Cause Analysis: BIOS Update Failure

The log entry indicating the launch of sp163086_HPZ2G9WorkstationSystemBIOS\install.cmd confirms that HPIA is attempting to install the BIOS update, which subsequently fails upon reboot and triggers the recovery mode (flashing lights/beeps).

1. Incomplete/Incorrect BIOS Prerequisite (Most Likely)

Modern HP BIOS updates often require the HP Firmware Installer Service (or similar mechanisms) to be running and sometimes need a specific version of the HP Client Management Script Library (CMSL) or other support tools. Simply running the command file directly may bypass necessary pre-checks or services, leading to failure.

2. Incorrect HPIA BIOS Installation Method

HPIA is designed to handle this, but for certain new or high-security models, the method it selects may be incompatible with a Task Sequence environment's current state.

3. SCCM Power State Interference

In a Task Sequence, the machine is often in a controlled environment. A BIOS update requires a clean reboot and for the new firmware to flash. If the SCCM client or Task Sequence environment interferes with this process, it can corrupt the flash.

Recommended Solution: Separate and Stage the BIOS Update

The safest and most robust way to manage HP BIOS updates in a Task Sequence is to separate the BIOS update from the driver/firmware updates and use the native HP utility designed for OS-independent flashing, instead of relying on the general Action:Install command within HPIA.

Step 1: Use HPIA to ONLY Download, NOT Install

Modify your HPIA command line within the Task Sequence for the initial pass. This will download all drivers and firmware except for the tricky BIOS update, leaving the BIOS package for a controlled step.

Modified HPIA Command Line:

HPImageAssistant.exe /Operation:Analyze /Category:All /Selection:**!BIOS** /Action:Install /Silent /ReportFolder:"<folder>" /debug /LogFolder:"<folder>"

• The key change is /Selection:!BIOS. This tells HPIA to exclude the BIOS update package from the installation action.

Step 2: Extract the BIOS Update Package

Use a separate HPIA run with the /Operation:Download and /Action:Install command to download only the BIOS package for the Z2 Mini G9 into a known location in your Task Sequence.

Example Command to Extract BIOS (Optional, but cleaner):

HPImageAssistant.exe /Operation:Download /Category:BIOS /Selection:All /Action:Install /SoftpaqDownloadFolder:"C:\_Drivers\Z2G9_BIOS"

Step 3: Use the Dedicated HP BIOS Flashing Utility (HPQPFlash/BiosConfigUtility)

The BIOS softpaq (the sp##### folder HPIA extracted) contains the necessary flashing utility, often called HPQPFlash.exe or HPBIOSUPDREC.exe. You need to use the one shipped within the BIOS softpaq to ensure compatibility.

You would typically create a new step in your Task Sequence after the initial HPIA pass:

1. Add a Run Command Line step (or similar, depending on your SCCM TS structure).

2. Point the command line to the extracted utility and its associated configuration file (often .bin or .sig).

Example Command Line (Location/utility name will vary slightly):

"C:\_Drivers\Z2G9_BIOS\sp163086\**HPBIOSUPDREC.exe**" -f **"C:\_Drivers\Z2G9_BIOS\sp163086\08573.bin"** -s -r

• -s usually means Silent.

• -r usually means Reboot.

• -f specifies the firmware file.

Step 4: The Final Reboot

A final Task Sequence step to reboot the machine is necessary to trigger the BIOS flash if the utility doesn't handle the reboot cleanly. Crucially, this reboot must be outside of the Task Sequence environment.

• Add a Restart Computer step with the option "The currently installed default operating system" selected. This forces a clean reboot, allowing the BIOS update to take control outside of the Windows PE or OS build phase.

Quick Fix/Workaround to Test

If you are just looking for a quick test to see if the BIOS update is the ONLY issue, simply change your existing command line to exclude the BIOS for the Z2 Mini G9:

Quick Test Command:

HPImageAssistant.exe /Operation:Analyze /Category:All /Selection:!BIOS /Action:Install /Silent /ReportFolder:"<folder>" /debug /LogFolder:"<folder>"

If the machines build successfully without the beeps, you've confirmed the BIOS update is the culprit, and you can proceed with the multi-step staging method above.

I hope the above is helpful.

If this helped you solve your problem, please mark my answer as the solution. Thank you!

[Ben762]

Thanks for the reply.

As far as your comments

Option 1 - Isnt that the point of a tool like HPIA? to identify those pre-reqs and install them ? I mean, if it is pre-reqs - if i can find out what the specific pre-req is, im happy to address it.... it just kinda defeats the purpose of the tool!

Option 2 - same as above really.

Option 3 - thats not the case

As far as "The safest and most robust way to manage HP BIOS updates in a Task Sequence is to separate the BIOS update from the driver/firmware updates and use the native HP utility designed for OS-independent flashing, instead of relying on the general Action:Install command within HPIA"

for a start - why are you bolding certain pieces of text ?

and the guts of that statement is that the HPIA is not a reliable tool.... so... if thats the case.... then... why has it been released as an enterprise tool ?

While none of the statements in your reply are incorrect - it flies in the face of the entire point of the utility!

[Dragora]

Hi Ben762

I use bolding to emphasize key terms, concepts which I consider useful. I'm sorry if the way I wrote to you bothered you; someone else will help you.

Thanks for reading!

[dfelman]

HPIA process is to download the softpaq in question, extract it, and install it with the silent install instructions obtained from the systems' reference file it gets when it starts. The instructions are also listed in the softpaq's cva file (sp163086.cva) and for this particular BIOS Softpaq is: SilentInstall="HpFirmwareUpdRec64.exe" -s -r -b

-b entry is to suspend bitlocker