Find your error with Ctrl+F — below it is written exactly as the loader prints it.
Half of all failures come from the overlay: it is either not running or was started after the loader. The order is covered in the launch guide.
Please launch SteelSeries Sonar overlay (FOR STEELSERIES)#
Sonar is not active. Press the SONAR bind before the injection, not after it.
Please launch SteelSeries Moment overlay (FOR GEFORCE)#
Turn the GeForce overlay off and then back on.
The bind does not respond#
Reinject. If that does not help, run the overlay as administrator.
The menu does not open, or the loader closes right after it starts#
The Microsoft Visual C++ libraries are missing. Install them and run the launch again.
The menu or black screens are flickering#
Open SteelSeries → Settings → MOMENTS → Capture and Sound and turn ALLOW MOMENTS TO CAPTURE WHILE GAMING off.
Failed to load dependencies(x)(-x) — Make sure all antiviruses are disabled#
Turn every security tool off and remove the antivirus software and anticheats from the computer. All of them: one left behind is enough. If that does not help, clean up the startup programs.
Please uninstall Vanguard/Faceit first#
Remove the Vanguard or Faceit anticheat and try again.
Please make sure PIN is not set in Windows sign-in options and manually disable Hyper-V#
Remove the sign-in PIN and turn Hyper-V off following the separate guide.
Please enable Intel VT-X/AMD-V in the BIOS#
Enable "Intel virtualization technology", "Intel VT-X", "AMD-V" or "SVM mode" in the BIOS: the name differs from board to board.
VMX/SVM is not supported#
The opposite case: Windows has to hand virtualization over to the cheat. Open Control Panel → Programs and Features → Turn Windows features on or off and make sure Virtual Machine Platform and Hyper-V are off.
If the error stays, a command prompt as administrator:
bcdedit /set hypervisorlaunchtype off
Restart the computer afterwards. On Windows 11, when that fails too, PowerShell as administrator is what is left:
takeown /F "C:\Windows\System32\hvix64.exe"
icacls "C:\Windows\System32\hvix64.exe" /grant *$(([System.Security.Principal.WindowsIdentity]::GetCurrent()).User.Value):F
takeown /F "C:\Windows\System32\hvax64.exe"
icacls "C:\Windows\System32\hvax64.exe" /grant *$(([System.Security.Principal.WindowsIdentity]::GetCurrent()).User.Value):F
del "C:\Windows\System32\hvix64.exe"
del "C:\Windows\System32\hvax64.exe"
Failed to allocate memory / to map memory(x) — Please reboot PC and try again#
The driver installed incorrectly. Restart the computer and run the launch again. After that, in order of effort: if you are in an internet café and the error persists, try a different computer; clean up the startup programs; and if that still leaves it, download Autoruns and disable everything non-system in startup. Drivers left behind by uninstalled software are a common cause.
0x296#
A reinject is required.
Unknown network error#
The loader never reached the server. Check the connection and try again; if a VPN is on, it may be the cause.
Unsupported Firmware#
The system is running in Legacy mode. Convert the system disk to GPT with the built-in mbr2gpt tool or any disk management utility, and switch the BIOS from Legacy to UEFI.
Please disable Intel Rapid Storage Technology#
Turn RST off, Microsoft's instructions.
Either virtual or RAID disk is present. Please revert it back to normal state#
If a spoofer is running, turn it off. If RAID is the cause, it is switched off in the BIOS, and Windows has to be fully reinstalled afterwards.
Incorrect HWID#
Check whether the system reports its serial numbers at all. A command prompt as administrator, one command at a time:
wmic diskdrive get Caption, SerialNumber
wmic baseboard get SerialNumber
Recent Windows 11 builds no longer ship wmic — PowerShell shows the same data there:
Get-CimInstance Win32_DiskDrive | Select-Object Caption, SerialNumber
Get-CimInstance Win32_BaseBoard | Select-Object SerialNumber
If one of the commands fails or comes back empty, the problem is on the computer's side. Reinstall Windows and check again.
AES instruction set is not supported#
The CPU does not implement the AES instructions. This cannot be fixed.
CRD failed at XXX with code XXXXXXXX / Failed to init render#
On a desktop the GPU is too old and unsupported; on a laptop, disable the integrated GPU in the BIOS.