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

garlin said:

Try this updated version.

Click to expand...

Nailed it. Thanks!

check-uefi -verbose -audit
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell Crossing into history

Windows 10 22H2 (19045.7663)

Secure Boot: ON
Virtualization Based Security: OFF (Audit Report runs as ON)
BitLocker on (C:) OFF

BIOS Firmware
-------------
3E Education PC by 3E
Version: PHBYT10A.86A.0031.2014.1216.1446
Date: 2014-12-15

Factory Default UEFI PK Cert
----------------------------
ECS

UEFI PK Cert
------------
Windows OEM Devices PK

Factory Default UEFI KEK Certs
------------------------------
Microsoft Corporation KEK CA 2011
ECS

UEFI KEK Certs
--------------
Microsoft Corporation KEK CA 2011
Microsoft Corporation KEK 2K CA 2023
ECS

Factory Default UEFI DB Certs
-----------------------------
Microsoft Corporation UEFI CA 2011
Microsoft Windows Production PCA 2011
ECS

UEFI DB Certs
-------------
Microsoft Corporation UEFI CA 2011
Microsoft Windows Production PCA 2011
Microsoft Option ROM UEFI CA 2023
Microsoft UEFI CA 2023
Windows UEFI CA 2023
ECS

Factory Default UEFI DBX Certs
------------------------------
(NONE)
EFI_CERT_SHA256_GUID Signatures: 0

UEFI DBX Certs
--------------
(NONE)
Windows BootMgr SVN is MISSING.
EFI_CERT_SHA256_GUID Signatures: 94

UEFI Variables
--------------
SBAT (Linux only): sbat,1,2024010900 / shim,4 / grub,3 / grub.debian,4

EFI Files
---------
Windows Boot Manager [Windows UEFI CA 2023] is ALLOWED.
\\.\HarddiskVolume1\EFI\Microsoft\Boot\bootmgfw.efi
File Version: 28000.342, SVN 9.0

Registry: "WindowsUEFICA2023Capable" = 2
[Windows UEFI CA 2023] in UEFI DB, and Windows starting from CA 2023 Boot Manager.

[OPTIONAL] SkuSiPolicy.p7b (for VBS) is MISSING.

AUDIT REPORT
============
1. [Production PCA 2011] is missing from UEFI DBX
2. DBX Updates are missing from UEFI DBX
3. Windows BootMgr SVN is missing from UEFI DBX

[OPTIONAL] SkuSiPolicy.p7b (for VBS) is missing from EFI

REQUIRED ACTION
===============

To REVOKE the [PCA 2011] cert, run the commands:

reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Secureboot /v AvailableUpdates /t REG_DWORD /d 0x282 /f
powershell Start-ScheduledTask -TaskName "\Microsoft\Windows\PI\Secure-Boot-Update"

BBQ McNugget said:

Nailed it. Thanks!

Click to expand...

Turns out yesterday's fix went 180 in the wrong direction.

I fixed "running 32-bit PS on 64-bit Windows" (someone tried that one before), but not "32-bit PS on 32-bit Windows".

UPDATE: 2026-08-24

1. Issue #129 fix for bcdedit & bcdboot execution path doesn't work on 32-bit Windows

Fixed it for reals on 32-bit Windows 10.

garlin said:

UPDATE: 2026-08-24

1. Issue #129 fix for bcdedit & bcdboot execution path doesn't work on 32-bit Windows

Fixed it for reals on 32-bit Windows 10.

Click to expand...

issue #129
I like even numbers, can someone find a bug so we can get to issue #130 !

Kidding aside, Thanks for your wonderfull support !!!

MS made the CA 2023 files available on W10 22H2, and that includes the 32-bit release. I imagine some folks are doing the "run 32-bit Windows because it takes up less RAM on a really old PC trick". So yeah, kinda have to support those users.