TPM-WMI ID:1802

Ruscov Vladmir 60 Reputation points
2026-11-19T12:56:24.8+00:00

The Secure Boot update KEK 2023 was blocked due to a known firmware issue on the device. Check with your device vendor for a firmware update that addresses the issue. This device signature information is included here.

DeviceAttributes: FirmwareManufacturer:HP;FirmwareVersion:Q74 Ver. 01.21.01;OEMModelBaseBoard:8470;OEMManufacturerName:HP;OSArchitecture:amd64;

BucketId: 6fd63787af552399f3b9e777ca4e2340c3419b4d5792eb45da80f9d4bfcd7afe

BucketConfidenceLevel: High Confidence

SkipReason: KI_7.

Windows for business | Windows Client for IT Pros | User experience | Session connectivity
0 comments No comments

2 answers

Sort by: Most helpful
  1. Ronald Sabiiti 2,250 Reputation points Independent Advisor
    2026-11-19T13:51:10.36+00:00

    Hi Vladimir,

    This message indicates that Windows has blocked the 2023 Secure Boot KEK update due to a known HP firmware compatibility issue (KI_7).

    Recommended actions:

    • Check HP's website for a BIOS/UEFI update for the affected device.
    • Install any applicable firmware updates following HP's instructions.
    • Restart the device and retry Windows Update.
    • If no update is available, contact HP Support for confirmation of the firmware issue.

    Avoid forcing the Secure Boot update or disabling Secure Boot.

    Reference: Microsoft Secure Boot troubleshooting guide.

    Hope this helps!

    Ronald

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

  2. AI answer

    2026-11-19T12:57:26.0633333+00:00

    Install the latest HP BIOS/UEFI firmware offered for the computer’s exact product number; until HP provides firmware that resolves KI_7, leave Secure Boot enabled and do not force the KEK 2023 update.

    TPM-WMI Event ID 1802 means Windows intentionally blocked the update because this firmware configuration matches a known condition in which applying it might fail or cause a more serious problem. It is not evidence of a defective TPM, and clearing the TPM will not address the documented block.^1^

    1. Identify the exact HP product
      • In Windows, open System Information (msinfo32).
      • Record System Model, System SKU, and BIOS Version/Date.
      • Do not select firmware solely from baseboard 8470 or BIOS family Q74; use the computer’s exact HP product number or serial number.
    2. Check HP’s official support page for that product
      • Look under BIOS or Firmware.
      • Compare the available release with the installed Q74 Ver. 01.21.01.
      • Review its release notes for Secure Boot, certificate, KEK, DB/DBX, or UEFI fixes.
      HP states that support for the new certificates is primarily available for Secure Boot-enabled commercial PCs released in 2019 or later and selected 2018 products. Older or end-of-service systems might not receive a compatible update.^2^
    3. If a newer applicable BIOS exists
      • Install it using HP’s instructions while connected to reliable AC power.
      • Do not interrupt the firmware update.
      • Restart Windows normally and install all available Windows security updates.
      • Allow the built-in Secure Boot servicing process to retry automatically.
    4. Check whether HP identifies the platform as prepared Run this in PowerShell:
         $system = Get-CimInstance -ClassName Win32_ComputerSystemProduct
         [pscustomobject]@{
             ProductName = $system.Name
             ProductID   = $system.IdentifyingNumber
             HPVersion   = $system.Version
             HasSBKPFV3  = $system.Version -match 'SBKPFV3'
         }
      
      HP indicates that systems not reporting SBKPFV3 require an applicable HP BIOS update before Windows can stage the new certificates.^2^

    Verify the result

    Open Event Viewer → Windows Logs → System, then filter the current log for source TPM-WMI.

    • Success: Event 1043, “Secure Boot KEK update applied successfully.”
    • Still blocked: Event 1802 continues to report KEK 2023 and SkipReason: KI_7.

    The BucketId identifies equivalent device configurations and can change after a firmware update. The important result here is whether Event 1802 stops recurring and the KEK success event appears.^1^

    If HP offers no newer compatible firmware

    • Do not manually inject Secure Boot keys, change AvailableUpdates to bypass the safeguard, reset Secure Boot keys, or clear the TPM.
    • Keep Secure Boot enabled and continue installing normal Windows and HP updates.
    • Contact HP with the exact model, product number, BIOS Q74 01.21.01, BucketId, and SkipReason: KI_7.
    • If HP confirms that the model is unsupported, document it as a firmware limitation. Microsoft’s administrative guidance says devices blocked by a known issue should not receive forced certificate deployment; administrators should monitor OEM firmware availability and Event ID 1802.^3^

    The displayed High Confidence value does not make overriding this specific Event 1802 safeguard appropriate—the event explicitly records that Windows blocked this KEK operation for the identified firmware condition.


    References

    1. Secure Boot DB and DBX variable update events | Microsoft Support
    2. HP Business PCs - Prepare for new Windows Secure Boot certificates | HP® Support
    3. Secure Boot status report in Windows Autopatch
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.