How to Recover or Unlock BIOS Password for old EliteBook Series (2170p)

[Andy1786]

Hi All,

Greetings from Jakarta,

I just got a second hand HP EliteBook 2170p. It is still a very good condition and I'm planning to use it to support my daily job. Unfortunately, the BIOS Administration setting is protected by password, and the  previous owner already forgot the password her used. Is that true that there's a way to reset/ recover the BIOS Administration password without changing the BIOS chip or the Motherboard? Because, changing the chip, sounds risky, and changing the whole motherboard (this is what the HP representative in my local country (Indonesia) suggested) will cost me a lot. Please kindly advice.

Regards,

Andy Ch

[IT_WinSec · Accepted solution]

Hello @Andy1786

Welcome to the HP Support forum. Thank you for posting. You made an excellent choice with your Elitebook.

Most business class notebooks (including yours Elitebook and Probook) have better security. Password cannot be removed here in the forum - you will have to contact HP Business Support for assistance on removing the password.

Note sure what they told you but under most curcumstances and if no other issues, support should be able to help you with SMC.bin file

Here is how to reach HP:

Phone >> http://www8.hp.com/us/en/contact-hp/ww-phone-assist.html

Chat >> https://support.hp.com/us-en/contact-hp

HP Business support should be able to send you a customised SMC.bin file and instructions which you can use  to reset the password. Under certain curcumstances, there may be some other problem and they will not be able to generate the SMC.bin file and the motherboard replacement is the only way.

Note that assistance for such issues is usually free of charge for HP business class computers. Ask them for explanation why they believe motherboard replacement is needed and why not using SMC.bin file

Hope this helps. Please, mark the post as a solution if it helped.

Let me know if you face any difficulties.

[Andy1786]

Thanks, IT_WinSec, I will try to reach the support guy again and do what you suggested.