Error codes

Virtualisation is off in BIOS, or Windows has taken it. Enable Intel VT-x or AMD SVM in BIOS first.

If it is already enabled, Windows is holding it. Run PowerShell as administrator, run Set-ExecutionPolicy RemoteSigned, restart, then disable Hyper-V, Core Isolation and Credential Guard. See the Hyper-V entries below.

Exactly what it says. Reboot into BIOS and enable Intel VT-x or AMD SVM. The setting is usually under CPU Configuration or Advanced.

Your CPU does not support AES, or AES is disabled in BIOS. Enable it in BIOS. If your CPU genuinely lacks it, the product will not run on that machine.

Your Windows disk is using the legacy MBR partition scheme. Convert it to GPT with the built in Windows mbr2gpt tool, or any disk management utility.

Your storage controller is in IDE or RAID mode. Set it to AHCI in BIOS.

Turn off RAID and virtual disks in BIOS, and disable Intel Rapid Storage Technology if you have it.

If that does not clear it, find every driver or service beginning with iaStor using DriverView or Process Hacker and disable them.

If Windows was installed on a RAID or IRST volume, switch from RAID to AHCI properly rather than flipping the BIOS setting, which will not boot.

Same fix as above. Disable IRST, then disable any remaining iaStor drivers and services.

Microsoft Storage Spaces is enabled. Disable it under Control Panel, Storage Spaces.

This can wipe the data on the affected disk. Back up first.

Your integrated GPU is still enabled. Disable the APU or iGPU in BIOS.

If the machine has no integrated GPU, your overlay is not set up. Go back to Overlay setup.

Remove your Windows PIN and password under Settings, Accounts, Sign-in options. Then disable Device Guard and Credential Guard:

1. Download the Device Guard and Credential Guard hardware readiness tool.
2. Extract the ZIP.
3. Open PowerShell as administrator.
4. Run Set-ExecutionPolicy Unrestricted -Scope Process.
5. cd to the folder you extracted.
6. Run .\DG_Readiness_Tool_v3.6.ps1 -Disable.
7. Restart. If a screen asks you to confirm disabling Device and Credential Guard, press F3.

Same procedure as the entry above. Remove your PIN first, then run the readiness tool with -Disable.

The loader could not repair your Hyper-V files, which almost always means you are on a custom or "optimised" Windows build. Reinstall official Windows.

Run the loader's disabler manually. Extract Disabler.rar to a folder and run run_disable_and_backup as administrator.

Restart first. If it persists, something else on the machine is running a hypervisor: VMware, VirtualBox, Sandboxie, BlueStacks, WSL2 or Docker are the usual culprits. Uninstall it.

Switch to the other HWID Virtualizer option in the loader. There are two, and hardware that rejects one usually accepts the other.

Reboot and try again. If it continues, something else on your PC is already spoofing hardware identifiers. Find it and remove it, since two spoofers will always fight.

Open CMD as administrator and run these one at a time:

wmic diskdrive get Caption, SerialNumber
wmic baseboard get SerialNumber
getmac

If any of them errors, your Windows install is damaged. Reinstall Windows.

An HWID mismatch. Restart Windows and try again. If it persists, request an HWID reset through a ticket in Discord.

Install vc_redist.x64.exe and restart.

Do this even if you are certain it is already installed. A damaged install looks identical to a missing one, and reinstalling is the fix either way.

An antivirus or anti-cheat is blocking it. Disable and uninstall every antivirus, Vanguard, FACEIT and ESEA, then retry.

Remove your antivirus and any FACEIT or Vanguard install, restart, and launch again.

Similar message, different cause. This one is a registry fix rather than an antivirus problem, and the vendor supplies a .reg file for it.

Ask for it in a ticket in Discord rather than downloading one from anywhere else, then run it and reboot.

Never run a .reg file from a forum, a video description or a stranger. It writes straight into the registry with no prompt about what it is changing.

Update Windows to the latest build. This one is the exception to the usual advice about staying on a known build.

Retry a few times, restarting the PC between attempts.

If it keeps failing, try a VPN, see VPN and region problems. If it still fails after that, open a ticket.

1. Confirm you have 16 GB of RAM or more.
2. Disable everything under Task Manager, Startup, then restart.
3. Make sure the loader is on a local disk, not OneDrive, Mega or any cloud folder.
4. Use Autoruns to disable everything under Microsoft/Windows/CurrentVersion/Run, and nothing else. Save and restart.

If none of that helps, run the product immediately after booting, before anything else starts. If it still fails, your Windows install is the problem.

Your Windows build is not supported. Update or roll back to a supported build in the 1909 to 25H2 range, and use an official Windows image.

You closed the loader while it was still downloading or loading the product. Let it finish next time.

Retry. If it keeps failing, update Windows.

Either the servers are under maintenance, which the status page will show, or your connection is being filtered. Try a VPN.

Restart your PC and try again.

The loader could not remove the hypervisor file it needs out of the way, because virtualisation is holding it open.

1. Reboot into BIOS and disable SVM, VT-x and VT-d.
2. Boot into Windows and delete or rename hvax64.exe.
3. Reboot into BIOS and enable SVM, VT-x and VT-d again.

The last step is not optional. Exodus needs virtualisation on, so leaving it disabled trades this error for a different one.

Open a ticket in Discord with a screenshot. This one is not user fixable.

Unlock your taskbar and drag it back to the bottom of the screen, then press your overlay key once to reposition.

Turn off Capture Clips under Medal's Clip Settings.

In order: confirm Medal or Discord is running as administrator, confirm the game is in borderless or windowed mode, and wait the full three minutes at the main menu. Those three account for nearly every report.