Bios update f.33 disabled my 2nd hard drive

[Stavrosc]

I have been a very satisfied owner of an hp 14 am011nd notebook that is still in its warranty

. It is my 3rd hp device.

 To counter its limited storage i have installed an 120gb ssd with a caddy to its internal port 

( patriot burst 120 gb).

It has been working excelent untill now.

Recently i decided to upgrade my drivers with hp support assistant software and among the drivers was bios update f.33.

After the update the ssd is not recognised by the bios. 

I have tested the ssd and it works fine. I tryied lots of things even another hdd on the slot but problem persists. Port seems completelly disabled.

Bios rollback will only allow me to reroll my bios up to f.32 whitch doesnt fix the problem.

I am hoping for a way to rollback to my older bios, or for a way to re enable the disabled port or for a bios update that will mend the issue.

Thanks in advance

[Barachiel]

@Stavrosc

Good Day. A warm welcome to the HP community. I reviewed the case regarding issues with the computer.

I will be delighted to assist you here. 

Follow this link and look for bios. Click on it and then click on the previous versions tab.

Click on download and install the earlier version.

Keep me posted. 🙂

[Stavrosc]

Hello again and thanks for the reply.

I have downloaded all previous versions of the bios but i can install only versions f.33 and f.32.

I have tried all 3 upgrade methods/ways.

With  hp tools usb stick and windows key + b gives me twice blinking caps lock. It usually translates to an error code. Possibly this option is locked ?

Running From windows previous versions other than 32 and 33 have the upgrade option greyed out. 33 and 32 install normaly.

Booting Via diagnostic tool while having extracted the bios image and its signature file that is matching my motherboard i can only install versions 33 or 32. With any version prior tho theese 2 i get an error " unable to open image file". If the signature file is part of a key of some sort propably the rest of it has to come from current version and it ends up as a missmatch to prevent rollbacks.

I think its locked intentionally from allowing rollbacks to earlier builds. 

Thanks in advance

[Barachiel]

@Stavrosc

Thanks for the response.

In this case I believe it require's a one to one conversation.

Please check the private message I've sent you with the required details.

Good luck. 🙂