Event details
202 Comments
- Heather_Poulsen
Community Manager
Welcome to today's Secure Boot AMA! We'll start with the questions posted in advance below, but keep them coming and we'll do our best to help.
Hi
question:
Lets say I will update our cert via Intune or Registry keys. What will happen if I will have to reset UEFI for some reasons?
Will the new cert stay or I will have to install them again?Can you confirm please, is event ID 1808 absolute confirmation that the certs are all in place and there's nothing left to do. Thanks.
- Mabel_Gomes
Microsoft
Yes, correct. Event ID:1808 confirms that the device has the required new Secure Boot certificates applied to the device’s firmware and there is no other action required in this certificate update process.
I can say Event ID 1808 is not absolute confirmation. I have seen systems have the cert and not have that EventID
- Mabel_Gomes
Event ID 1808 used to be logged on every startup. As a result, if Boot Manager or certificates were updated after the device had already booted, Event ID 1808 would not appear until the next restart.
Starting with the April 2026 Windows security update, this behavior has changed. Event ID 1808 is now logged a soon as the update is applied.
What telemetry level should we have set in our org for the certs to properly install? Currently we have them set to blocked here and I know that is wrong, but I'm unsure what would be correct for this case. Is there any sort of guidance available for this?
Answered twice in the video, basic/recommended telemetry is enough if you want to take part in the CFR process. In case your machines are managed, in addition to enabled telemetry, you also need to set the Managed Device Opt In so that you take part in CFR. If you don't take part in CFR, you will get the certificates only for High Confidence devices via the LCU.
I got to the report in Intune, but is there a way to get better data besides yes/no, not applicable? the results appear to be random in nature and not sure if it's properly reporting on secure boot status. I have multiple new computers that were purchased and distributed around the same time and some are and some aren't showing as set to secure boot. I thought this was set on by default these days.
Will Microsoft keep updating the High Confidence list after the 2011 certificates expire for devices that we configure for High Confidence before deploying?
You've mostly answered my question. I was looking for if we need to skip the High Confidence configuration to meet the deadline
I am unsure what deadline you are talking about. Depending on what devices you are using, not all of them may become High Confidence by June. So if you want to make sure to have those devices updated, you need to manually push the updates.
On a Hyper-V host, regarding the certificate update process, is there an order to do things in meaning does it matter if the secure boot certificate update process is started first on the host and does the host need to be fully updated before starting the VMs? I am aware of the requirements of the firmware needing to be up to date and at least the March updates being installed on both the host and VMs. Thank you.
Answered at 14:30 in the video.
Secure Boot process is completely separate between Guest and Host, the order does not matter.
To enable secure boot on the host, the host needs to be powered down. This will obviously prevent the VMs from still running, but it does not matter whether they are shut down or paused.
I'm curious about an updated ADK as well as official guidance on how to address PXE w/ WDS:
"A new checkbox, Use Windows Boot Loader signed with Windows UEFI CA 2023, is available in the Data Source tab of boot image properties. When enabled, it updates the boot image to use the boot loader signed with Windows UEFI CA 2023. The checkbox automates the mitigation steps described in KB5025885.
The new functionality only works on WDS-Less PXE-enabled Distribution Points."
???
Yes, please assist!
On the Intune Secure Boot Status Page - https://intune.microsoft.com/#view/Microsoft_EMM_ModernWorkplace/SecureBootReport.ReactView - all of my 900+ devices are showing as Certficate Status = "not applicable".
3rd party scripts are helping to confirm that updated certs are in place on my devices, but I would like to see the official status page working properly.
What are the pre-requsite factors needed in order to make this report on our devices provide accurate statuses on my laptops?+1 for this, we have some of those too
What do I have to do to get the new certificates to Windows 11 and server ISOs? Will they be integrated in newer ISOs in the near future or do I have to do something manually to add them?
Answered at 5:30 in the video.
One addition, even if they are added to the ISO, this does not mean they will update any "leftover" devices during the installation phase. It only means that those media can boot from machines that do not trust the old certificates any longer.
