• ×
    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
Check out our WINDOWS 11 Support Center info about: OPTIMIZATION, KNOWN ISSUES, FAQs, VIDEOS AND MORE.
HP Recommended

HP Pavilion Desktop PC TP01-2000a – winver – 25H2 build 26200.6901

 

So I kept seeing errors in ‘view reliability history’. Went to: Event Viewer / Windows Logs / System / Error. After filtering I saw a “lot” of these ‘errors’ TPM-WMI 1796. Google search says it regards ‘secure boot’ and that it needs to be enabled. So I go into ‘bios / security tab and I don’t see ‘secure boot’ but I do see TPM Device – Available and TPM state – enabled. I didn’t change anything.

 

Any suggestions on how to I resolve this issue?

 

So I went back into Bios, looked under Boot Order this time, and I saw 'secure boot' and it was enabled.  So why am I getting these 'errors' to enable 'secure boot'?

Thanks in advance

 

Thanks in advance

 

1 ACCEPTED SOLUTION

Accepted Solutions
HP Recommended

Hi @eddie11013 

 

Welcome to the HP Support Community! We're here to help you get back up and running.

 

You're seeing TPM-WMI 1796 errors despite Secure Boot being enabled because the issue likely stems from a recent Windows update or firmware interaction—not from your BIOS settings.

 

Here’s a clear breakdown of what’s happening and how to address it:

 

What the TPM-WMI 1796 Error Means

  • Event ID 1796 typically logs:
    “The Secure Boot update failed to update a Secure Boot variable with error Unknown HResult Error code: 0x800700c1.”
  • This error is triggered when Windows attempts to update Secure Boot variables via TPM but encounters a failure—often due to firmware communication issues or TPM driver inconsistencies.

 

Why You’re Seeing It Even Though Secure Boot Is Enabled

  • Your BIOS shows Secure Boot is enabled, and TPM is active, which is correct.
  • However, Windows may still fail to update Secure Boot variables if:
    • A recent Windows update (like KB5058379) introduced a bug.
    • The TPM firmware or UEFI firmware is slightly out of sync with Windows expectations.
    • There’s a driver mismatch or TPM provisioning issue.

 

Steps to Reduce or Eliminate the Error

 

Clear TPM via Windows (non-destructive):

  • Go to Settings > Privacy & Security > Device Security > Security Processor Details > Security Processor Troubleshooting.
  • Click Clear TPM.
  • Your system will reboot. This does not erase your data but may reset TPM-stored keys (BitLocker users should suspend protection first).

 

Update BIOS and TPM Firmware:

 

Run Windows Security Health Check:

  • Open Windows Security > Device Security > Core Isolation.
  • Ensure Memory Integrity is enabled.
  • Run System File Checker:
    sfc /scannow
    from an elevated Command Prompt.

 

Optional – Check for Known Conflicts:

  • If the issue started after a specific update (like KB5058379), you may temporarily uninstall it via:
    • Settings > Windows Update > Update History > Uninstall Updates.

 

Should You Worry?

  • If your system is stable, boots normally, and BitLocker or Secure Boot are functioning, this error is mostly cosmetic.
  • However, keeping firmware and Windows fully updated ensures long-term stability.

 

 

If my response helped, please mark it as an Accepted Solution It helps others and spreads support. 💙 Also, tapping "Yes" on "Was this reply helpful?" makes a big difference! Thanks! 😊

 

Take care, and have an amazing day!

 

Regards, 

Hawks_Eye

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.

View solution in original post

3 REPLIES 3
HP Recommended

Hi @eddie11013 

 

Welcome to the HP Support Community! We're here to help you get back up and running.

 

You're seeing TPM-WMI 1796 errors despite Secure Boot being enabled because the issue likely stems from a recent Windows update or firmware interaction—not from your BIOS settings.

 

Here’s a clear breakdown of what’s happening and how to address it:

 

What the TPM-WMI 1796 Error Means

  • Event ID 1796 typically logs:
    “The Secure Boot update failed to update a Secure Boot variable with error Unknown HResult Error code: 0x800700c1.”
  • This error is triggered when Windows attempts to update Secure Boot variables via TPM but encounters a failure—often due to firmware communication issues or TPM driver inconsistencies.

 

Why You’re Seeing It Even Though Secure Boot Is Enabled

  • Your BIOS shows Secure Boot is enabled, and TPM is active, which is correct.
  • However, Windows may still fail to update Secure Boot variables if:
    • A recent Windows update (like KB5058379) introduced a bug.
    • The TPM firmware or UEFI firmware is slightly out of sync with Windows expectations.
    • There’s a driver mismatch or TPM provisioning issue.

 

Steps to Reduce or Eliminate the Error

 

Clear TPM via Windows (non-destructive):

  • Go to Settings > Privacy & Security > Device Security > Security Processor Details > Security Processor Troubleshooting.
  • Click Clear TPM.
  • Your system will reboot. This does not erase your data but may reset TPM-stored keys (BitLocker users should suspend protection first).

 

Update BIOS and TPM Firmware:

 

Run Windows Security Health Check:

  • Open Windows Security > Device Security > Core Isolation.
  • Ensure Memory Integrity is enabled.
  • Run System File Checker:
    sfc /scannow
    from an elevated Command Prompt.

 

Optional – Check for Known Conflicts:

  • If the issue started after a specific update (like KB5058379), you may temporarily uninstall it via:
    • Settings > Windows Update > Update History > Uninstall Updates.

 

Should You Worry?

  • If your system is stable, boots normally, and BitLocker or Secure Boot are functioning, this error is mostly cosmetic.
  • However, keeping firmware and Windows fully updated ensures long-term stability.

 

 

If my response helped, please mark it as an Accepted Solution It helps others and spreads support. 💙 Also, tapping "Yes" on "Was this reply helpful?" makes a big difference! Thanks! 😊

 

Take care, and have an amazing day!

 

Regards, 

Hawks_Eye

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.

HP Recommended

Sorry for the late reply.  Your answer went to my 'spam' folder, since fixed.  Your answer resolved my issue.

Thank you

HP Recommended

Thanks for the update @eddie11013

 

You're very welcome—I'm glad to hear the issue is resolved! And no worries at all about the delay; it happens. 

 

If anything else crops up, TPM-related or otherwise, I’ll be here to help you sort it out.

 

You're awesome, and I'm honored to have been your go-to guide! 😊

 

Stay fantastic, and have an amazing day ahead! 

 

Regards, 

Hawks_Eye

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.

† 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>.