Event 1796 TPM-WMI

I've noticed after updating today with the latest Windows update that after boot up I get at least one of these in the event log after every boot.

"The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931"

Now, assuming the TPM is referring to an actual TPM module, I do not have one of these. Nor, as it states, do I have secure boot enabled. I've never had this event turn up at any point in the past so I'm confused as to why I'm getting it now. The link doesn't help me out as all I'm wanting is to turn off needless error reports such as this.

Is this an event not worth worrying over, so I can possibly even hide disable it from being logged and clogging up my event viewer, or is there a good reason I'm being notified of something that doesn't affect me?

In the Search box,start typing ---reliability ---and access Reliability History.
If there aren't red flagged entries for event id 1796,then ignore it.
A completely error free PC does not exist in the practical world.
Updates are more general than specific,with respect to PCs.

Oh good. Nothing's come up in reliability history so I shall take the ignore it advice aha

Cheers for the reply! Just thought I'd check.

Getting the same crap. I have secure boot totally disabled on purpose, so this is annoying as ****. I'm trying to find out what service, sch task, etc. etc. etc. is trying to "update secure boot" in the first place, so I can nuke it.

"The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine."

joeandmarg0 said:

A completely error free PC does not exist in the practical world.

Mine actually was, except the occasional, yellow, informational DCOM message. Now this...

Background info why you're getting these events: Microsoft Updating Windows Secure Boot Keys in 2024

I got this error upon reboot today as well.

I also started getting this error everytime I boot up my PC after the windows update around April 15th, did you ever find a fix or reason why this was happening? I never had this error before that windows update

I'm beginning to see a lot of reports emerging about this. From what I read, I'm guessing that Microsoft's algorithm to determine which devices are OK to implement the Secure Boot update is possibly faulty.

What's worrying is that there are reports of BSODs and 'failures to boot' as well as the Event ID 1796 errors reported in this thread.

One thing that is fairly consistent is agreement that an out-of-date BIOS/UEFI may be a cause. As a result, it appears important, when posting about Event ID 1796 errors, to also include the following information:

1. Make/model of your device.
2. BIOS/UEFI date.
3. Whether your device uses UEFI or Legacy BIOS mode to boot.
4. If UEFI mode, whether Secure Boot is enabled.

This may make it easier to see whether there are one or more common factors to this issue.

Additional info: It is very easy to use PowerShell to provide most of the info.

To start, do this:
1. Right-click on the Start button and select Windows PowerShell (Admin) from the context menu.
2. When the PowerShell console opens, copy/paste or type the following commands then press the ENTER/RETURN key.

BIOS/UEFI date?

Code:

(Get-Ciminstance  -Class "Win32_BIOS" -Namespace "ROOT\CIMV2").BIOSVersion

This should show you the date of your BIOS/UEFI firmware. For example:


Firmware Boot Mode?

Code:

Write-Host 'The mainboard''s firmware mode is:'$env:firmware_type

This will show you what 'mode' your device boots in. For example:


Secure Boot status, e.g. is this enabled?

Code:

Confirm-SecureBootUEFI

This will give one of 3 results:

If the computer supports Secure Boot and Secure Boot is enabled, this cmdlet returns $True.
If the computer supports Secure Boot and Secure Boot is disabled, this cmdlet returns $False.
If the computer does not support Secure Boot or is a BIOS (non-UEFI) computer, this cmdlet displays the following:
Cmdlet not supported on this platform.

For example:


Make a note of the results and use them in any further posts. For example:

Make/model of your device: Dell Latitude E7450
BIOS/UEFI date: DELL - 1072009 BIOS Date: 12/26/16 20:26:34 Ver: A15.00
Firmware Boot Mode: The mainboard's firmware mode is: Legacy
Secure Boot status: Cmdlet not supported on this platform: 0xC0000002

Hope this helps...

I also started to get this error after 4/9/24 update and my windows 10 pc's mb is not secure boot optional. It does have uefi but not secure boot; the only way I could figure out to stop error was uninstall update dut don't want to really do that. Is there another work around to stop the logging or will it affect my pc at all, thanks.