HP bricks ProBook laptops with bad BIOS delivered via automatic updates — many users face black screen after Windows pushes new firmware
HP bricks ProBook laptops with bad BIOS delivered via automatic updates — many users face black screen after Windows pushes new firmware
HP / Microsoft seems to have removed the bugged BIOS download now.
On May 26, a user on HP's support forums reported that a forced, automatic BIOS update had bricked their HP ProBook 455 G7 into an unusable state. Subsequently, other users have joined the thread to sound off about experiencing the same issue.
This common knowledge regarding BIOS software would, then, seem to make automatic, forced BIOS updates a real issue, even if it weren't breaking anything. Allowing the user to manually install and prepare their systems for a BIOS update is key to preventing issues like this.
At the time of writing, HP has made no official comment on the matter — and since this battery update was forced on laptops originally released in 2020, this issue has also bricked hardware outside of the warranty window, when previously users could simply send in the laptop for a free repair.
Overall, this isn't a very good look for HP, particularly its BIOS update practices. The fragility of BIOS software should have tipped off the powers at be at HP about the lack of foresight in this release model, and now we're seeing it in full force with forced, bugged BIOS updates that kill laptops.
You're viewing a single thread.
HP expanding their bad practices from printers to PCs now?
Microsoft should also be to blame here. Sending BIOS updates via automatic windows updates should not be a thing.
Permanently Deleted
The alternative is that BIOS updates simply never get applied.
Not sure when the sentiment changed, but it used to be heavily recommended against updating the bios on any computer unless there was a specific feature or fix your computer needed.
Sentiment changed when the "BIOS" became a component for enforcing security architecture via "SecureBoot" and also Bitlocker sealed to PCRs only does so much if the BIOS code is vulnerable. Now they really badly want a "trusted" chain from some root of trust until the OS bootloader takes over. Problem is that the developers have historically enjoyed being in a trusted, single user context for decades and so the firmware has been full of holes when actually pushed.
Which is better than bricking a machine
That's a better alternative...