07-15-2016 04:35 PM - last edited on 07-15-2016 04:37 PM by danny-r
Model #: HP Z230 Tower Workstation
Product #: D1P34AV
[personal information removed]
Software Build #: 13WWWDKA601#SABA#DABA
PCBRAND #: HP
Despite installing the updates from softpaq [and manually installing/flashing the BIOS which was marked Critical] and them saying installed [or unknown in some cases] - restart - open softpaq and again...they say "Not Installed" [same ones I just installed and the BIOS update - which I didnt even need becauase it told me [you already have this BIOS do you want to do it anyway?] and when I go to reinstall [I guess...] the softpaq downloads - they all tell me "You already have a newer version on this computer"
So why in gods name is it still saying their not installed?? How can I fix this? How do I know that when the newer updates come out that it won't erroneously think I still need to install the older ones before the new ones [thus leaving me unable to update]
What's going on? [and just a little constructive criticism - You can buy a 200 dollar laptop at best buy and have the geek squad update everything and get rid of all the bloatware before you leave the store for nothing.
You'd think a close to 3000 dollar Workstation [ones NASA use or are updating on the ISS! I know mines the base model but still] would come with the newest drivers/updates/bios installed... just doesn't make a lick of sense to me. To each his own. Wouldn't be an issue if Softpaq worked the way its supposed to unless I'm missing something...
I need to figure this out. Anyhelp would be MUCH appreciated.
07-16-2016 08:02 PM
Your post is not that clear but in any case we are just forum users (and not HP support) so we don't need constructive criticism :)'
Frustrating as it is, for some, consumer gear can sometimes provide a better user experiance than much more expensive corporate gear that seems more locked down and less often updated... Consumer motherboards for example see more micorcode and BIOS updates than worksation motherboards (and thus can take the latest CPU's with ease - big OEM's just expect corporates to replace their stuff often)...
Anyway, as to what BIOS version you actually have installed on your workstation, look when booting as it should display it during POST (or go into BIOS and look). This should clarify the actual BIOS version you have. Then, if a later BIOS version exists, fetch the appropriate softpack from HP and run it.
HP downloads for your system can be found here. Latest version in your case is sp76244.exe (BIOS 1.54 Rev A) and updates some UEFI vulnerabilities that as i understand are not being currently exploited (and can only be exploited with physical access to the system). It's critical according to HP but hardly a case of the sky falling.
In any case, double clicking the HP softpack within windows will create a c:\swsetup\sp76244 directory containing the contents of the softpack and also autorun the update executable. The update executable will then check the BIOS version and indicate if it is the same as the softpack version or later than the softpack version before continuing. If the update is run within windows, it requires a restart to complete it's task (since it needs to put the CPU into 16bit mode to load BIOS into NVRAM, hense restart needed to get CPU into that mode)...
If for some reason the update is failing, try the direct BIOS update method by placing the DOS BIOS found within the c:\swsetup\sp76244 directory on a FAT32 formated USB stick. Then insert the USB stick and during POST jump into BIOS and perform a BIOS update pointing to the USB stick. Not sure the exact menu worrding but it should be obvious.
But if your confusion is related to the "HP tools" that tell you when new updates are available, then i can't offer much as i always manually update my systems and don't use the HP tools to automat it for me (i keep tight control of what i allow on my system)... It simply maybe that HP tools has not detected the latest BIOS and this sees a new varsion available - uninstall and resinstall HP tools may or may not resolve such issues... Or simple refere to the HP update site periodically and see what you consider worth updating 🙂