BIOS update bricked my laptop, no posted solutions have worked.

[blav1]

My laptop (HP Notebook 15-bs115dx) was working perfectly fine until I updated the BIOS version from version F.34 to F.75 rev A, which is the latest version present on the driver page for this model. I ran the exe, let the computer restart, and the update seemed to go fine. Then, I was never able to get anything to show up on the screen again.

The laptop will turn on, but the only things that indicate it's even on are the power light and the fan. Nothing is happening on the screen, leading me to believe that the BIOS update has bricked the chip.

What's especially infuriating is that I've managed to find several other posts to this forum describing the exact same issue with this exact bios version with laptops with very similar model numbers to mine, and not a single person has been able to successfully fix the issue. HP support either recommends the same steps of pressing win+b (or v) while turning the laptop on (which doesn't work for this issue, as me and several others seem to have found) or just straight up ignoring the post altogether if the person has already tried this step. Along with hard resetting the laptop by removing the battery and holding the power button, which also does nothing to fix a bricked bios chip.

Here are some links to others with the same issue that I've found: Post 1 Post 2 Post 3 Post 4 

That's just what I managed to find after a couple of minutes of digging. The fact that this BIOS update has bricked so many machines without being fixed or removed from the driver page is unbelievable. The fact that HP support is so difficult to reach is unbelievable, too. I could not find an email, call, or online chat option after scouring the internet for over 20 minutes. Am I forced to post to this forum in hopes of someday getting an answer? I should not have to pay to get this laptop repaired when the issue is 100% HP's own fault. This issue has clearly existed for years with no effort on HP's end to rectify it, and I am disgusted with the lack of action taken to prevent this from happening over and over again. If I wanted to lean into a bit of conspiracy, I'd go as far as to say that this is just another way tech companies are getting people to abandon their old hardware that still works: by pushing bad updates to brick machines and force people to buy new ones.

Is there any way I can talk to an actual agent about this issue? Or has anyone with a similar issue actually managed to fix it? I wanted to try rolling back to bios version F.34, but many sources online claim that it isn't possible to roll back from F.75, and I'm having difficulty finding a download for version F.34 anyway.

[VikramTheGreat]

Hi @blav1,

Welcome to the HP Support Community.
 

Thank you for posting your query. I will be glad to help you.

We understand your frustration, and we sincerely apologize for the experience you've had after updating your HP Notebook – 15-bs115dx to BIOS version F.75 Rev.A. You've done your research,

To clarify the version history:

• BIOS F.34 was released in late 2018, and since then, multiple BIOS updates have been rolled out by HP to improve system stability, support newer OS configurations, and address vulnerabilities.
• The most recent version, BIOS F.75 Rev.A, is indeed the latest available on the HP support site for the 15-bs1xxx series.

What You Can Do Now

1. Try BIOS Recovery (Even if Win + B Didn’t Work)

Sometimes the recovery key combo is Windows + V instead of Windows + B:

1. Turn off the laptop.
2. Insert a USB drive with the correct BIOS recovery file (see below).
3. Press and hold Windows + V, then press and hold the Power button for 2–3 seconds.
4. Release the power button but keep holding Windows + V until the screen lights up or you hear beeps.

Download BIOS Version F.34 (Rollback)

HP doesn’t always list older BIOS versions publicly, but you can try the official support page:

🔗 HP Notebook - 15-bs115dx Software and Driver Details

I hope this helps.

Take care, and have an amazing day!
 

Did we resolve the issue? If yes, please consider marking this post as "Accepted Solution" and click "Yes" to give us a helpful vote - your feedback keeps us going!

Regards,

VikramTheGreat