Blade 15 (2023) RZ09-0485 stuck in Deployed Mode - Secure Boot locked, no Windows bootloader will boot | Razer Insider
Skip to main content
Solved

Blade 15 (2023) RZ09-0485 stuck in Deployed Mode - Secure Boot locked, no Windows bootloader will boot

  • June 17, 2026
  • 1 reply
  • 66 views

My Razer Blade 15 (2023), model RZ09-0485, cannot boot any Windows bootloader due to a locked Secure Boot state. My device is out of warranty, but this is a known Secure Boot firmware/certificate issue, not a hardware fault — I'm requesting the recovery firmware package to reset the Secure Boot keys / Platform Key for my model.

I believe this is the known Secure Boot key invalidation issue affecting Blade laptops in 2026 (related to the 2011 Secure Boot certificate expiration / CVE-2023-24932 transition).

Device details:
- Model: Razer Blade 15" (2023) — RZ09-0485
- CPU: Intel Core i7-13800H
- RAM: 64 GB
- Storage: Samsung MZVL21T0HCLR-00B00 (1 TB NVMe)
- BIOS: AMI Aptio (engine v2.22.1287, 2023), Razer BIOS v1.03
- ME Firmware: 16.1.25.2049
(Serial number and proof of purchase available by PM on request)

BIOS Security tab status:
- System Mode: Deployed
- Vendor Keys: Active
- Secure Boot: Enabled (greyed out — cannot be toggled to Disabled)
- No "Key Management", "Reset to Setup Mode", or "Restore Factory Keys" options available

Timeline / how it started:
- Initially, a Windows 11 USB installer booted fine and I began a clean install, deleting all partitions on the internal Samsung SSD.
- During/after that first install attempt, on the first reboot the system dropped into BIOS and from that point on NO Windows bootloader would boot anymore — not the internal SSD's Windows Boot Manager, nor any Windows 11 USB I create now.
- This strongly suggests the Windows installation process applied a Secure Boot revocation (DBX/SVN) update that, combined with the 2026 certificate transition, now causes the firmware to reject Windows bootloaders.

Current symptom:
- No Windows bootloader will start. Freshly created Windows 11 USB installers fail: the Rufus (NTFS) media reported "Windows bootmgr encountered a security validation or internal error", and a Media Creation Tool (FAT32) USB is detected but drops back to BIOS without booting.
- A Linux (Ubuntu) USB boots normally from the same port, confirming the hardware, SSD and USB ports are fine and isolating the problem to Secure Boot rejecting Windows bootloaders.
- The BIOS is in System Mode: Deployed with Secure Boot enabled and greyed out, and there are no Key Management / Reset to Setup Mode / Restore Factory Keys options, so I cannot clear or re-provision the keys myself.

Because the BIOS is in Deployed Mode with no key-management options, and there is no downloadable BIOS update for the RZ09-0485, I cannot resolve this myself. The Windows-based firmware updaters are unusable since I cannot boot into Windows.

Could you please provide the Secure Boot / PK recovery firmware package for the RZ09-0485 that can be applied from a USB drive without a bootable Windows installation? I can provide my serial number and proof of purchase by private message.

Thank you.
 

Best answer by Razer.ScarletRouge

Hey there, ​@jmonterroza

I understand that your Razer Blade 15 (2023) is unable to boot any Windows bootloader due to a locked Secure Boot state, where Secure Boot is enabled and greyed out.

Please try the troubleshooting steps on this link to help resolve your concern. If the issue persists after performing the troubleshooting steps, please send me a private message along with your device's serial number so I can check its details in our system and assist you further. Thank you!



*Thread locked to curb conversation to PM. 

This topic has been closed for replies.

1 Reply

Razer.ScarletRouge

Hey there, ​@jmonterroza

I understand that your Razer Blade 15 (2023) is unable to boot any Windows bootloader due to a locked Secure Boot state, where Secure Boot is enabled and greyed out.

Please try the troubleshooting steps on this link to help resolve your concern. If the issue persists after performing the troubleshooting steps, please send me a private message along with your device's serial number so I can check its details in our system and assist you further. Thank you!



*Thread locked to curb conversation to PM.