-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Boot and Lockup
- Secure Boot

Create an account on the HP Community to personalize your profile and ask a question
11-07-2026 11:32 AM
I have already installed BIOS F.34 on my HP Pavilion All-in One 27-xa0014, motherboard 84EE. Secure Boot still produces an Invalid Signature Detected error. Windows works with Secure Boot disabled. Please connect me with a live HP technical support representative who can confirm whether my model supports the 2023 Secure Boot certificates and provide a model specific fix.
11-09-2026 06:07 AM
Hi @Pops071761
Welcome to the HP Support Community!
Thanks for reaching out!
I understand that you have already updated the BIOS to F.34 on your HP Pavilion All-in-One 27, but enabling Secure Boot still results in the“Invalid Signature Detected” message.Dont worry let me check and help you with this.
To better understand the issue, kindly confirm when Secure Boot is enabled, does the Invalid Signature message appear immediately during startup? and h ave you already tried restoring the HP Factory Default Secure Boot keys?
Kindly try the below and confirm :
- Restart the PC and repeatedly press F10 to enter BIOS Setup.
- Go to Boot Options and temporarily disable Secure Boot.
- Select Clear All Secure Boot Keys, save the changes, and restart.
- Enter BIOS again and select Load HP Factory Default Keys.
- Re-enable Secure Boot, save the changes, and restart.
These are also the steps specifically recommended in the HP Support Community Knowledge Base article for “Invalid Signature Detected”.
You can refer to the article here: Invalid signature detected - Check Secure Boot policy in Setup
You may also refer to the official HP PCs - Secure Boot (Windows 11) document for information on accessing and configuring Secure Boot in the BIOS.
Since Windows starts normally when Secure Boot is disabled, the issue appears specifically related to Secure Boot validation rather than a general Windows boot failure.
I hope this helps.
I'm an HP Employee.
If this reply helped resolve your issue, please select the Accept as Solution as it helps others in the community quickly find the answer they’re looking for.
And if you found this reply helpful, clicking Yes below is a great way to let us know we’re providing the support you need, as it encourages us to keep improving and sharing helpful guidance.