Solved Event Log Error TPM-WMI Event ID: 1796

bo elam · Sep 28, 2025

Hi @zbook The picture below confirms again that Secure boot is On.

Zbook, there is nothing wrong with my computer or most computers that are getting this 1796 error. The problem is the method that Windows updates uses to confirm if Secure boot is On or not. Their method is faulty. Their method is OK with most systems but not all. If Windows updates read that Secure boot was On in my computer, it would update whatever it tried to update. The update fails because WU thinks my computer don't have Secure boot On.

Yes, I have been reading and following the Did you manually update thread.

Thanks for the HP link about Secure boot. It is a good link and I ll save it. It is very confusing, but very good link to keep.

I thought about opening the thread at the HP forum, but I wanted to hear from other HP users before doing so.

By the way, I did run the Hardware test last night. I had to download and install the program. And uninstalled the program after running the test. Scans annoy me. See the results below. So you know, the Hardware diagnostics tool, includes the UEFI diagnostic tool also. I almost click to run it by mistake. That would have been a disaster.

Thank you, you have been very kind. I certainly appreciate your help and don't take it for granted.

Bo

zbook · Sep 28, 2025

The writer of the V2 script is Spectrum and I've not seen him in the forums for years.

In the opening you commented that you had ran Garlin's script.

If Garlin is available to comment this is the script from V2:

Code:

# Confirm if UEFI is enabled and if SecureBoot is enabled
    $FirmwareType = Get-FirmwareType

    # If the system is not using UEFI secureboot is not enabled as it is a UEFI-specific feature
    If ( $FirmwareType -ne "UEFI" )
    {
        $SecureBoot = "Not Enabled"
    }

    Else
    {
        $ErrorActionPreference = 'SilentlyContinue'
        $SecureBoot = Confirm-SecureBootUEFI | Out-Null
        $ErrorActionPreference = 'Continue'

        If ( $SecureBoot -eq $True )
        {
            $SecureBootStatus = "Enabled"
        }
        Else
        {
            $SecureBootStatus = "Not Enabled"
        }
    }

    $FirmwareInfo =
    [PSCustomObject]@{
        "Safe Mode"    = $SafeMode
        "FastStartup"  = $FastStartup
        "FirmwareType" = $FirmwareType
        "SecureBoot"   = $SecureBootStatus
    }

    Return $FirmwareInfo
}

Each HP computer may have different BIOS menu features.

HP has access to each model's menu.

Approximately 15 - 20 years ago I'd moved from HP consumer to HP business support.
They offered whatever handholding was needed.
And they regularly asked for feedback.
The HP business support was excellent.
Hopefully HP consumer support has improved.

bo elam · Sep 28, 2025

@zbook The script Garlin arranged/fixed for my case use was to check the certs that are right now in my computer. The picture in the opening post is the result of running his script. It also shows Secure boot as On. This was done in the "Did you manually update ...." thread.

My W7's were HP, they were good. I have been visiting their website every day since I discovered this error (remember I was not aware of the error because I visited Event viewer for the first time in this computer after using the computer for about 45 days). I have been looking for any kind of information from HP regarding the Secure boot issue and there is nothing. I seen BIOS updates from other brands that mention the Secure boot issue. But from HP, nothing. The BIOS update I did about 4 days ago, had not a word about Secure boot. Their forum. I have been lurking. Nothing. Not one thread I seen about Secure boot. Is like the issue doesn't exist.

Thanks brother zbook

Bo

zbook · Sep 28, 2025

You're welcome.

When you've got a solution please follow up.

bo elam · Sep 28, 2025

I ll let you (

) know when I create a thread at the HP forum.

Bo

bo elam · Sep 30, 2025

I have an advice for anyone thinking of buying a new computer. Don't buy it yet. Wait, wait at least until January 2027. That way you ll know for sure your computer will boot out of the box. HP and other manufacturers are being quiet about this issue. They are quiet because they think it will cost them sales if they were open with customers about the Secure boot issue. What they don't realize is that some of us are watching them and how they proceed. And if they don;t handle this issue well, it will cost them more money in the long run.

For example. My W10 is Dell. I bought it new in 2017 and their last BIOS update was in 2020. I am not only looking at HP, I am also looking at how Dell treat their customers regarding this issue. If Dell or HP abandon customers, I won;t buy from them again, ever.

Every day now I am searching Google for this TMP WMI Error 1796, and this thread is showing up in the search results. So, people will read this thread and my advice. Hopefully, and I think someone from HP will also read it. In case they are and if they care, HP, this is what I bought and booted for the first time on August 6:

HP All-in-One 24-cr0055m PC, Windows 11 Home, 23.8", AMD Ryzen™ 5, 16GB RAM, 1TB SSD, FHD, Jet black

Is a nice computer. For me. But I shouldn't have to be spending time searching for answers. I shouldn't be spending time searching Google, I should be enjoying using the computer not looking for fixes for a new computer. HP knows about this issue for at least 2 years. New computer should come set to go. I haven't worried about anything related to computers since 2008. My time using a computer since that year has been a breeze, until now. So, new buyers, be aware.

Bo

Alan Smithee · Sep 30, 2025

I have this error in event viewer on my HP Omen 17'' notebook (bought three years ago) since 24h2 update

UPDATE
I read carefully this thread and the suggestion in post n. 2 by FerchogtX fixed the error for me also (I applied the solution by suatcini54 in this thread Did you manually update your Secure Boot Keys ?
runnning the following commands in powershell, one at a time:

Set-ItemProperty -Path “HKLM:\SYSTEM\CurrentControlSet\Control\SecureBoot” -Name “AvailableUpdates” -Value 0x40

Start-ScheduledTask -TaskName “\Microsoft\Windows\PI\Secure-Boot-Update”

and restarting the laptop twice).

The error seems to be gone from event viewer

bo elam · Sep 30, 2025

Alan Smithee said:
I have this error in event viewer on my HP Omen 17'' notebook (bought three years ago) starting from 24h2 update

We are not alone brother. Good to know that it started when you updated to 24h2.

Bo

bo elam · Sep 30, 2025

@zbook I remembered something. There is actually one thread in the HP forum about the 1796 error. It is from about 4 or 5 months ago. The OP wanted to know what to do and said that he was concerned about June 2026. The moderator basically told the OP to relax and not to worry about it. That does not relaxes me at all but that's what he said.

Bo

bo elam · Sep 30, 2025

Alan Smithee said:
UPDATE
I read carefully this thread and the suggestion in post n. 2 by FerchogtX fixed the error for me also (I applied the solution by suatcini54 in this thread Did you manually update your Secure Boot Keys ?
runnning the following commands in powershell, one at a time:

Set-ItemProperty -Path “HKLM:\SYSTEM\CurrentControlSet\Control\SecureBoot” -Name “AvailableUpdates” -Value 0x40

Start-ScheduledTask -TaskName “\Microsoft\Windows\PI\Secure-Boot-Update”

and restarting the laptop twice).

The error seems to be gone from event viewer

That is pretty simple, I think. Confirm this. You ran the PS scripts and rebooted twice. And after the second reboot, the error went away.

Bo

Alan Smithee · Sep 30, 2025

Consider to do what is suggested in this thread Did you manually update your Secure Boot Keys ? running the two PS commands.
This worked for me even if boot keys was already updated on my laptop

Alan Smithee · Sep 30, 2025

bo elam said:
That is pretty simple, I think. Confirm this. You ran the PS scripts and rebooted twice. And after the second reboot, the error went away.

Bo

Yes, exactly. Idid that some minutes ago after stumbled on this thread

bo elam · Sep 30, 2025

Alan Smithee said:
Yes, exactly. Idid that some minutes ago after stumbled on this thread

Alright, I ll give it a shot and bback in a little while. Thanks.

Bo

bo elam · Sep 30, 2025

Great news. Running the 2 scripts fixed the error for me. Look below. That covers the two reboots. It looks like the error was cleared after the first reboot as it doesn't show up after the first reboot.

One thing the scripts did not do is update certs. My certs look identical as in the picture I attached in post #1. @Alan Smithee Are certs in your HP the same as I have them in that picture.

Bo

bo elam · Sep 30, 2025

FerchogtX said:
That's right, I did the commands, and the error stopped happening in my Event Viewer. That's why I thought it would help you even if you had the certs installed already.

They sure did help @FerchogtX Thank you.

Bo

DarkShadowMD · Sep 30, 2025

Yer most welcome my dude

bo elam · Sep 30, 2025

FerchogtX said:
Yer most welcome my dude

I am going to mark this thread as Solved (thanks to you and Alan and everyone else including zbook, etc, who put effort to help) as the error seems to be gone, it was not triggered or generated today after cold starting the computer. I don't see any change in the status of the certificates in my W11 but I think they are right now where MS wants them to be at this point in time. Does the status of the certs in your HP look like in mine? You can compare yours to mine as they are right now as they were when I posted the picture of the certs in the opening post.

Bo

DarkShadowMD · Sep 30, 2025

In my case, I only have one CA 2023 Cert installed, apparently the rest are not needed or something makes them not available to me. Might be a BIOS update that I need on my HP at least. I havent tried this on any of my desktops, because they have no event viewer errors, and hopefully, updating the certs on them will be less painful than in my HP lol.

bo elam · Oct 1, 2025

FerchogtX said:
In my case, I only have one CA 2023 Cert installed, apparently the rest are not needed or something makes them not available to me. Might be a BIOS update that I need on my HP at least. I havent tried this on any of my desktops, because they have no event viewer errors, and hopefully, updating the certs on them will be less painful than in my HP lol.

I read your posts in another thread about your BIOS update that is available for your HP. Last week I updated my BIOS in the HP. I know how you feeling about your BIOS updates, HP doesn't make the process seamless. My HP computer comes with two different processors, one is AMD, like mine, and another model comes with Intel processors. In the Software updates page for my model there are 2 BIOS updates and they are not clearly marked so you really don't know (easily) which one is for the version with the AMD processor and which one is for Intel or Gigabite. Later I found that the one that is not for my model is Gigabyte, where GB comes from in all this I have no idea.

But anyway, I reinstalled HP Support Assist just because I wanted make sure I installed the correct BIOS. I had a clue, in System information, BaseBoard product shows the numbers 8B4E, and that number was in the BIOS information of one of the updates. Afterward, I searched for updates with HPSA and it also came up with that update. So, I installed it feeling 100% sure that I was installing the correct update. But is not easy. Two months ago when I got this computer, I visited that page before uninstalling HPSA, and one of the BIOS updates at the time, showed AMD in the information about the update. Why they changed that to how they have it now, I don't know but is not good.

I know HPSA has a BIOS update for you, I think you should install it. When I installed mine, I thought that the update was going to clear the 1796 error and/or do the update that according to the description of the error MS was trying to do but couldn't do. Neither happened. Perhaps this error is a typical Event viewer error. Whenever and whatever I see in there, I always remember the Cry wolf fable and the moral of the story. And perhaps this is one that fooled me. I should have ignored it.

Bo

zbook · Oct 1, 2025

bo elam said:
Hi @zbook The picture below confirms again that Secure boot is On.

View attachment 146923

Zbook, there is nothing wrong with my computer or most computers that are getting this 1796 error. The problem is the method that Windows updates uses to confirm if Secure boot is On or not. Their method is faulty. Their method is OK with most systems but not all. If Windows updates read that Secure boot was On in my computer, it would update whatever it tried to update. The update fails because WU thinks my computer don't have Secure boot On.

Yes, I have been reading and following the Did you manually update thread.

Thanks for the HP link about Secure boot. It is a good link and I ll save it. It is very confusing, but very good link to keep.

I thought about opening the thread at the HP forum, but I wanted to hear from other HP users before doing so.

By the way, I did run the Hardware test last night. I had to download and install the program. And uninstalled the program after running the test. Scans annoy me. See the results below. So you know, the Hardware diagnostics tool, includes the UEFI diagnostic tool also. I almost click to run it by mistake. That would have been a disaster.

View attachment 146929

Thank you, you have been very kind. I certainly appreciate your help and don't take it for granted.

Bo

The Windows hardware testing reported all passes.

It did not test all components (RAM).

When running the HP UEFI hardware diagnostics it's best to run the testing overnight while sleeping.

The UEFI hardware testing was designed to abort testing and may report only some test results when it detects a malfunctioning component.

When there is a failure to boot Windows the HP UEFI hardware diagnostics can typically run to potentially rule in / out malfunctioning hardware.

If the UEFI hardware diagnostics runs then the test results are typically stored and can be compared to the Windows hardware diagnostics.

The other differences are some of the component tests.

Solved Event Log Error TPM-WMI Event ID: 1796

Active member

My Computer

Well-known member

My Computer

Active member

My Computer

Well-known member

My Computer

Active member

My Computer

Active member

My Computer

Well-known member

My Computer

Active member

My Computer

Active member

My Computer

Active member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Active member

My Computer

Active member

My Computer

Active member

My Computer

Peaceful Citizen

My Computers

Active member

My Computer

Peaceful Citizen

My Computers

Active member

My Computer

Well-known member

My Computer

Similar threads