The Secure Boot update failed to update a Secure Boot variable with error Unknown HResult

[gtspeck]

The Secure Boot update failed to update a Secure Boot variable with error Unknown HResult Error code: 0x800700c1 Event: 1796

I am getting the above error randomly. Sometimes it happens when starting my laptop other times it shows up randomly.

All my drivers, according to Device Manager, are up to date.

Neither SFC nor DISM found any errors. I have reset the BIOS, turned Secure Boot off and then back on, reset TPM, BIOS firmware is current, and all drivers are up-to-date.

It started with the update of May 13th. The error never appeared prior to the May 13th update. I did a reset using the recovery (Repair Version), since I couldn’t roll back which didn’t fix this error.

By the way when I turn off Secure Boot I get the following message “The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine”

Windows Build/Version

24H2 26100.4061

[zoey7886]

@gtspeck, Welcome to the HP Support Community!  

Thanks for reaching out about your query regarding the Secure Boot! 

We're thrilled to have the opportunity to assist you and provide a solution.  

Since you've already covered the major ground — BIOS reset, TPM reset, SFC/DISM scans, turning Secure Boot off/on — and the issue began after the May 13th update, this looks like a firmware or update-related hiccup, possibly with how Secure Boot variables are being written during startup or certain triggers.

The error code 0x800700c1 typically hints at a corrupt executable or process not running correctly — almost like Windows is trying to talk to the firmware but the line keeps crackling.

Here’s what I’d suggest trying next:

Check Windows Update History:
Look for a Secure Boot DBX update or firmware update around May 13. If one exists, you might try uninstalling it (if possible) or wait for Microsoft to patch it.

Run MSERT (Microsoft Safety Scanner):
Just in case something subtle is interfering in the background. You can download it here.

Event Viewer – Deeper Dive:
Go to Event Viewer > Applications and Services Logs > Microsoft > Windows > SecureBoot-Update and Kernel-Boot.
There might be a more specific event ID or line showing what variable it’s choking on.

Disable Fast Boot (in BIOS):
Sometimes the system boots too quickly for certain firmware updates or variables to process fully — odd but it happens.  

Hope this helps! 

Take care, and have an amazing day!  

Did we resolve the issue? If yes, Please consider marking this post as "Accepted Solution" and click "Yes" to give us a helpful vote - your feedback keeps us going!  

Regards, 

[gtspeck]

Thank you for your reply. I performed the following:

Kernel Boot for the time and date of the error has no information.

I don’t see SecureBoot-Update listed.

I also don’t see Fast Boot in Bios.

I did do another Microsoft Windows re-install keeping files, apps etc as well as the June 11 update and the error still persists.  What's odd it sporadically appears.  Sometimes at startup other out of no where. Not consistent!

[gtspeck]

Is it possible not having the UEFI CA 2023 CA could be the issue? My BIOS firmware is UpToDate, and I don't know what UEFI certificate is currently active. I was, however, able to verify I don't have the UEFI CA 2023 CA.

[zoey7886]

@gtspeck, welcome back! 😊

Thanks for sharing that detail — you're absolutely on the right track.

Yes, not having the UEFI CA 2023 certificate could very well be the culprit here. When Windows tries to update Secure Boot variables, it needs to verify signatures using those updated certificates. Without the 2023 CA, it’s like handing over a sealed letter without the right stamp — the system just won’t accept it.

Since your BIOS is already up to date, I’d recommend checking with your device manufacturer (or motherboard vendor) for a way to manually import or enable the UEFI CA 2023 certificate, if it wasn’t included in a recent firmware update.

In the meantime, disabling Secure Boot can stop the error pop-up — though I know that's not ideal if you're aiming for full security.

Hope this clears things up a bit! Let us know how it goes — we're here with you every step of the way. 🌱

Take care, and have an amazing day!  

Did we resolve the issue? If yes, Please consider marking this post as "Accepted Solution" and click "Yes" to give us a helpful vote - your feedback keeps us going!  

Regards,