SOLVED] Blade 14 (2021) RZ09-0370 Secure Boot Violation “Invalid signature detected” – db missing Windows UEFI CA 2023 (fix without BIOS update) | Razer Insider
Skip to main content

SOLVED] Blade 14 (2021) RZ09-0370 Secure Boot Violation “Invalid signature detected” – db missing Windows UEFI CA 2023 (fix without BIOS update)

  • Nov 4, 2026 3:56 PM UTC
  • 1 reply
  • 70 views

Proto25x

After BIOS 1.08 and the October 2026 Windows updates, enabling Secure Boot on my Blade 14 (2021) gave a red “Secure Boot Violation – Invalid signature detected” screen. Windows only booted with Secure Boot disabled, and Call of Duty showed “Secure Boot not Enabled” with reduced matchmaking.

The official recovery USB (article 20795), sfc, DISM, bcdboot and F3 defaults did not help. Here is what fixed it.

Root cause
Windows boot files are now signed under Microsoft’s new certificate chain (“Microsoft Windows Production PCA 2026”). The BIOS factory db only contains the old “Windows Production PCA 2011” certificate and is missing “Windows UEFI CA 2023”, so the firmware rejects Windows Boot Manager. Windows’ automatic certificate update can’t run while Secure Boot is off, so it’s a dead end unless you add the certificate manually.

⚠️ Disclaimer: This is not an official Razer or Microsoft procedure. It worked on my Blade 14 (2021) RZ09-0370 with BIOS 1.08. Do it at your own risk, with the charger connected. If you use BitLocker, back up your recovery key first (manage-bde -status C:). If the firmware rejects the file, nothing changes.

All commands run in PowerShell as Administrator, with Secure Boot disabled.

1. Check that this is your problem (read-only)

powershell

$db=[Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI db).bytes)
$kek=[Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI KEK).bytes)
"DB 2011: " + ($db -match 'Windows Production PCA 2011')
"DB 2023: " + ($db -match 'Windows UEFI CA 2023')
"KEK 2011: " + ($kek -match 'KEK CA 2011')

This fix applies if you get DB 2011: True, DB 2023: False, KEK 2011: True.

2. Back up your db and prepare the Microsoft-signed update file
The file dbupdate2024.bin ships with Windows and is signed with Microsoft’s 2011 KEK, which the Blade firmware trusts.

powershell

New-Item -ItemType Directory -Force C:\SBfix | Out-Null
Get-SecureBootUEFI db -OutputFilePath C:\SBfix\db_backup.bin | Out-Null
$b=[IO.File]::ReadAllBytes("C:\Windows\System32\SecureBootUpdates\dbupdate2024.bin")
$len=[BitConverter]::ToUInt32($b,16)
[IO.File]::WriteAllBytes("C:\SBfix\signature.p7", $b[40..(16+$len-1)])
[IO.File]::WriteAllBytes("C:\SBfix\content.bin", $b[(16+$len)..($b.Length-1)])

3. Append the certificate to the firmware db

powershell

Set-SecureBootUEFI -AppendWrite -Name db -ContentFilePath C:\SBfix\content.bin -SignedFilePath C:\SBfix\signature.p7 -Time 2010-03-06T19:17:21Z

Success returns a small table (Name: db, Attributes: NON VOLATILE...). An error means the firmware rejected it and nothing changed.

4. Verify

powershell

$db=[Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI db).bytes)
"DB 2023: " + ($db -match 'Windows UEFI CA 2023')

It should now say True.

5. Enable Secure Boot
BIOS > Security > Secure Boot > Enabled > F4 Save & Exit. Windows boots normally and Confirm-SecureBootUEFI returns True.

Notes

  • Don’t use F3 Optimized Defaults afterward. It may reset the keys and remove the certificate.
  • Keep the C:\SBfix folder in case a future BIOS update resets the keys.
  • Razer, please release a BIOS update with the Microsoft 2023 Secure Boot certificates in the default keys for the 2021 Blade models.

Credit to the community guide that documents manual installation of Microsoft’s signed files: https://github.com/cjee21/Check-UEFISecureBootVariables/issues/21

1 Reply

  • Insider Mini
  • Nov 10, 2026 8:18 AM UTC

Confirmed working on a Razer Blade 15 (2018, RZ09-02386, BIOS 1.05). Same symptoms, same fix. In my case the cert was lost after the battery fully drained once (keys reset to factory).

 

One addition: after re-enabling Secure Boot, let Windows apply the remaining 2023 certs (KEK 2023, 3rd-party UEFI CA, Option ROM CA). The manual step only adds the Windows cert. In PowerShell as Administrator:

 

Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\SecureBoot' -Name 'AvailableUpdates' -Value 0x5944 -Type DWord

Start-ScheduledTask -TaskName '\Microsoft\Windows\PI\Secure-Boot-Update'

 

Reboot twice. Event Viewer > System > TPM-WMI should show events 1043/1044/1045/1808, and HKLM\SYSTEM\CurrentControlSet\Control\SecureBoot\Servicing\UEFICA2023Status should read "Updated". Thanks for the write-up!