Using bcdboot after revocations

Jim Whitaker 66 Reputation points
2024-08-08T02:04:19.9733333+00:00

I completely did the revocations from here:

https://support.microsoft.com/en-us/topic/kb5025885-how-to-manage-the-windows-boot-manager-revocations-for-secure-boot-changes-associated-with-cve-2023-24932-41a975df-beb2-40c1-99a3-b3ff139f832d#bkmk_mitigation_guidelines

I next (to experiment) recreated my system partition, formatted, etc. Normally (prior to revocations),

the following code would restore boot of course I used assign letter=S

bcdboot C:\windows /s S: /f UEFI

It did not boot, I got the secure boot warning.

So next I ran these in order from the revocations KB article:



COPY D:\EFI\MICROSOFT\BOOT\BCD D:\EFI\MICROSOFT\BOOT\BCD.BAK

bcdboot c:\windows /f UEFI /s D: /bootex

COPY D:\EFI\MICROSOFT\BOOT\BCD.BAK D:\EFI\MICROSOFT\BOOT\BCD

I did substitute S: instead of D: This time it booted normally.

Now my question, is the method I used fine to repair the system (esp) partition once revocations have been applied?

And one more question, will a major Windows 11 update mess with the revocations or booting?

Of course I restored the whole drive after experimenting, I use Macrium Reflect.

Windows for business Windows Client for IT Pros User experience Other
0 comments No comments
{count} votes

Accepted answer
  1. S.Sengupta 24,476 Reputation points MVP
    2024-08-09T01:46:30.33+00:00

    Now my question, is the method I used fine to repair the system (esp) partition once revocations have been applied?

    Yes.

    And one more question, will a major Windows 11 update mess with the revocations or booting?

    Best practice will be creating a System Restore Point, so that if any mess happens you could always go back to normal state.

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.