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^
Recommended action
- 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.
- 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^
- 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.
- 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
- Secure Boot DB and DBX variable update events | Microsoft Support
- HP Business PCs - Prepare for new Windows Secure Boot certificates | HP® Support
- Secure Boot status report in Windows Autopatch