Secure Boot Violation - Blade 15" Base (2018) | Razer Insider
Skip to main content
Question

Secure Boot Violation - Blade 15" Base (2018)

  • October 14, 2026
  • 2 replies
  • 19 views

Hi there,

 

Since installing the latest Windows updates on my Razer device, I am consistently presented with a red pop-up message on startup titled:

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

After clicking OK, the System Recovery window appears. I have attempted to use the "Recover OS Partition to Factory Default" option on multiple occasions, however this has not resolved the issue.

I would be grateful if someone could assist with resolving this problem, as I am currently unable to restore the device to a working state. Any guidance or support would be greatly appreciated.

Thank you in advance for your assistance.

 

Many thanks,

Erdogan Yusuf 

This topic has been closed for replies.

2 Replies

smartHarlequinwatch493

Hi Erdogan, this one has been hitting a lot of 2018 Blade owners after the recent Windows updates, because the updates changed the Secure Boot signatures that the older BIOS expects. Boot into the BIOS setup (tap F1 or Del at startup), go to the Security tab, and check that Secure Boot is enabled and the boot mode is set to UEFI rather than Legacy or CSM. In the Secure Boot section, use the option to restore or enroll the factory default keys, then save and exit — that clears the violation message in most cases. If it still will not boot, temporarily disable Secure Boot so you can get into Windows, install every pending Windows update plus the latest Blade BIOS and firmware, and then turn Secure Boot back on. A factory recovery will not fix this on its own, since the recovery image restores the same older bootloader that Secure Boot is now rejecting.

Razer.ScarletRouge
Forum|alt.badge.img

Hey there, ​@Eddie39 

 

I understand that you are consistently encountering the "Secure Boot Violation - Invalid signature detected error. Please try the troubleshooting steps on this link to help resolve the issue.

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. 

CookiesAccessibility statement