Bitlocker Issue On Laptop

I have an HP Elitebook 870, left over from my old job, and I wish to continue its use at home.
I can no longer login, nor have access to the bitlocker code.
Now, i know the bitlocker protects the encryted data within, but i don't in, i just want to be able to wipe the HD and re-format it, so that I can do a new clean windows install.
I can find ways to resolve and get rid of bitlocker, but they all assume i can boot from USB, but this PC seems to prevent booting from USB thru its HP BIOS.
Any ideas how to fully resolve this???

 

Contact your old job and ask how they disabled the BIOS key. Then get into BIOS and change it so you can boot USB, then reinstall Windows.

 

Thanks, but they are no longer trading and thus no tech support.
In (what I think is the hp bios) I can toggle secure boot off/legacy on, but still doesn't work.

 

If you can get into BIOS you can set it to boot to USB, then reload Windows.

 

Thanks, i can get into such, but there is an HP form of BIOS on top of normal BIOS (at least i think that's what it is, or just HPs BIOS), and it prevents that?!?
Hence my situation.

 

I'm confused how you can get into the settings where secure boot is, yet can't change boot order. A possible work around if you have another PC & an adapter for the hard drive (assuming that laptop has a removable drive). https://www.bleepingcomputer.com/fo...ll-windows-directly-from-the-hard-disk-drive/ or
https://www.majorgeeks.com/files/details/wintohdd.html "WinToHDD is a handy and beneficial Windows software that allows you to install or reinstall Windows without using a CD/DVD or USB drive."

Basically copy the install files to the drive since the PC will boot from the drive and install the OS, use to do that in the Win 98 days, was much faster.

 

Cheers, yes got mostly sorted here: https://support.hp.com/lv-en/document/c04784866
But also, had to enter HPs BIOS, and apply factory defaults for a few settings, so that it wouldn't try to re-associate the windows with previous corporation 9which it kept trying to do upon new windows install). Seems to all resolved now.