this post was submitted on 10 Jun 2024
702 points (99.0% liked)

Technology

55657 readers
4381 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

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 are viewing a single comment's thread
view the rest of the comments
[–] NutWrench 17 points 3 weeks ago (4 children)

Microsoft has no business forcing firmware updates on anything. This is something HP should have handled. Those laptops are THEIR products, not Microsoft's.

[–] [email protected] 18 points 3 weeks ago* (last edited 3 weeks ago)

This is something HP should have handled.

If a bad update is rolled out then it's the responsibility of the software maker partner (HP) and the distributor (Microsoft), not just one or the other.

Those laptops are THEIR products, not Microsoft’s.

Both Microsoft and HP have branding on their laptops and a responsibility post-sale for the reliability of their systems. Hardware, firmware and OS responsibilities are all party to this chain of failure.

[–] [email protected] 12 points 3 weeks ago (1 children)

Those laptops are THEIR products, not Microsoft’s.

Microsoft: All your PC are belong to us.

[–] PlasticExistence 6 points 3 weeks ago (2 children)
[–] [email protected] 5 points 3 weeks ago
[–] [email protected] 2 points 3 weeks ago

"Hit the road Jack"

[–] x0x7 10 points 3 weeks ago

This logic breaks down when you realize the laptop is mine, and not HP's or Windows. And any software that is mine, my copy of windows should also be mine and not microsoft's, can modify my device if I have selected some of my software to do that.

[–] ikidd 6 points 3 weeks ago (1 children)

Well, you might want to avoid fwupd too then

[–] madscience 1 points 3 weeks ago (2 children)

Fwupd is a pull model, not a pushed automatic update. Who the fuck doesn’t read release notes and do due diligence before running fwupd?

[–] ikidd 3 points 3 weeks ago

Every fucking Ubuntu user where it's installed by default in Software Center?

[–] jj4211 2 points 3 weeks ago

Fedora pulls fwupd by default. If you use one of the 'check for updates' UIs, fwupd, dnf, and flatpak sources are all polled.