Newly Created HP BIOS Update Packages Suppressing Leading Zero in Version (7.2.4)

[jpatton1979]

In previous versions of the tool, HP BIOS updates were versioned exactly as HP lists them (e.g. Elite Mini 800 G9 would be 02.15.12). However, the tool is now suppressing the leading zero (e.g. 2.15.12). This is resulting in packages being unnecessarily created when the latest version is already packaged. I've tried this on both an Elite Mini 800 G9 and an EliteBook 860 16 inch G10.

[ericvanboven]

I have just been removing the extra 0 after so it will work with devices.

[jpatton1979]

We've got lots of pre-existing BIOS update packages so going back and deleting the leading "0" on all of them isn't really an option...especially if/when this gets fixed/reverted then we'd have to go back and re-add the leading "0".

[stephannn]

Hi, the change may comes through the Get-SoftpaqList module from HP. I modified it like this: $BIOSVer = (($HPBIOSDownload.Version.Trim() -split '\.') | ForEach-Object { $_.PadLeft(2, '0') }) -join '.' I modified it in my fork: https://github.com/stephannn/DriverAutomationTool/blob/master/Current%20Branch/7.2.2/DriverAutomationTool.ps1