Append VAR -> Public Key CertificateSet new KEK or Append Var to KEK?
input file format? which one
My Computer
System One
-
- OS
- Windows 7
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Append VAR -> Public Key CertificateSet new KEK or Append Var to KEK?
input file format? which one
AvailableUpdates is 0x200 or missing the SVN.I wonder a little bit why your script proposes to revoke the PCA2011 cert while it lists the PCA2011 already in the dbx? (Read the latest posts and didn't find that covered. Did I overlook something?)
$UpdateFlags -band 0x200" check and throw out a SVN-only message.I'm not smart like @garlin , but why don't you wipe/reset the keys to factory, reboot and run the script. Every OEM BIOS is a bit different, it may be that in your case, when resetting the keys to factory, it might be throwing your Secure Boot into Setup Mode without you knowing.@garlin I've already done these I don't have option for custom mode
the only option I've is enable or disable the secure boot is always on "UEFI mode", I can only enable or disable.
Look, I've explained the check DBX warnings are because MS recently changed the file format. It doesn't affect the update process.
Don't put the burden of whether to book a trip to update a PC on me. Your dad's PC will continue to work even if it can't get updated. Windows will skip over unsupported PC's. It will be less secure, but your dad's less likely to be a random target of bad actors.
If the currently outlined process doesn't work on your visit, disable Secure Boot and reset back to Secure Boot factory defaults. That puts the PC exactly where it was before.
Update_UEFI-CA2023.ps1 -Revoke -Latest
Check_UEFI-CA2023.ps1 -Verbose -Audit
1. Secure Boot certs are installed to your UEFI's NVRAM memory. They're used by the BIOS to check anything that tries to boot, whether it's Windows, Linux or an USB boot drive.Do the scripts have a way for updating the Recovery partition so that it contains the 2023 certificates ?
I've looked at the following link from Microsoft, but no mention for updating recovery partion.
I'm not smart like @garlin , but why don't you wipe/reset the keys to factory, reboot and run the script. Every OEM BIOS is a bit different, it may be that in your case, when resetting the keys to factory, it might be throwing your Secure Boot into Setup Mode without you knowing.
You updated all the CA 2023 certs, but have not revoked PCA 2011. This is optional for now, and you can wait for MS to perform this task (later this summer).I updated all the certificates manually with your help. Is it correct now? Thank you.
The bootable media script doesn't apply any Secure Boot certs. It helps copy the newer boot file to an install ISO. A clean install of Windows will not change your certs if your PC doesn't have a valid KEK CA 2023 cert. Which can only be applied in Setup mode for unsupported PC's.I've already done these with no results.
I've successfully create an iso file from link gave by @anchamp65 with "Make2023BootableMedia.ps1"
Now I'm going to do a clean install of Windows to see the results.
Thanks for the clear explanation1. Secure Boot certs are installed to your...
Yes, you're right, nothing has changed, thank you for your help.The bootable media script doesn't apply any Secure Boot certs. It helps copy the newer boot file to an install ISO. A clean install of Windows will not change your certs if your PC doesn't have a valid KEK CA 2023 cert. Which can only be applied in Setup mode for unsupported PC's.

Contact your region's Acer support and ask them why your model is not in this list and if it's not going to be there (it should), then let you know how to change the Secure Boot mode to Setup/Custom mode as it stays stuck at Standard even for my model.acer nitro 5 an515-55 notebook and don't support key enrrollment
There are two planned phases in the normal CA 2023 migration:This is strange.
On March 26, Check_UEFI-CA2023.ps1 indicated success. I have the text file to prove it. Also Windows Device Security/Secure Boot indicates no further certificate changes needed. However I ran Check_UEFI-CA2023.ps1 today and it indicated (similar to below since it it won't show up again at this point)
The update script also breaks the required actions in two parts.REQUIRED ACTION
To revoke the [PCA 2011] cert, run the commands, run the commands:
reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Secureboot /v AvailableUpdates /t REG_DWORD /d 0x280 /f powershell Start-ScheduledTask -TaskName "\Microsoft\Windows\PI\Secure-Boot-Update"