07-06-2026, 12:19 AM
(06-30-2026, 09:48 AM)Bespoken Wrote:(06-30-2026, 08:43 AM)Epictetus Wrote: So can you make something like this work if you boot using the HBS.ISO from a Ventoy drive? Or if not just turn off Secure Boot?This is uncharted territory as MS only updates the SVN when a vulnerability in the Boot Manager has been fixed. This has not been a common activity. It is possible that an update to Ventoy or HBS is all that may be required. Until these occur you may need to turn off Secure Boot. An alternate may be to use the above to update Ventoy.
We will know better when MS next updates the Boot Manager. It could be months or years.
SVN is always increasing counter stored in your motherboard's UEFI/BIOS (meaning it only ever goes up). If a boot manager file carries an SVN lower than the minimum allowed value in your firmware, the PC will refuse to load it. This stops attackers from replacing updated boot files with older, vulnerable ones.
You have three different SVN which may or may not match depending on if you revoked 2011 cert.
FirmwareSVN <-- UEFI's current value
BootManagerSVN <-- boot manager's current value
StagedSVN <-- latest possible value from \Windows\System32\SecureBootUpdates\DBXUpdateSVN.bin, if you haven't applied revocation or recent Secure Boot updates
You can see all these SVN with the powershell command: Get-SecureBootSVN
The only time you will have a SVN mismatch right now is if you revoke the 2011 cert and as far as Microsoft are concerned you should not be doing that.
The only step Microsoft expects people to be at right now is updated to the 2023 cert.
On the latest update Microsoft extended the expire date of 2011 cert to October 2026.
The last three monthly windows updates have updated the SVN from 7 then 8 and now 9.
All these files are in C:\Windows\System32\SecureBootUpdates
