• ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
Join the HP Community Solve‑a‑thon | Help Others & Share Your Solutions | Live on Zoom | 2:30 PM to 2:30 AM IST | Every Wednesday Click here to know more
HP Recommended

Secure boot cannot be enabled because all UEFI secure boot key variables are missing. In windows powershell, "Get-SecureBootUEFI" returns as "Variable is currently undefined" for PK, KEK, and db. In BIOS, platform key shows "Not Enrolled" and secure boot cannot be properly activated. Using "Load HP Factory Default Keys" completes and clears pending action, but doesn't populate any secure boot keys and platform key remains not enrolled after reboot.

System Details :

HP Omen 40L GT21 series

Motherboard - 8949

BIOS - F.38 (updated/reflashed, no change)

TPM 2.0 - enabled, functional

Secure boot state - off (can't be turned on due to missing keys)

I've been up all night trying to fix this and i genuinely have no clue what to do anymore. My sanity is low. Please help.

1 ACCEPTED SOLUTION

Accepted Solutions
HP Recommended

Greetings,

 

I don't work for HP.

 

I have been seeing many folks in this Forum, using various HP MBs, having the same Secure Boot data base problem you are having.

 

My guess is: the HP team responsible for firmware updates erroneously removed Secure Boot data when preparing the latest BIOS updates for the affected MBs.

 

I would say you'll have to check for a future BIOS update which, hopefully, fixes this problem. There is nothing you can personally do to solve the problem.

 

Regards

View solution in original post

3 REPLIES 3
HP Recommended

Greetings,

 

I don't work for HP.

 

I have been seeing many folks in this Forum, using various HP MBs, having the same Secure Boot data base problem you are having.

 

My guess is: the HP team responsible for firmware updates erroneously removed Secure Boot data when preparing the latest BIOS updates for the affected MBs.

 

I would say you'll have to check for a future BIOS update which, hopefully, fixes this problem. There is nothing you can personally do to solve the problem.

 

Regards

HP Recommended

**bleep**, that sucks. Thank you for the help though, it's much appreciated. My sanity shall thankfully return now.

HP Recommended

Greetings @spect-ace ,

 

Just saw a possible solution Here.

 

Try it to see if it works.

 

Regards

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.
-->