First launch and the bootloader

The first time you run the loader on a machine, it does something it will never do again: it installs its own bootloader and enrolls the Secure Boot keys that sign it. This is why you emptied those databases.

1. 1.
   Run the loader as administrator and sign in.
2. 2.
   It checks your hardware: processor generation, VT-x, VT-d, VT-rp, Secure Boot state and Memory Integrity. Anything missing is named on screen.
3. 3.
   It writes its bootloader to the EFI system partition and enrolls its keys into your now-empty databases.
4. 4.
   It asks you to reboot.

If it stops at the hardware check instead, the message tells you which requirement failed. Each one maps to a page in this section.

Restart normally when asked. On the way back up, your firmware validates the new bootloader against the keys that were just enrolled and hands control over.

Once you are back in Windows, everything that read as off during setup should now read as on:

1. 1.
   Press Windows + R, type msinfo32 and press Enter.
2. 2.
   Secure Boot State should now read On.
3. 3.
   Virtualization-based security should still read Running.

You are out of Setup Mode and Secure Boot is enforcing again, this time trusting our bootloader. From here the loader starts in seconds and never asks for any of this again.

1. 1.
   Start the loader first and leave it open. It has to be running before the game is.
2. 2.
   Pick the product you redeemed from the list. Its status is shown next to it.
3. 3.
   Start the game the way you normally would, through Steam, the Epic launcher or Riot Client.
4. 4.
   Get to the main menu, not into a match yet.

1. 1.
   With the game at its main menu, click Inject next to the product in the loader.
2. 2.
   Wait for it to report success. It takes a few seconds.
3. 3.
   Open the in-game menu with the Insert key, then configure what you want from there.

That is it. Every session after this is: open the loader, start the game, inject.

If the injection fails, or the game closes when you try, the troubleshooting page covers the common causes.