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

Fixed! And faster, too. Previously, there was a long delay at the start, but now it works quickly.
Thx

Sony Vaio sve said:

Hello all. I have read all 176 pages on all these subjects and all of you been great on your ideas, fixes, and end results. I truly mean it!
To begin this "I'm truly sorry" to be putting this out there! I'm doing this because I'm at my last resort of what to do so please be and have patience with me. I'm so so cautious of messing with my UEFI/BIOS because I can't afford another computer. I mostly work with spreadsheets and a CAD program. I really need advise what to do and how to do it. Not for work. I just poured a 1/4 bottle of Kahlua into my coffee, so here it goes. I just don't know if I should do the update or just leave as is? I really want to update though. When upgrading to Windows 11, I had to bypass all requirements. Thank you.
I'm in the bios as Administrator and secure keys is custom. This is what I see when I see if I can manually input UEFI files.

SECURE BOOT DATABASE: Installed and Locked.
ENFORCED SECURE BOOT: Enabled.
USER CUSTOMIZED SECURITY: No.
ERASE ALL SECURE BOOT SETTINGS: Disabled. (I can erase.)

Click to expand...

This PC could be more risky to update. Acer, Lenovo and Sony use the Insyde BIOS as their reference platform.

Older versions of this BIOS (going back to 2016) may have a hidden HW or BIOS limitation, where trying to manually add certs can trigger a possible "bricking" situation. While the UEFI may have enough NVRAM (in total) to safely add more keys, the specific amount of memory allocated for Secure Boot may be artificially capped. In certain cases, adding new certs will fail and you get truncated data.

This leads to a bricking because the data fails the BIOS's consistency checks. Sometimes you can manage a way to get out, other times it requires reflashing the BIOS to a known good state to recovery. If this PC is important to you, I wouldn't risk it and just leave Secure Boot off. You can always try manual enrollment (it works for a wide range of PC's) but the older Insyde versions are more prone to failure than an older BIOS from AMI.

Typically this requires a new BIOS version, to account for how much memory is available for Secure Boot variables.

Thank you Garlin for your quick response. because the Insyde bios in Sony Vaio laptops are pretty much imposable to get the password to unlock the bios and there's no way in hell to get a updated bios, I also felt that I would keep the laptop as is, until I find a rock solid way to update UEFI files manually or by using your UEFI pack to update the secure boot files.
I'm not on the internet that much. I use Norton365 and Norton AntiTrack to help what they can.
I know you have put a whole lot of time into helping everyone and giving them the bravery to update their UEFI/bios. Hell, If you told me to just do it wit an idea it would work, I would do it because I fully trust your mind and word, and I don't trust anyone, still at 62!
A great big thanks to all who is making updates possible!
all take care and keep up with the great work. I will keep reading daily just in a case someone has the same problem I have and they have found a fix!
Bob