BIOS rollback Update failing -Engae one, Model 145

[jayapalreddy]

Hi Team

"The system could not find one of the BIOS Update binary files..."

This confirms that HPBIOSUPDREC64.exe is not recognizing the -f switch properly or is still expecting the .BIN file in one of the default folders.

Kindly help for the issue

[jayapalreddy]

Re: BIOS rollback Update failing -Engae one, Model 145

[zoey7886]

@jayapalreddy, Welcome to the HP Support Community!  

Thanks for reaching out about your query regarding BIOS Rollback Update Issue! 

We're thrilled to have the opportunity to assist you and provide a solution.  

If you are experiencing issues with BIOS rollback updates failing, it is likely due to the BIOS update binary files not being located correctly by the update utility. Here are a few troubleshooting steps you can follow:

Ensure Correct File Placement:

• Check that the .BIN file required for the update is located in one of the expected folders on the system. Typically, these can be:
  • Hewlett-Packard\BIOS\New
  • EFI\HP\BIOS\New
  • Hewlett-Packard\BIOS\Previous
  • EFI\HP\BIOS\Previous
• Ensure that the folder names and paths are correct and accessible.

Check File Naming and Extensions:

• Verify that the .BIN file is correctly named, as naming conventions can be crucial for identification by the HP BIOS update tool.
• Ensure that file extensions and case sensitivity are correctly adhered to, especially if your server is running on Linux where filenames are case-sensitive.

Verify Command Syntax:

• Double-check the command you're using with HPBIOSUPDREC64.exe to ensure the -f switch is being properly applied and that it references the correct location and file name.

Network and Server Settings:

• If using a network path, ensure network configurations are correctly set up and the server is accessible. Check proxy settings if applicable.  

Hope this helps! 

Take care, and have an amazing day!  

Did we resolve the issue? If yes, Please consider marking this post as "Accepted Solution" and click "Yes" to give us a helpful vote - your feedback keeps us going!  

Regards, 

[jayapalreddy]

Hi ZOEY7886 / Team,
Thank you for your response.
I’ve extracted the BIOS update files and executed them via Command Prompt and SCCM Task Sequence. Below are the steps I followed:

1. Model: Engage One – BIOS Driver v2.40 (Rollback)

I attempted the update using the following commands from an elevated Command Prompt and via SCCM Task sequence
HPBIOSUPDREC64.exe -s
HPBIOSUPDREC64.exe -s -f sp123456.bin -r
HPBIOSUPDREC64.exe -s -f "C:\Path\BIOS Update\sp123456.bin" -r
\\fileserver\BIOSUpdates\HPBIOSUPDREC64.exe -s -f "\\fileserver\BIOSUpdates\sp123456.bin" -r
However, after reboot, the system still rolls back to BIOS version v2.40 throwing same message.

2. Model: Engage Go – BIOS Driver v1.27 (Rollback)

The update works fine from both Command Prompt and SCCM Task Sequence. However, after reboot, the system prompts for a PIN to proceed with the rollback version.

Could you please advise on how to bypass or suppress the PIN prompt during rollback for Engage Go systems? Any steps or configuration changes to avoid this prompt would be greatly appreciated.

Note:
The latest BIOS upgrades are working successfully via both SCCM Task Sequence and Command Prompt for the following models:

• HP Engage One (Model 145) 
• HP Engage Go Mobile System

The issue arises only when attempting to install rollback versions of the BIOS (After reboot). Please advise on how to proceed with rollback installations, 

[zoey7886]

@jayapalreddy, Welcome to the HP Support Community! 

We're here to help you tackle that BIOS rollback! Don't worry, we've got your back! 

To get you the best assistance, we need to take this conversation to a private chat. We're inviting you to a private message to protect your privacy and ensure that any sensitive information remains confidential. 

To access your private message, just click the little blue envelope icon on the upper right corner of your HP Community profile, next to your profile name.  

We're looking forward to helping you resolve this issue! 

Stay tuned, and thanks for your patience! 

Regards,