Event details
Ask Microsoft Anything (AMA) about updating Secure Boot certificates on your Windows devices before they expire in June of 2026. We recently published the first version of the Secure Boot playbook, outlining the tools and steps you can take today to proactively plan and prepare for this milestone. Join this AMA with your questions about update scenarios, inventorying your estate, and formulating the right deployment plan for your organization.
On the panel: Arden White; Scott Shell; Richard Powell, Kevin Sullivan
How do I participate?
Registration is not required. Simply select Add to calendar then sign in to the Tech Community and select Attend to receive reminders. Post your questions in advance, or any time during the live broadcast.
Get started with these helpful resources
113 Comments
- FailedSuccessfullyOccasional Reader
starting from what OS build are the Secure Boot certificates renewed?
- prabhv1982
Microsoft
Renewed secure boot certificates are applicable for all Secure Boot enabled devices. Latest windows cumulative updates include the renewed certificates. Refer to https://aka.ms/getsecureboot on how to safely roll out certificates in your environment.
- Vinod7Brass Contributor
How about updating the WinPE boot image for SCCM?
- prabhv1982
Microsoft
This link WinPE: Create bootable media | Microsoft Learn explains how to update WinPE bootable images.
Additional references:
- WinPE: Mount and Customize | Microsoft Learn
- Makewinpemedia Command-Line Options | Microsoft Learn
- BCDBoot Command-Line Options | Microsoft Learn
- Capture and Apply Windows using a WIM file | Microsoft Learn
- https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/oem-deployment-of-windows-de
- lalanc01Iron Contributor
When should we expect the ConfidenceLevel registry to be populated?
Our devices are managed with WUFB, but the key is empty- RayC15Copper Contributor
After ConfidenceLevel is populated, does that mean the update will be triggered on next Windows Update?
- lalanc01Iron Contributor
Any news/eta for Option 4: Deploy certificates using mobile device management (coming soon)?
thks
- lalanc01Iron Contributor
What can we do if a device won't update it's secureboot cert?
We have updated to the latest bios version, released a few months back, set the registry key and started the scheduled task and rebooted multiple times, but the cert is still not updated.
Are there some logs/events that we can look at?
Thks- prabhv1982
Microsoft
Secure boot update failure events are logged in the System Event log under TPM-WMI channel. Refer to Secure Boot DB and DBX variable update events - Microsoft Support for list of Secure Boot event IDs to monitor.
- lalanc01Iron Contributor
How do you recommend that we update our sccm boot images to support those new certificates?
Saw that 2509 can do it for WDS-Less PXE, but what about WDS PXE?
is there an official doc/post mentioning the required steps?
Thks in advance. - jhcdocCopper Contributor
For machines imaged with Win11 Pro Edition and signed into Work accounts that are E5 licensed, using the Intune Settings catalog CSP for Secure Boot, we are seeing the following errors in Event Viewer:
- Event ID 404: MDM ConfigurationManager: Command failure status. Configuration Source ID: (***Omitted***), Enrollment Name: (MDMDeviceWithAAD), Provider Name: (Policy), Command Type: (Add: from Replace or Add), CSP URI: (./Device/Vendor/MSFT/Policy/Config/SecureBoot/EnableSecurebootCertificateUpdates), Result: (Unknown Win32 Error code: 0x82b00006).
- Event ID 809: MDM PolicyManager: Set policy int, Policy: (EnableSecurebootCertificateUpdates), Area: (SecureBoot), EnrollmentID requesting set: (***Omitted***), Current User: (Device), Int: (0x5944), Enrollment Type: (0x6), Scope: (0x0), Result:(0x82B00006) Unknown Win32 Error code: 0x82b00006.
- Event ID 827: MDM PolicyManager: Policy is rejected by licensing, Policy: (EnableSecurebootCertificateUpdates), Area: (SecureBoot), Result:(0x82B00006) Unknown Win32 Error code: 0x82b00006.
- Event ID 2204: Caching uri for blocking mapped GP location. URI: (./Device/Vendor/MSFT/Policy/Config/SecureBoot/EnableSecurebootCertificateUpdates), Operation: (0x0).
- Event ID 2204: Caching uri for blocking mapped GP location. URI: (./Device/Vendor/MSFT/Policy/Config/SecureBoot/EnableSecurebootCertificateUpdates), Operation: (0x0).
Seems after creating the previously non-existent Secure Boot key at Computer\HKEYLOCALMACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\ fixes errors related to deployment attempts of the ConfigureHighConfidenceOptOut_ values, but not the MicrosoftManagedOptIn and AvailableUpdates values:
Using slmgr /dli, noticing the Windows OS edition is Professional, with the Subscription edition of the user account that is E5 licensed as Enterprise:
Created an Intune detection script that also verifies the same OS edition in-relation to CSP failures (Event 827, etc.):
Does the Secure Boot CSP require Enterprise OS edition, rather than just Win11 Enterprise subscription from the user account context?
If so, does this then mean we would need to upgrade the OS edition using the Intune template to Enterprise with a valid key? We are assuming other CSPs will also fail given the OS edition is Pro and not Enterprise.
Thanks for your feedback on this!
- prabhv1982
Microsoft
Is Windows 11 Pro edition where issue is being observed has been updated with latest cumulative updates from Microsoft? If not, request you to update the client devices to latest available Windows updates and retry applying the policies.
- jhcdocCopper Contributor
Our machines are continually updated with Autopatch/Hotpatch, which are up to date. We've tested several up to date machines and see the same errors across the board (Intune deployment error 26000 and Event Viewer error 827 as screenshotted in OP). These machines have been imaged using Win11 24H2 ISO (Pro edition) provided by your software download link for the ISO, then upgraded to 25H2 via Autopatch feature update.
- jzink1495Occasional Reader
If a computer can't be updated for any number of reasons and is using UEFI, can you simply disable the Secure Boot option in BIOS to avoid this certificate issue affecting boot?
- stephc_msft
Microsoft
yes
- PieterrrrmanCopper Contributor
We have been testing a bit and have so far not seen any issues. What I would like to know is whether a report will become available in Intune any time soon so we can monitor the update proces in our organisation...
- HeyHey16KIron Contributor
What qualifies a device as "high-confidence" please?
- Mabel_Gomes
Microsoft
A high-confidence device refers to one that Microsoft can reliably identify and update automatically through Windows Update without additional intervention. These devices typically meet criteria such as:
- Trusted diagnostic data signals confirming the device’s identity and compatibility.
- Secure Boot enabled and using supported UEFI firmware.
- Running a supported Windows version that can receive updates.
- No anomalies in the boot chain or firmware keys that could block the update process.
For devices that don’t meet these conditions (e.g., missing diagnostic data, unsupported OS, or OEM-specific issues), they may require manual validation and rollout steps.
More information here: Secure Boot Certificate updates: Guidance for IT professionals and organizations - Microsoft Support
- mikehartsteinCopper Contributor
I have yet to see a value next to the BucketConfidenceLevel key in the text of the Event ID 1801s in our environment. MS' inventory/discovery script lists several possible values, though...