cancel
Showing results for 
Search instead for 
Did you mean: 
grimson73
Level 1
6 3 0 1
Message 1 of 8
2,094
Flag Post

HP Z240/Z238 series Workstation System BIOS v1.71 RECALLED? (1.66 Rev.A now 'latest')

HP Recommended
HP Z240/Z238
Microsoft Windows 10 (64-bit)

HP Z240/Z238 series Workstation System BIOS v1.71 is not available anymore (sp88736.exe) on the support download site. It's really annoying when HP does this without any information!

This was not the first time as before this happened with the 'spectre' microprocessor Intel failure.

things happen but please describe accordingly!

 

 

7 REPLIES 7
DGroves
Level 11
4,712 4,683 444 995
Message 2 of 8
Flag Post
HP Recommended

actually HP did/does tell you, if you click on the v1.66 details link it tells you that the SPECTRE/MELTDOWN patch has been removed  due to compatability with intel 6th gen/xeon E3-1200 v6 cpu's

 

so it appears that HP has found a problem with the intel microcode on this model(s) and pulled it untill they can resolve the issue

 

and when HP reissues the specture/meltdown patch  in the future it will also be documented the the details notes of the new bios 

 

 

Version: 1.66 Rev.A

Fixed in this release: • Fixes an issue where system would not boot with certain Ethernet Server Adapters configured for iSCSI boot. • Reverts Intel processor microcode to 0xBA for Intel 6th generation Core processor product family and Intel Xeon processor E3-1200 v5 product family.
• Reverts Intel processor microcode to 0x5E for Intel 7th generation Core processor product family and Intel Xeon processor E3-1200 v6 product family.
• Removes enhancement to address CVE-2017-5715.

TPM2.0 PCR0 = 52DD9406F7C6B8B49D4B71E9D6194A5FE7541F131EACDCDB84A30FA194F89733 (SHA256)
TPM1.2 PCR0 = 38F63BA87EF6E082F1AF0308F6FB089639D471CE (SHA1)

Version: 1.63 Rev.A

Fixed in this release: • Fixes an issue where system could incorrectly report a POST error (90D-System Temperature). • Improves security of UEFI code and variables. (Vulnerabilities to be disclosed as HP PSR-2017-0123 and HP PSR-2017-0134). HP strongly recommends promptly transitioning to this updated BIOS version.
• Updates Intel reference code to v4.1.0.8.
• Updates PXE OROM to v1.12.
• Updates UEFI LAN driver v0.0.17.
• Adds F10 Setup and WMI option to disable individual UEFI boot devices
• Adds certain Linux boot paths 


PCR0 (TPM1.2)= BF465D3BE1D47250FC031DAB516B36C36D44109C (SHA1)
PCR0 (TPM2.0)= 3C2FEEEA57821A438E6FC6EEF7E2C3473F2099532DD6D9454284E34FC5A48A5D (SHA256)

Version: 1.60 Rev.A

Fixed in this release: • Adds UEFI NX Protection support.

Was this reply helpful? Yes No
Skylarking
Level 6
382 364 22 69
Message 3 of 8
Flag Post
HP Recommended

HP's documentatuion with respect to BIOS changes leaves a lot to be desired (on many fronts).

 

If BIOS v1.71 was released by HP and then later cancelled or withdrawn, then it is not enough to make some rather obsucure reference to a security vulnerability being 'reverted' in an earlier BIOS release as an explaination to it's disapearance.

 

Such can never be an explaination for the fact v1.71 is no longer available and does nothing to help those that may have downloaded and applied this 'problem' release.

 

What is needed is clarity and openness which would require that a BIOS v1.71entry exists within the BIOS section of the software and drivers download page (obviously without the actual problem SP.exe download being available). But all the remaining documentation related to V1.71 should be included with BOLD explanation in the history section (as well as at a top level) as to why it was withdrawn along with the technical reason for such AND more importantly how someone who has applied such a BIOS can indeed recover from it !

 

Doing it the way HP does just creates confusion and hides the fact the such a BIOS was released.

 

So all i can see is that HP's method to document the disapearance of a BIOS release is more an attampt to hide their obvious failure at the expense of clarity and openness.  And it comes at their customers expense...

Was this reply helpful? Yes No
DGroves
Level 11
4,712 4,683 444 995
Message 4 of 8
Flag Post
HP Recommended

HP workstations come with the "HP Performance Advisor" application which by default checks for updated drivers/Bios's

on startup, and at user defined intervals, if you removed this program then it's your responsibility to check fo updates or changes

 

and if you don't like hp's current way of posting changes to a bios or driver update that is on their web site you might want to consider emailing hp support exactly what you feel needs to be changed (and provide a example) rather than posting here in a user to user board that you don't like HP's current method. This is the best way to let them know, since the HP moderators only check the boards on a semi-regular basis

 

i personally don't think the HP posting of the reasion the bios was rolled back for your model was obsure since it was plainly listed in the changes. also if the problems with this bios (1.71) were major, then hp would have posted this and recomended all users downgrade so the issue appears to be a minor one and if you are not having any problems then there is no reasion to downgrade to 1.6x

 

again,complaning to me or other uses on this forum is not the best way to promote a change. specifically pointing out what should be changed in your opinion and forwarding it to hp support is a better way to go in my opinion

Was this reply helpful? Yes No
grimson73
Author
Level 1
6 3 0 1
Message 5 of 8
Flag Post
HP Recommended

Well,

 

According to the history a lot more firmware revisions were removed,

1.71, 1,70 and 1.68!

 

SP88736/history.htm N51 Firmware Family - Revision History

History

Version 1.71

 

Updates Intel processor microcode to 0xC6 for Intel 6th generation Core processor product family and Intel Xeon processor E3-1200 v5 product family.

Includes enhancement to mitigate CVE-2018-3639 and CVE-2018-3640 for Intel 6th generation Core processor product family and Intel Xeon processor E3-1200 v5 product family.

 

 

TPM2.0 PCR0 = F9C6FB50346141649D3DE5D259B317CF18A24D07A6CAB21AE0F9DAF4BB6B93A9 (SHA256)

TPM1.2 PCR0 = EBD4A531552942750DD981E225B453FACFAD4C8D (SHA1)

 

Version 1.70

 

Updates Intel processor microcode to 0x8E for Intel 7th generation Core processor product family and Intel Xeon processor E3-1200 v6 product family.

Includes enhancement to mitigate CVE-2018-3639 and CVE-2018-3640 for Intel 7th generation Core processor product family and Intel Xeon processor E3-1200 v6 product family.

Adds NTFS driver support to enable the HP Cloud Recovery Download Tool.

 

TPM2.0 PCR0 = 0EFA1C0578454459BA35572A90C22B601C0EDF3321C5DE6BE35BF160FCA05938 (SHA256)

TPM1.2 PCR0 = 77060BA92272E803F40B88FEC3AF2B4DB579D899 (SHA1)

 

Version 1.68

 

Updates Intel GOP driver to v9.0.1052.

Updates UEFI Diagnostics to v1.23.

Improves security by requiring Administrator password to enter Intel MEBx menu.

Enhances “Early PCIe Delay” functionality to accommodate devices requiring additional PCIe delay.

Fixes an issue where system would not display when using certain projectors in some integrated graphics configurations.

Fixes an issue where system would not boot with certain USB device installed.

Fixes an issue where system would experience a 3.3 beep code when attempting to boot with certain graphics cards with Option ROM policy set to All UEFI.

Fixes an issue where system would take excessive time to boot with certain USB imaging devices installed.

 

TPM2.0 PCR0 = A911D953D8DBC4A061931C48322C5D2906A058E372EBA12E5637B46F31F967D9 (SHA256)

TPM1.2 PCR0 = 9A3A0835BCF453B762094A93D9449F29C134A9EF (SHA1)

 

Version 1.66

 

Reverts Intel processor microcode to 0xBA for Intel 6th generation Core processor product family and Intel Xeon processor E3-1200 v5 product family.

Reverts Intel processor microcode to 0x5E for Intel 7th generation Core processor product family and Intel Xeon processor E3-1200 v6 product family.

Fixes an issue where system would not boot with certain Ethernet Server Adapters configured for iSCSI boot.

 

TPM2.0 PCR0 = 52DD9406F7C6B8B49D4B71E9D6194A5FE7541F131EACDCDB84A30FA194F89733 (SHA256)

TPM1.2 PCR0 = 38F63BA87EF6E082F1AF0308F6FB089639D471CE (SHA1)

 

 

 

So I'm with the team who call HP out for this on public forums. No way a simple request would be honored and eventually would lead to nothing. Corporate, heck even consumers, do need to know WHY and if you SHOULD revert your firmware to the current posted one.

 

Also the 'current' 1.66 is not posted to replace the 1.71 firmware because the releasenotes are just the same as they were when 1.66 came out in February this year. So nothing says that this replaced the 1.71 firmware.

 

Regards,

Arian 🙂

Was this reply helpful? Yes No
DGroves
Level 11
4,712 4,683 444 995
Message 6 of 8
Flag Post
HP Recommended

sorry but hp has a diffrent opinion on the current bios revision number,...... and it's v1.67 currently which has obviously replaced 1.68-1.71 and is the current version posted on the driver page for your model and this 1.67 will remain so until hp releases a new bios

 

and HP does notify users of changes, perhaps you missed the notices somehow?

 

https://support.hp.com/hk-en/document/c05963213

 

https://support.hp.com/us-en/document/c06042840

 

https://support.hp.com/hk-en/document/c06075885

 

I have not listed every change page, but you get the general idea right?

 

 

 

Was this reply helpful? Yes No
Ed-Westminster
New member
1 1 0 1
Message 7 of 8
Flag Post
HP Recommended

I have fallen foul of the 1.71 rogue BIOS along with our ever helpful HP engineers.
This was on a Z240.

Having been the compliancy officer on some of the largest networks in the country I am appalled that this was allowed to happen. The fault is obvious, catastrophic and repeatable and the only way it can have been allowed out is that it was never tested!

 

This incident begs several questions:

 

The Z240 motherboards seem to be of variable build quality and they have been racing through BIOSes since I got mine in late December.

 

I updated because the SoftPaq utility told me to. What would happen if this had been applied when the motherboard was out of warranty?

 

Why was this BIOS release untested on the Z240/238s before release?

 

What is HP's position on what we should believe to upgrade a BIOS in future? 

Was this reply helpful? Yes No
grimson73
Author
Level 1
6 3 0 1
Message 8 of 8
Flag Post
HP Recommended

DGroves,

 

I agree with you and I do follow those releasenotes.

Those release notes are only posted when NEWER versions are released... so .. all well UNTIL they are withdrawn.

Where are the release notes / Client notifications when this happens?

 

The only 'release note' is that the previous firmware version is the latest available o nthe website when browsing.

That just does not cut it!

 

We need a reason why the withdrawal has happened, just like the reason why a NEWER revision is posted.

 

To summarize for this instance:

HP does release releasenotes for newer revisions.

HP does not release releasenotes for why newer revisions were removed.

 

 

Also:

The valuable post of Ed-Westminster shows EXACTLY why HP should communicate. If I read correctly those withdrawed firmwares caused malfunctions on several machines. Therefore HP should WARN their customers not to use firmware above 1.66.

 

Was this reply helpful? Yes No
Warning Be alert for scammers posting fake support phone numbers and/or email addresses on the community. If you think you have received a fake HP Support message, please report it to us by clicking on "Flag Post".
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation