In connection with a vulnerability in Secure Boot 2020, Microsoft introduced a DBX block list in 2022. We reported on it. This has now been expanded. Until now, only event ID 1033 was logged for the event viewer. The list is valid for Windows 10, Windows 11 and servers from 2012.
“To ensure the security of Windows devices, Microsoft adds vulnerable boot loader modules to the Secure Boot DBX revocation list (managed in the system's UEFI-based firmware) to override the vulnerable modules. When the updated DBX revocation list is installed on a device, Windows checks whether the system is in a state where the DBX update can be successfully applied to the firmware and reports errors in the event log if a problem is detected. ”
Entries in the event viewer
For some of these entries, Microsoft provides fixes in the “Perform Action” section. As always in the event viewer, an entry is really an error. If there are general problems, it is an advantage to first look at the reliability history. But here is the updated list:
- Event ID 1032 – This event is logged when BitLocker is configured on the system drive such that applying the Secure Boot DBX list to the firmware would cause BitLocker to enter recovery mode. The solution is to temporarily pause BitLocker for 2 reboot cycles to allow the update to install.
- Event ID 1033 When the updated DBX revocation list is installed on a device, Windows checks whether the system depends on one of the vulnerable modules to boot the device. If one of the vulnerable modules is detected, the update of the DBX list in the firmware is postponed. Each time the system restarts, the device is rescanned to determine whether the vulnerable module has been updated and whether it is safe to apply the updated DBX list.
- Event ID 1034, 1035 This event is logged when the Secure Boot DBX variable is successfully updated. The DBX variable is used to detrust Secure Boot components and is typically used to block vulnerable or malicious Secure Boot components such as boot managers and certificates used to sign boot managers.
- Event ID 1036 This event is logged when the Secure Boot DB variable is successfully updated. The DB variable is used to grant trust to Secure Boot components and is typically used to trust certificates used to sign boot managers.
- Event ID 1795 When the updated DBX revocation list is applied to the firmware, the firmware may return an error. If an error occurs, an event is logged and Windows attempts to apply the DBX list to the firmware the next time the system reboots.
- Event ID 1796 If the updated DBX revocation list is applied to a device and an error not covered by the above events occurs, an event will be logged and Windows will attempt to apply the DBX list to the firmware at the next system reboot.