Secure Boot certificates have been updated but are not yet applied

Wilson T 245 Reputation points
2025-12-09T05:17:43.8733333+00:00

Hello,

User's image

What's this? Do I need to take any action about it or just leave it alone?

Thanks very muchπŸ˜€

Windows for home | Windows 11 | Performance and system failures

Answer accepted by question author
Alexandr S 106.4K Reputation points Independent Advisor
2025-12-09T06:03:24.0433333+00:00

Hello, Wilson T.

If the OS is stable, you can ignore these messages. Judging by the information from the screenshot, they relate to updates from Lenovo (the manufacturer of your PC).

P.S. Even on a fully functional PC and a working OS, there are always similar messages in the Event Viewer. This is the normal behavior of the log collector.

Was this answer helpful?

2 people found this answer helpful.

9 additional answers

Sort by: Newest
  1. Michael Held 25 Reputation points
    2026-07-12T08:35:15.81+00:00

    With some BIOS version like my Dell Optiplex 7050 you first have to empty your certificate memory in your BIOS. Do NOT user Factory Settings => USe DELETE ALL! With this EMPTY certificate memory you can boot your machine in SETUP MODE and Windows will write the new certificates in your BIOS Memory. If it doesn't, use Garlin UEFI Tool from GitHub. I managed to update my machine to the new certs and I'm happy now. btw, the option to delete the certificates in BIOS may only be visible in "Custom Mode" NOT "Standard Mode". Some machines like Acer Aspire even need you to setup a BIOS password to get into Secure Boot Custom Mode and to DELETE ALL certificates. Use an easy password and delete it immed afterwards. All the best to you

    Was this answer helpful?


  2. Dean Wortmier 20 Reputation points
    2026-02-14T19:35:51.6466667+00:00

    STOP!

    May not be an issue. Check your BIOS for your type of boot. If you are using the LEGACY boot, then you're not using the secure boot or the these keys anyway and so updating is NOT necessary. Life goes on, albeit with a once per month error in the event log.

    DO NOT CHANGE from Legacy Boot to Secure Boot because this will require a reinstall of Windows, and I'm pretty sure you don't want to do that.

    Was this answer helpful?

    4 people found this answer helpful.

  3. John Westfield 95 Reputation points
    2025-12-25T20:58:31.54+00:00

    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.

    Was this answer helpful?

    10+ people found this answer helpful.

  4. 2025-12-20T19:23:18.3866667+00:00

    finally i tried it myself and succeeded, for fix that. 1 unistall security on "devices manager" and then restart pc. after back to dekstop windows try open delta force and then not show green screen again.

    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.