The list is shared by every Arcane product, the radar included. If nothing starts at all, check the preparation first: third-party antivirus removed, Windows Defender and SmartScreen off, FaceIt and Vanguard removed, and the computer restarted after Intel RST was disabled — an antivirus left enabled and a skipped restart account for more than half of all errors.
Loader and libraries#
The loader closed without an error#
Install the Visual C++ libraries (download) and run the loader again.
Library error on an AMD graphics card#
The loader cannot reach the AMD Software libraries. Go through the steps and stop as soon as it works.
- Install the latest Visual C++ libraries (download).
- Open Task Manager and end every AMD process: AMD Radeon, AMDSrv…, AMDow, CPUMetrics and the rest with those names.
- Open the folder AMD Software: Adrenalin Edition is installed in. By default that is
C:\Program Files\AMD\CNext\CNext. - Download and unpack Libs.rar, then copy the DLL files into that folder, replacing the existing ones.
- If the files will not copy and Windows says the file is open in another program, the AMD processes are still alive — go back to step 2 and check the list again.
- Start AMD Software and turn the performance metrics display back on: replacing the files resets that setting, and the overlay does not work without it.
- Go back to launching the software.
Antiviruses#
Make sure all antiviruses are disabled on Windows 10#
- Remove every third-party antivirus.
- Turn off real-time protection.
- Turn off SmartScreen.
Make sure all antiviruses are disabled on Windows 11#
- Download both files.
- Run
Turn_ON, accept the registry changes, restart the computer. - Run
Turn_OFF, accept the registry changes again and restart the computer once more. - If that did not help, check that the antivirus is actually removed and real-time protection is off.
Virtualization and Hyper-V#
Please make sure PIN is not set in Windows sign-in options and manually disable Hyper-V#
- Remove the Windows sign-in password and PIN completely.
- Temporarily disable CPU virtualization in the BIOS.
- Run PowerShell as administrator and execute the commands. You can paste all of them at once, there is no need to copy line by line:
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"
- Turn CPU virtualization back on in the BIOS.
The full walkthrough for disabling Hyper-V — with DISM, bcdedit and the registry keys — lives in the common section: disabling Hyper-V.
Please enable Intel VT-X in the BIOS#
Enter the BIOS, find the option called "Intel Virtualization Technology" or "Intel VT-X" and enable it.
Please enable AMD-V in BIOS#
Enter the BIOS, find the option called "AMD-V" or "SVM Mode" and enable it.
VMX/SVM is not supported#
- Open "Control Panel" → "Programs and Features" → "Turn Windows features on or off" and clear the "Virtual Machine Platform" and "Hyper-V" checkboxes.
- If the error is still there, open cmd as administrator and run:
bcdedit /set hypervisorlaunchtype off
- Restart the computer.
Secure Boot and disk layout#
Please disable secure boot in the BIOS#
Enter the BIOS and turn Secure Boot off.
Secure boot keys are incorrect and need to be enrolled#
The error means the Secure Boot keys are not enrolled. They have to be written once, and then Secure Boot is turned off again.
- Enter the BIOS, enable Secure Boot and save the settings.
- Check the result: open PowerShell and type
Confirm-SecureBootUEFI. ATrueanswer means it was enabled correctly. - Restart the computer, go back into the BIOS and disable Secure Boot.
Unsupported firmware#
The system drive uses the MBR layout while GPT is required. Convert it with the built-in Windows tool mbr2gpt or any other disk management utility.
The conversion touches the partition layout of the system drive. Back up your important files before it.
Hardware and memory#
Failed to map memory#
- Check how much RAM you have. Less than 12 GB and the software will not start, that is a hardware requirement; contact support.
- Turn off every startup program and restart the computer.
- If that did not help, download AutoRuns and disable everything registered under
CurrentVersion\Run.
Incorrect hwid#
Open cmd as administrator and run the commands one after another:
wmic diskdrive get Caption, SerialNumber
wmic baseboard get SerialNumber
They show the same data the loader reads: the model and serial number of the drive and the serial number of the motherboard. If either one fails or comes back empty, the problem is on the system side — a Windows reinstall usually fixes it.
AES instruction set is not supported#
The CPU does not support the AES instruction set. There is no way around it — the software will not work on this hardware. Contact support.
Menu and visuals in game#
The menu is there but does not react, or opens only on the second try#
The cause is almost always the same: the wrong overlay is fighting for the rendering, or the rights are wrong.
- Run the overlay application — NVIDIA App, AMD Software, Discord, Medal or SteelSeries GG — as administrator.
- Run Steam without administrator rights if you play through Steam.
- Turn off the EA App overlay in the app settings if the game starts through it.
- Turn off every other third-party overlay and keep only the one the software runs through.
The menu disappears, or the visual features do not work#
- If the game was patched, wait for the product update: the features will not work until then.
- Verify the integrity of the game files, or better, reinstall the game completely.
- If that did not help, contact support.
Nothing helped#
Take a screenshot of the error and send it to support. If a remote session is needed, install AnyDesk and send its ID there as well — that speeds the case up.
