Troubleshooting

Vega sets itself up across one reboot. Being asked again after that means it cannot find the state it wrote, and there are three usual reasons:

1. More than one Windows install on the machine. Vega writes to one and boots into the other.
2. A leftover EFI partition from a Windows install that is no longer there. This is the most common one, and the hardest to see, because the machine boots perfectly.
3. Some laptops simply hang on a black screen through this step. It is uncommon but known.

For the first two, the fix is removing the second install or the stale EFI partition, which is real disk surgery and easy to get catastrophically wrong.

Do not delete partitions to fix a cheat loader unless you know exactly what you are doing and have a backup. Getting this wrong makes the machine unbootable. If you are not confident, open a ticket instead.

Go into BIOS and set your Windows drive as the first boot option. The restart can leave the boot order pointing somewhere else.

It did not work. The loader closing itself is the success signal, so do not start the game hoping for the best.

Restart the machine and run through the second Load again. If it still stays open, work through the loader entries below.

Windows component damage is the usual cause. Open a command prompt as administrator and run these one at a time, letting each finish:

Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Restart afterwards.

If it still crashes, install vc_redist.x64.exe and try once more.

1. Check the key has not run out. Licences count from when you entered the key, not from purchase, and run continuously. See Licences and keys.
2. Check your hardware has not changed, see HWID resets.
3. Check the status page.

1. The game is not in borderless. Fullscreen will not show the menu.
2. The game window is not focused. Click into the game, then press the key.
3. The security patch has not finished. Siege restarts and patches itself after the second Load. Let it finish.
4. The first load is still running. It can take up to ten minutes. Closing the game restarts the whole process.

Windows Exploit Protection is blocking it. Open Windows Security, App and browser control, Exploit protection settings, and turn off the system wide mitigations.

Turn them back on when you finish playing.

Use the Windows interface first, because it is reversible with one click:

Windows Security, Device security, Core isolation details, turn Memory integrity off, then restart.

If the toggle is greyed out or switches itself back on, open a command prompt as administrator and run:

bcdedit /set hypervisorlaunchtype off
reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity" /v "Enabled" /t REG_DWORD /d 0 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard" /v EnableVirtualizationBasedSecurity /t REG_DWORD /d 0 /f

Restart afterwards.

Watch the last value. Guides circulating for this product give that command with /d 1 on the end, which switches virtualisation based security on and is the opposite of what they are trying to do. The value you want is 0, as written above.

To undo all of this later, set both registry values back to 1 and run bcdedit /set hypervisorlaunchtype auto.