docs: add EFI Secure Boot page covering the 2023 CA transition

Document the two Microsoft-signed loader sets and their firmware db requirements, the EfiBootLoader diagnostics registry key, and the BIOS third-party certificates option needed on machines that ship with a 2023-only Secure Boot configuration.

Explain why the Windows Secure Boot certificate rollout does not trigger automatically on system-encrypted machines, how to trigger it via the documented AvailableUpdates registry value, the precautions to take, and the recovery procedures when Secure Boot blocks the boot chain.

Link the page from the System Encryption documentation and the CHM table of contents.
This commit is contained in:
Mounir IDRASSI
2026-07-07 17:49:34 +09:00
parent 7f24d98db2
commit d773ce95e6
21 changed files with 607 additions and 5 deletions
+4
View File
@@ -52,6 +52,10 @@
<param name="Name" value="Îïåðàöèîííûå ñèñòåìû, ïîääåðæèâàþùèå ñèñòåìíîå øèôðîâàíèå">
<param name="Local" value="Supported Systems for System Encryption.html">
</OBJECT>
<LI> <OBJECT type="text/sitemap">
<param name="Name" value="EFI Secure Boot">
<param name="Local" value="EFISecureBoot.html">
</OBJECT>
<LI> <OBJECT type="text/sitemap">
<param name="Name" value="Äèñê âîññòàíîâëåíèÿ VeraCrypt (Rescue Disk)">
<param name="Local" value="VeraCrypt Rescue Disk.html">
+1
View File
@@ -69,6 +69,7 @@ Defragmenting.html
Digital Signatures.html
Disclaimers.html
Documentation.html
EFISecureBoot.html
Encryption Algorithms.html
Encryption Scheme.html
FAQ.html