faqHelp
Frequently asked questions
Guides and answers to the most common questions.
01Getting started
Log in and open Downloads in the sidebar. Only the products active on your account are listed there, always with the latest build. If a product is missing, check your Dashboard to confirm the subscription is active.
Products only appear once a purchase has been delivered. If you just paid, give it a few minutes and refresh. If it's still missing, check your Dashboard for an active subscription, then open a Support ticket.
02HWID & device
A reset can be requested once the loader has refused a login from a new machine. Open the Support page, create a new request, choose HWID reset, pick the product and give a short reason. If at least 2 of the 4 hardware identifiers (CPU, motherboard, system UUID, disk) still match your registered machine, the reset is approved automatically and you can log in right away. Otherwise an admin reviews the request. You can only have one HWID reset pending at a time. Once it is approved, relaunch the product on the machine you want to use: it re-binds to that PC automatically.
03Billing & payments
Most payments are delivered automatically within a few minutes. If you paid and nothing arrived, open a Support ticket with your payment email and transaction ID so we can match and deliver it manually.
Yes, if the product won't launch or isn't compatible with your machine, contact support and we'll help troubleshoot or issue a refund. Outside of these cases, digital products are non-refundable once a license has been activated or redeemed.
04Loader errors
The build was downloaded but failed its cryptographic check. The most common causes: 1. Your Windows clock is out of sync (very common after a reboot). Go to Settings → Time & language → Date & time → "Sync now", then relaunch the loader. 2. Your antivirus altered the download. Defender, Kaspersky or Avast can modify or truncate the downloaded .bin file. Add the loader folder to your antivirus exclusions. 3. The local cache is corrupted (interrupted download, power loss). Delete every .bin file in the product folder next to the loader, then relaunch. 4. An update is being deployed. Wait 1–2 minutes and try again.
Your system clock is out of sync, so login will most likely fail. Go to Settings → Time & language → Date & time → "Sync now", then relaunch the loader.
The loader can't reach api.elusive.is. Check your internet connection, try again with your VPN turned off, and open https://api.elusive.is in a browser to confirm it loads. Restart your router if needed. You can also check the Status page.
The product you selected has no build available right now. In the loader's product list, a product with a build shows an "updated: DD/MM/YY HH:MM" date. If the date is missing, check the Status page or contact support.
Your session token has expired or was revoked. Enter your username and password again.
The Windows WMI service isn't responding. Open a Command Prompt as administrator and run: net stop winmgmt net start winmgmt Then relaunch the loader.
The downloaded build is incomplete or was altered on your PC, usually by a connection drop or your antivirus. 1. Relaunch the loader: it downloads the build again. 2. Make sure your connection is stable: no VPN that drops, no weak Wi-Fi. If it keeps failing, try another network (Ethernet, or a phone hotspot) to rule out your router. 3. Add the loader folder to your antivirus / Windows Defender exclusions, then relaunch. 4. Check that you have at least 500 MB of free disk space.
Part of the build is missing, most often because an antivirus emptied or quarantined it. 1. Delete the loader and download it again from elusive.is (Downloads). 2. Before launching it, add its folder to your antivirus exclusions. 3. If your antivirus is very aggressive (Kaspersky, Avast), turn it off while you launch the product.
Windows ran out of memory while starting the product. 1. Close heavy apps (Chrome with many tabs, OBS, other games). 2. Restart your PC. 3. Make sure the Windows page file is enabled: Control Panel > System > Advanced system settings > Performance > Settings > Advanced > Virtual memory.
The build download was cut off before it finished (network drop during the transfer). 1. Relaunch the loader: downloading again usually fixes it. 2. Change network to rule out your connection: switch from Wi-Fi to Ethernet, or try a phone hotspot. 3. Turn off VPN, QoS and parental control on your router. 4. If you are far from Europe (Brazil, Asia) and it keeps failing, try a VPN to Europe.
Part of the build was modified on your PC, usually by an antivirus or security software. It can also be an incomplete download (see E04). 1. Add the loader folder to your antivirus exclusions (Defender, Avast, Kaspersky). 2. If you have company security software (CrowdStrike, SentinelOne, Sophos), turn it off temporarily. 3. Relaunch. If it still fails, try another network (Ethernet or a phone hotspot).
A Windows component the product needs could not be loaded: the Microsoft Visual C++ runtime is missing, or your antivirus quarantined a system file. 1. Install the Microsoft Visual C++ Redistributable 2015-2022 (x64): https://aka.ms/vs/17/release/vc_redist.x64.exe 2. Run Windows Update and install every pending update. 3. Check your antivirus quarantine and restore any Microsoft file listed there. 4. Open a Command Prompt as administrator and run: sfc /scannow
A Windows file the product needs is outdated, or was replaced by a non-Microsoft version (old Windows build, or another program placed its own DLL next to the loader). 1. Run Windows Update and install ALL updates. 2. Reinstall the Microsoft Visual C++ Redistributable 2015-2022 (x64): https://aka.ms/vs/17/release/vc_redist.x64.exe 3. Delete every .dll file in the loader folder: the loader downloads the ones it needs again at the next launch. 4. Open a Command Prompt as administrator and run: sfc /scannow
The product refused to start. This is rarely a loader problem: it usually comes from the DMA setup or the game. 1. Relaunch the loader. 2. Check that your DMA card is plugged in and detected. 3. If the product needs the game running first: start the game, then relaunch the loader. 4. If it keeps happening, restart both PCs.
The product stopped right after starting. The usual causes: the subscription has expired, you are on a different PC than the one your account is bound to (HWID), or the DMA card is not detected. 1. Check your Dashboard: the subscription for this product must be active. 2. Make sure you are on the PC you first logged in with. If you changed PC or hardware, see "How do I request a HWID reset?". 3. Check that your DMA card is plugged in and detected. 4. If everything looks right, open a support ticket with the error code and attach your session logs.
05After launching
Windows Defender has most likely quarantined it. Open Windows Security → Virus & threat protection → Protection history, restore the file, then add the loader folder to your exclusions.
That's expected. The loader is waiting for your game to start. Launch the game and within a few seconds the message should change to "attached to <game>.exe (pid …)".
The folder is created as soon as you select the product, before the download starts. If it stays empty, the loader printed an [Error] line just before. Read the console and find that error in the "Loader errors" section above.
This was fixed in recent versions. Download the latest loader from the Downloads page.
06Support
If nothing above fixes it, open a ticket and attach: • Session logs: <loader folder>\<product name>\logs\session_YYYY-MM-DD_HH-MM-SS.txt • Crash reports (if any): <loader folder>\<product name>\crashes\crash-YYYYMMDD-HHMMSS.log and the matching .dmp • A copy-paste of the full loader console output
Still stuck? A ticket from the panel reaches a person, with your account attached.