This is what I get, I assume I should be fine.
Please download an updated copy of BoScript.bat from:
I didn't manually updates the certs on this machine, but I did manually update two others. After re downloading the script, it seems to work. See below:
You're ready for the revocation step (banning PCA 2011). PCA 2010 is distinctly different from PCA 2011.This is what I get, I assume I should be fine.
PCA 2010 is an older cert, which pre-dates PC's using the 2011 certs. The CA 2023 update process doesn't specifically address PCA 2010 certs, it only cares about CA 2011. CA 2010 falls into a gray area where it should be blocked, but MS doesn't explicitly call for it.
Where are you located? I have the same message you show on your last line.
I'm in PA. Refer to @garlin post #24 in this thread. I re downloaded the script and ran it again, where it now seems to be working. Check my post #25, where it is now working.Where are you located? I have the same message you show on your last line.
Downloaded again from where?
@garlin posted the link in post #24 in this thread. try this link:
www.elevenforum.com
@garlin posted the link in post #24 in this thread. try this link:
Did you manually update your Secure Boot Keys ?
Not sure why my output looks different to everyone else's after running @Sheikh's script. Especially where it's referenced as EFI not UEFI So EFI preceded UEFI. I get it. I get that I am also probably out of luck. PS C:\Users\XXXXX> powershell -nop -ep bypass -f...
I don't know what NTFC stands for.
Apparently, the script is not looking for the case of a split install.wim into install.swm and install2.swm.
Didn't work for me
Did the PowerShell open as Administrator? It needs to have Administrator privileges.
Yes, same error. Same version of PS 7.5.4Did the PowerShell open as Administrator? It needs to have Administrator privileges.
Open in Terminal may not open as Administrator.
View attachment 154376
