Solved garlin's PowerShell scripts for updating Secure Boot CA 2023

anchamp65 said:

I would still use Rufus for everything except 2023 certs, simpler then command line or registry fixes.
Then use Garlin's check with -bootmedia and -noskip so it checks all install images
Then use Garlin's update with -bootmedia
And rerun check with -bootmedia and -noskip to see if they all got fixed

I would try this first...

I would test it myself, but no time to do all this today or this week-end...

Click to expand...

Monika1491 said:

Yes, you can manually add the latest cumulative update to the latest iso file and then use Rufus.

Use AI to get information instead of Google.

Notes:

1)
It is best to download the June official original MVS iso (26200.8655) from Microsoft (Not the one from Microsoft's public website.).
SVN 9 already has that. A trusted unofficial source is also suitable.

2)
MCT/ESD is also suitable.
ESD is usually up to date on Thursday, two days after the release of CU (B).
This month, however, Microsoft released an ESD with an unofficial CU (CU B = revision 8655, ESD = revision 8653). If that doesn't bother you, create ISO using MCT.
I haven't verified that SVN 9 is there, but I'm guessing it is.

3)
If you are not able to find out information on how to update wim using dism, do not do it, it is not suitable for you.
The ready-made script (W10UI) is more suitable for you, but you wrote that you do not want to use it.

Click to expand...

iFX_Legacy said:

Thank you again,

1)
I assume that I need an MVS subscription to get the iso from microsoft? or is this avaialble to the public?

2)
My iso is freshly downloaded so I believe they are still using SVN 7.0 on the weird ESD. This would hav ebeen the preferred route as its easy enough to do. I'm assuming using MCT or downloading the iso from the windows 11 download site will ge tthe same version of teh file? I usually just grab the iso from there.

3)
A lot of the information is using older files and older versions of windows...It doesnt seem overly complicated. My preference is not to use 3rd party links and sources, but if I have no choice but to do it this way....so be it.... you are suggesting that the dism process is very complex?


thank you again, I'm still uncertain why your original post was deleted....

Click to expand...

Monika1491 said:

1)
MVS iso is not publicly available. Subscription required.

2)
There is an iso from March on the public website.
But MCT uses June revision 8653 ESD.
To be safe, download the current MCT and create an ISO using the MCT.
There is probably SVN 9 there, try it .-)
Edit, I just checked:
MVS iso (revision 8655) and MCT iso (ESD revision 8653) have binary identical bootmgfw_EX.efi files and since MVS iso is SVN 9...

3)
Dism process is not very complex.

Click to expand...