You ran the loader, your PC restarted, and instead of Windows you got a screen reading Secure Boot Violation, sometimes with a line about an invalid signature being detected. Or Windows came back up and blocked the driver instead, with a signature error carrying the code C0000428, sometimes worded as Windows cannot verify the digital signature for this file. Others see the loader flash a few lines and restart the PC the moment they press Load Module. Support treats all of those as the same underlying problem, so the same fix is the first thing to try on any of them.
Why this happens
Each of those screens is a signature check refusing to let a driver load. The guides do not spell out the mechanism, so we will not guess at it here. What support sees in these chats is consistent: the customer still has Secure Boot enabled in the BIOS, and disabling it is the fix support gives. It does not clear it for everyone, and support handles those cases individually. If yours is already off and the screen is still there, go straight to the last step.
How to fix it
Turning Secure Boot off can trigger a BitLocker recovery prompt on the next boot, so have your BitLocker recovery key to hand first. Support also sees violations and boot loops in the other direction, when Secure Boot is turned back on after the cheat has been used, so ask support before you flip it back.
If the violation screen is stopping the PC from reaching Windows at all, do not work through this list. That one needs a person, so contact support.
- Search
System Informationin Windows and read the Secure Boot State line. If it says On, that is the cause support looks for first. - Restart and enter your BIOS. The key is usually DEL, F2 or F10, and is normally shown briefly on the startup screen. This has to be done in the BIOS itself, not from inside Windows.
- Find Secure Boot, normally under the Boot or Security tab. On ASUS boards it is often called Secure Boot Control. Set it to Disabled.
- While you are in there, find Fast Boot under Boot or Advanced and set it to Disabled too. Save and exit.
- Back in Windows, turn off Fast Startup through Control Panel, Power Options, Choose what the power buttons do.
- Open System Information again. Some boards still report Secure Boot State as On after the option has been changed, so confirm it actually reads Off before you inject.
- On Rainbow Six Siege products, support also asks you to disable Virtualization in the BIOS, under Advanced or CPU Configuration. It may be listed as VT-x, VT-d, or SVM Mode on AMD boards. If you are on another game and are not sure whether this applies, ask support for the specifics for your product.
- If you use a spoofer, run it after the BIOS change and before you launch the game. For Trace 2.0 the documented order is register your key, press Clean, restart, press Spoof, then launch.
- If the loader still crashes after you changed Secure Boot, confirm your Windows installation still boots in UEFI mode, disable Fast Startup, then do a complete shutdown and restart. Contact support with your motherboard, CPU, Windows version and the exact error.
One case chat cannot settle for you. If the game itself refuses to launch unless Secure Boot is on, that is the game's own requirement and it pulls against this setup. Contact support instead of guessing.
Which products this applies to
These screens turn up across our loader products, most often on Rainbow Six Siege:
- Frost, Frost Pro and Inferno for Rainbow Six Siege
- Frost for Fortnite
- Frost, Frost LITE and Armani for BO6, BO7 and Warzone
- Hydra for Arc Raiders
- The Trace 2.0 spoofer, which can show the same signature error while it runs
Check your product guide too, and check the status board before you buy.
If you have worked through all of that and the same screen is still there, open a chat with support. Send a photo of the screen, your motherboard or PC brand, and your Windows version.
