Troubleshooting
The exact messages the loader shows, and what each one actually means.
Start here
Four checks solve most reports before they reach us. Do these in order.
-
1
Restart the machine. If you have spoofed at all this session, this is mandatory rather than optional.
-
2
Run the loader as administrator. Right click, Run as administrator.
-
3
Confirm your antivirus has not quarantined it since last time.
-
4
Re-check the settings for the load method you are picking. A Windows update can silently turn Memory Integrity or the blocklist back on.
Feature updates re-enable Memory Integrity and the Vulnerable Driver Blocklist, and occasionally reset firmware settings. If a setup that worked yesterday stopped working today, and Windows updated in between, that is almost always the cause.
Requirement messages
These come from the firmware check the loader runs after you pick a method. Each one names the exact setting, so match it to your method rather than guessing.
| Message | What to do |
|---|---|
| Please disable 'Memory Integrity' then reboot and try again. | The standard build needs it off. Core isolation, switch off, then reboot. The reboot is required. |
| Please enable 'Memory Integrity' then try again. | The Intel Edition needs it on. Turn on virtualization in the BIOS first or the switch stays greyed out. |
| Please disable 'Vulnerable Driver Blocklist' then reboot and try again. | The standard build needs it off. Same Core isolation screen, then reboot. |
| Please enable 'Vulnerable Driver Blocklist' then try again. | The Intel Edition needs it on. |
| Please disable 'Secure Boot' then try again. | Turn Secure Boot off in the BIOS. See the Secure Boot page for your board. |
| Please clear secure boot keys. | The Intel Edition needs the firmware in Setup Mode. Clear the keys, do not restore factory keys. |
| Your motherboard is not supported. | Your firmware cannot take this method. Use the standard build, or contact support. |
When this is followed by If you're already spoofed, please reboot your computer and try again. Otherwise, please disable 'Secure Boot' and/or clear secure boot keys., read the first line carefully. Nine times out of ten you simply already spoofed this boot, and a restart fixes it. Only if a restart does not help is it actually a Secure Boot problem.
Setup and load failures
These appear after the requirement checks pass, while the loader is doing the actual work. They usually mean something on the machine is interfering rather than a setting being wrong.
| Message | What it usually means |
|---|---|
| Failed to setup a mount point. | The loader could not get at the system volume. Close disk tools and encryption software, then retry. |
| Failed to prepare the system volume. | Same area. BitLocker still on, or a third-party disk driver in the way. |
| Failed to patch the system. | Something blocked the load. Anti-cheat still resident, or the blocklist is back on. |
| Failed to load the BTL component. | The bootloader component could not start. Reboot and try once more before reporting it. |
| Failed to clear the secure boot keys. | Clear them from the BIOS by hand instead. The message names which key failed, such as PK or KEK. |
| Failed to set up the secure boot keys. | Enrolment failed. Clear the keys again in the BIOS, then rerun. Report it if it repeats. |
| Failed to capture your hardware information. | The loader could not read your hardware. Run as administrator, and close other monitoring tools. |
| Failed to read the boot manager file signature. | The boot configuration is unusual or damaged. Contact support rather than experimenting. |
Every one of these ends with Please try another method or contact support. for a reason. If your machine supports both methods, switching is often faster than fighting the one that failed.
Licence and account messages
| Message | What to do |
|---|---|
| Please enter a valid license key. | The key format was rejected. Copy and paste it rather than typing it. |
| You already have a valid license key. | Your account already has time. Your new key stays unredeemed for later. |
| Please purchase a license key at one of our numerous resellers, or on our official website. | No active licence on this account. Check you signed in to the account you redeemed on. |
| Please reboot your computer and run this software again. | Expected on the first Intel Edition run. Restart, then launch the loader a second time. |
| Please manually download the update at the official channel. | Automatic update failed. Delete the loader and download a fresh copy from this site. |
For a hardware mismatch on your account, see hardware lock and resets.
Spoof did not stick
The loader reported success but your serials are unchanged, or only some of them changed.
| Cause | Fix |
|---|---|
| You spoofed twice in one boot | Restart and spoof exactly once. This is by far the most common cause. |
| Fast Startup | Shut down did not really shut down. Use Restart, or disable Fast Startup in Power Options. |
| You checked before rebooting | Identifiers apply fully after the restart the loader asks for. |
| The game was already running | It cached your real values at launch. Close it, reboot, spoof, then start it. |
| A preparation setting reverted | Re-run the verification steps for your method. |
| First Intel Edition run only installed | That run sets up and reboots. Launch the loader again afterwards to actually spoof. |
Still stuck
Open a ticket on Discord. To get a useful answer on the first reply rather than the fourth, include:
- Which load method you picked, Standard or Intel.
- Your processor model and motherboard, or laptop model.
- Your Windows version and build number, from Settings, System, About.
- The exact message, including any code in square brackets such as [PK] or [db].
- What you have already tried from this page.
If the software genuinely does not work on your machine, our refund window is 5 days from delivery or 2 days from redemption. Tell us early rather than at the end of it.
This page did not solve it? Ask our staff on Discord.
