Troubleshooting
The errors that come up most, and what each one actually means.
On this page
Startup errors #
Anything the loader refuses to start over, before it touches your boot configuration.
| Message | What it means |
|---|---|
| Unsupported processor | Your CPU is older than Intel 12th generation. There is no workaround; the feature we need does not exist on it. Read more |
| Virtualization not available | VT-x is off in the BIOS, or another hypervisor grabbed it first. Check Task Manager, then Performance, then CPU. Read more |
| VT-d not available | VT-d is off. It is often on a different BIOS page than VT-x, under System Agent or Chipset. Read more |
| VT-rp not available | Redirect Protection is off, or the board hides it behind VT-x and VT-d being enabled together. Enable both and try again. Read more |
| Memory Integrity is off | Core isolation is not running. Usually an incompatible driver is blocking the switch. Read more |
| Access denied | You did not run it as administrator. Right-click the loader and choose Run as administrator. |
| The loader vanished after download | Your antivirus quarantined it. Restore it from Protection history and add a folder exclusion. Read more |
Bootloader errors #
Errors from the first-launch step that installs our bootloader and enrolls its Secure Boot keys. Almost all of them come back to the key databases not being empty.
| Message | What it means |
|---|---|
| Not in Setup Mode | Your Secure Boot key databases still hold the factory keys. Clear them, then confirm with Get-SecureBootUEFI -Name SetupMode. Read more |
| Secure Boot is disabled | You switched Secure Boot off instead of clearing its keys. Set it back to Enabled and clear the keys instead. Read more |
| Key enrollment failed | The firmware refused the write, which usually means it left Setup Mode between the check and the write. Clear the keys again and launch immediately after. Read more |
| EFI partition not writable | The EFI system partition is full, missing or on a different disk than Windows. Bring this one to Discord. |
| BitLocker recovery screen on reboot | Expected after a Secure Boot change. Enter your 48-digit recovery key, then suspend BitLocker before making further changes. Read more |
| Machine will not boot at all | Restore the factory Secure Boot keys from the same BIOS menu you cleared them in, then contact support. Read more |
Injection errors #
Everything that goes wrong once the loader is working and you are trying to get into a game.
| Message | What it means |
|---|---|
| Game not found | The game is not running, or it started before the loader did. Start the loader first, then the game. |
| Injection failed | Most often the game was already in a match, or an overlay grabbed the process first. Close Discord, GeForce Experience and browser overlays, then retry from the main menu. |
| Game closes on inject | Usually the anti-cheat updated ahead of us. Check the product status before retrying, and do not force it. Read more |
| Hardware mismatch | Your machine changed since your first loader sign-in locked the account to it, or you are on a different PC. Reset the hardware lock. Read more |
| License expired | Time runs from redemption. Buy a new plan and redeem the fresh key. |
| Sales are paused for this product | It is flagged as detected and being reworked; sales reopen when it is back. Read more |
Still stuck #
Bring these four things to Discord and you will get an answer in one message instead of five:
- Your processor model and motherboard or laptop model.
- The exact error text, ideally as a screenshot of the loader.
- What the output of Get-SecureBootUEFI -Name SetupMode is.
- What msinfo32 says for BIOS Mode, Secure Boot State and Virtualization-based security.
Never share your license key or your password
Our staff will never ask for either, in a ticket or a direct message. Anyone who does is not us.
This page did not solve it? Ask our staff on Discord.