Recent content by GunnzAkimbo

Got an automated update just a moment ago: This device has updated Secure Boot CA/keys. This device signature information is included here. DeviceAttributes: BaseBoardManufacturer:MSI;FirmwareManufacturer:American Megatrends Inc.;FirmwareVersion:1.A1_0.4.3;OEMModelBaseBoard:X99A GODLIKE GAMING...

Changed to moving the script to C: and launched it with Powershel ISE. Result: PS C:\> C:\EFI_Path.ps1 UpdatesFolder: C:\Windows\System32\SecureBootUpdates BootDirectory : C:\Windows Name : BootConfiguration SettingID : Caption : \Device\Harddisk22\Partition1 Disk 22...

BootDirectory Name SettingID Caption ------------- ---- --------- ------- C:\Windows BootConfiguration \Device\Harddisk22\Partition1

v2026.05.08.01 PS D:\AdminTools\CheckCA2023> .\check_UEFI-CA2023.ps1 -Audit Secure Boot: ON Virtualization Based Security: ON BitLocker on (C:) OFF UEFI KEK Certs -------------- Microsoft Corporation KEK CA 2011 Microsoft Corporation KEK 2K CA 2023 UEFI DB Certs -------------...

v2026.04.24 operates as normal without any messages, i will just stick with that release.

\Device\Harddisk22\Partition1 : The term '\Device\Harddisk22\Partition1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 +...

I tried that script you posted just a few back and received this: *update: is it because i am launching from D: drive ? I have all my utilities on that. UEFI DBX Certs -------------- (NONE) Windows BootMgr SVN Get-Partition: D:\AdminTools\CheckCA2023\Check_UEFI-CA2023.ps1:1591 Line |...

I had to do secure boot clear again (this old 2015 mobo is odd, when powered off at the plug, turning on gives black screen. Have to clear secure boot into setup mode to boot into windows and redo process). I have done the update with -revoke, and checked with -audit - verbose -bootmedia this...

Same, just ran that win update. I might see if garlin does an updated script then clear the keys and run update script again.

Or MS does it through win update? apparently. I will leave it for now and check if it does in a few days.

I re-enabled core isolation memory integrity (big fps hit on my cpu) and ran the check again and it says this: SkuSiPolicy.p7b (for VBS) is MISSING. [OPTIONAL]

hmmmmmm umm!!! Previous posts back i did the deleting of ALL SB files in bios and entered secure boot setup mode then used the older script to check then update, completely oblivious to the fact i had windows hello pin enabled... WHAT???!!! It all worked fine though, but what i did was used the...

OK! Success. The Output LOG: Secure Boot: ON Virtualization Based Security: OFF BitLocker on (C:) OFF UEFI KEK Certs -------------- Microsoft Corporation KEK CA 2011 Microsoft Corporation KEK 2K CA 2023 UEFI DB Certs ------------- Microsoft Corporation UEFI CA 2011 Microsoft...

I have changed to MANUAL permanently instead of STANDARD so it would have a better chance of updating then ran the .\Check_UEFI-CA2023.ps1 script again: Secure Boot: ON Virtualization Based Security: OFF BitLocker on (C:) OFF UEFI PK Cert ------------ DO NOT TRUST - AMI Test PK...

hmm lots to process. I just want to get my old X99 board updated with 2023 secure boot. Theres an option in bios to use custom (instead of standard) Should i just enable custom? I will linger around as this becomes more of a concern closer we get. What i get: REQUIRED ACTION ===============...