With the optional update from October 28 (KB5067036), Microsoft introduced a CLI tool for the WinCS API. Install https://support.microsoft.com/en-us/topic/windows-configuration-system-wincs-apis-for-secure-boot-d3e64aa0-6095-4f8a-b8e4-fbfda254a8fe
Now install this PowerShell-Module:
Install-Module UEFIv2 -Force
You can list now the certificates:
Get-UEFISecureBootCerts db | select SignatureSubject
Get-UEFISecureBootCerts kek | select SignatureSubject
Certificates which are updated are listed here:
https://support.microsoft.com/en-us/topic/windows-secure-boot-certificate-expiration-and-ca-updates-7ff40d33-95dc-4c3c-8725-a9b95457578e
WinCsFlags is going to update ALL FOUR certificates listed. Also the one stored in KEK.
Now set the update configuration:
WinCsFlags.exe /apply --key "F33E0C8E002"
Now, run the Scheduled Task Secure-Boot-Update.
Start-ScheduledTask -TaskName "\Microsoft\Windows\PI\Secure-Boot-Update"
Reboot twice and check again for the certificates and the Event-Log.
If all is updated, you can set back the update configuration:
PS:
After validating the new values, a change to the former is not required!
As each value defines a state, and not a action.
WinCsFlags.exe /apply --key "F33E0C8E001" is NOT required afterwards.
F33E0C8E001 (State: Disabled):
This is the default state on a system. It indicates that the update for the new Secure Boot certificates is paused or disabled. The system continues to use the old certificates.
F33E0C8E002 (State: Enabled):
This key signals the Windows Configuration System (WinCS) to write the new 2023 certificates (such as Windows UEFI CA 2023) to your motherboard's firmware and to update the boot manager.