Razer Blade 15 Base (2020) – Persistent Secure boot violation on BIOS 1.04; BIOS 1.06 Update Blocked | Razer Insider
Skip to main content
Question

Razer Blade 15 Base (2020) – Persistent Secure boot violation on BIOS 1.04; BIOS 1.06 Update Blocked

  • Nov 16, 2026 8:52 PM UTC
  • 0 replies
  • 5 views

hitPaleVioletside563

Device Information

  • Model: Razer Blade 15 Base (2020)

  • Model Number: RZ09-03289E21

  • BIOS Version: 1.04 (06/04/2020)

  • Windows: Windows 11

  • Issue: Persistent Secure Boot Violation

Problem Description

I'm troubleshooting a Razer Blade 15 Base (2020) that repeatedly displays the following message during startup:

"Secure Boot Violation – Invalid signature detected. Check Secure Boot Policy in Setup."

The error appears after the Razer logo. Disabling Secure Boot allows Windows to boot normally, but enabling it brings the error back.

The BIOS date and time are correct. The laptop otherwise boots and operates normally with Secure Boot disabled.

Troubleshooting Already Performed

  • Disabled and re-enabled Secure Boot.

  • Performed Razer's official USB Secure Boot recovery procedure. This temporarily resolved the issue, but the violation eventually returned.

  • Verified that the BIOS date and time are correct.

  • Ran sfc /scannow — no integrity violations found.

  • Ran DISM /Online /Cleanup-Image /RestoreHealth — completed successfully.

  • Checked SSD SMART health — healthy.

  • Checked TPM status — no apparent issues.

  • Verified that both Windows Boot Manager files have valid Authenticode signatures:

    • C:\Windows\Boot\EFI\bootmgfw.efi

    • S:\EFI\Microsoft\Boot\bootmgfw.efi

  • Confirmed that the firmware boot entry points to \EFI\Microsoft\Boot\bootmgfw.efi.

Secure Boot Certificate Findings

Using PowerShell, I inspected the UEFI Secure Boot databases (PK, KEK, db, and dbx).

The decoded db contains:

  • Microsoft Corporation UEFI CA 2011

  • Microsoft Windows Production PCA 2011

  • RAZER Certificate

The KEK contains:

  • Microsoft Corporation KEK CA 2011

  • RAZER KEK

I did not find the newer 2023 Microsoft UEFI CA or Microsoft KEK certificates in the decoded output.

Windows registry information under:

HKLM:\SYSTEM\CurrentControlSet\Control\SecureBoot\Servicing

shows:

  • WindowsUEFICA2023Capable: 0

  • UEFICA2023Status: NotStarted

  • ConfidenceLevel: High Confidence

  • Several RebootRequested values set to 1

I don't know whether this certificate situation is directly responsible for the Secure Boot violation, but it seems worth investigating.

BIOS 1.06 Update Problem

The laptop is currently running BIOS 1.04. Razer lists BIOS 1.06 as compatible with the RZ09-03289 model family.

I downloaded the official updater:

RazerUpdater_v1.1.1.2_DA550-BIOSv0106.exe

The updater launches, but the laptop simply restarts. The BIOS remains at 1.04.

I extracted the updater and inspected its contents. It includes:

  • AFUWINx64.EXE

  • Dana5_0106.bin

  • Dana5_0106_FWUpdate.bin

  • amifldrv64.sys

  • FWUpdLcl64.exe

The updater's batch script uses AFUWINx64.EXE to update the BIOS region and FWUpdLcl64.exe to update the Intel ME region.

However, Windows Event Viewer shows the following at the time of the attempted update:

Event ID 3077:
Code Integrity determined that System attempted to load:

\Device\HarddiskVolume4\Program Files (x86)\Razer\Update Tool\amifldrv64.sys

The driver did not meet the Authenticode signing level requirements or violated Code Integrity policy.

Event ID 3023:
The driver amifldrv64.sys is blocked from loading because it has been revoked by Microsoft.

This appears to explain why the BIOS updater cannot proceed.

The updater executable itself has a valid Razer digital signature, and the AMI driver also reports a valid Authenticode signature when inspected. However, Windows explicitly blocks the driver because it has been revoked.

I have not attempted to bypass Windows driver security or manually flash the BIOS.

Questions for the Community

  1. Has anyone experienced this persistent Secure Boot Violation on a Razer Blade 15 Base 2020 (RZ09-0328 series)?

  2. Could the missing 2023 Microsoft Secure Boot certificates be related to this issue?

  3. Is there a way to update the Secure Boot db and KEK certificates safely on this model?

  4. Does anyone have an alternative, official BIOS 1.06 installation method that does not rely on the revoked amifldrv64.sys driver?

  5. Is there a standalone BIOS image or official EFI/USB flashing procedure available for this model?

  6. Could BIOS 1.04 have a firmware-level Secure Boot compatibility issue that requires a newer BIOS or firmware recovery?

Ultimately, I'm trying to restore Secure Boot functionality without permanently disabling it, compromising Windows security, or risking a failed manual BIOS flash.

Any insight from someone familiar with Razer's UEFI firmware, AMI BIOS flashing, or Microsoft Secure Boot certificate updates would be appreciated.