Instructions
Antilose setup guide for Genshin Impact
Antilose • Genshin Impact
Launching ANTILOSE for Genshin Impact, step by step: enable virtualization in BIOS, turn off the Windows protections that block the launch, unpack the archive to C:\antilose and run…
Instructions
Follow the steps in order: enable virtualization in BIOS, turn off the Windows protections that block the launch, unpack the archive to C:\antilose and run antilose.exe as administrator.
What you need to run it
Windows 10 (version 22H2, build 19045 or newer) or Windows 11, 64-bit (x64) only. To check: Win + I → System → About → System type and version.
An AMD CPU with SVM support (recommended) or an Intel CPU with VT-x support. On AMD the DLL is additionally hidden (EPT Ghost Page); Intel doesn't get this protection, everything else works the same.
At least 8 GB of RAM, administrator rights and a stable internet connection: the key is checked at launch.
You get the key after payment.
An AMD CPU with SVM support (recommended) or an Intel CPU with VT-x support. On AMD the DLL is additionally hidden (EPT Ghost Page); Intel doesn't get this protection, everything else works the same.
At least 8 GB of RAM, administrator rights and a stable internet connection: the key is checked at launch.
You get the key after payment.
Step 1. BIOS / UEFI
1. Restart your PC and during boot press Del or F2 (depends on your motherboard).
2. Open Advanced → CPU Configuration (or OC → Advanced CPU Settings).
3. Enable virtualization. On AMD it's SVM Mode (AMD-V, Secure Virtual Machine) → Enabled. On Intel it's Intel Virtualization Technology (VT-x, VMX) → Enabled; if available, also enable VT-d.
4. Under Boot (or Security) set Secure Boot to Disabled.
5. Save the settings and exit (F10 → Yes).
6. After the restart, press Win + R, type msinfo32 and check: BIOS Mode is UEFI, Secure Boot State is Off, virtualization is Enabled.
2. Open Advanced → CPU Configuration (or OC → Advanced CPU Settings).
3. Enable virtualization. On AMD it's SVM Mode (AMD-V, Secure Virtual Machine) → Enabled. On Intel it's Intel Virtualization Technology (VT-x, VMX) → Enabled; if available, also enable VT-d.
4. Under Boot (or Security) set Secure Boot to Disabled.
5. Save the settings and exit (F10 → Yes).
6. After the restart, press Win + R, type msinfo32 and check: BIOS Mode is UEFI, Secure Boot State is Off, virtualization is Enabled.
Step 2. HVCI, Hyper-V and conflicting programs
1. Turn off HVCI: Win + I → Privacy & security → Windows Security → Device security → Core isolation → Core isolation details → Memory integrity → Off. Restart your PC. This is the most common cause of problems on Windows 11.
2. If the setting has turned itself back on, open Command Prompt as administrator and run two commands: reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity" /v Enabled /t REG_DWORD /d 0 /f and reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard" /v EnableVirtualizationBasedSecurity /t REG_DWORD /d 0 /f. Then restart your PC.
3. Turn off Hyper-V with the command bcdedit /set hypervisorlaunchtype off and restart your PC. To turn it back on, use the command bcdedit /set hypervisorlaunchtype auto.
4. Before launching, close Docker Desktop, WSL2, Android emulators (BlueStacks, NoxPlayer, LDPlayer, MEmu), VMware Workstation, VirtualBox, Sandboxie, as well as Cheat Engine, x64dbg, IDA, Process Hacker and ReClass.
5. On AMD, Hyper-V together with Docker breaks the program: the driver sees a nested hypervisor (code 0xDB810004) and doesn't load.
2. If the setting has turned itself back on, open Command Prompt as administrator and run two commands: reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity" /v Enabled /t REG_DWORD /d 0 /f and reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard" /v EnableVirtualizationBasedSecurity /t REG_DWORD /d 0 /f. Then restart your PC.
3. Turn off Hyper-V with the command bcdedit /set hypervisorlaunchtype off and restart your PC. To turn it back on, use the command bcdedit /set hypervisorlaunchtype auto.
4. Before launching, close Docker Desktop, WSL2, Android emulators (BlueStacks, NoxPlayer, LDPlayer, MEmu), VMware Workstation, VirtualBox, Sandboxie, as well as Cheat Engine, x64dbg, IDA, Process Hacker and ReClass.
5. On AMD, Hyper-V together with Docker breaks the program: the driver sees a nested hypervisor (code 0xDB810004) and doesn't load.
Step 3. Antivirus and Windows Defender
1. Create the folder C:\antilose. The path must not contain Cyrillic letters or spaces; don't use the Desktop or Downloads folders, Defender scans them more aggressively.
2. Open Win + I → Privacy & security → Windows Security → Virus & threat protection → Manage settings → Exclusions → Add or remove exclusions.
3. Press Add an exclusion → Folder, select C:\antilose and confirm in UAC. Do this before downloading, otherwise Defender will delete the files right after unpacking.
4. If you use Kaspersky, ESET, Avast, AVG or Dr.Web, add C:\antilose to that antivirus's exclusions or temporarily disable it.
5. If files get deleted even from the excluded folder, go to "Manage settings" and turn off Tamper Protection and add the exclusion again.
6. If Defender has already deleted the files: Virus & threat protection → Protection history → find the file → Actions → Restore, then move it to C:\antilose.
2. Open Win + I → Privacy & security → Windows Security → Virus & threat protection → Manage settings → Exclusions → Add or remove exclusions.
3. Press Add an exclusion → Folder, select C:\antilose and confirm in UAC. Do this before downloading, otherwise Defender will delete the files right after unpacking.
4. If you use Kaspersky, ESET, Avast, AVG or Dr.Web, add C:\antilose to that antivirus's exclusions or temporarily disable it.
5. If files get deleted even from the excluded folder, go to "Manage settings" and turn off Tamper Protection and add the exclusion again.
6. If Defender has already deleted the files: Virus & threat protection → Protection history → find the file → Actions → Restore, then move it to C:\antilose.
Step 4. SmartScreen
1. If Windows says "Windows protected your PC" on first launch, click More info → Run anyway.
2. To stop this window from appearing: Windows Security → App & browser control → Reputation-based protection → Reputation-based protection settings → Check apps and files → Off.
2. To stop this window from appearing: Windows Security → App & browser control → Reputation-based protection → Reputation-based protection settings → Check apps and files → Off.
Step 5. Download and launch
1. Download the archive from the link https://telegra.ph/antilosewin-update-link-11-08: the page will have a link to the file.
2. Unpack the archive into C:\antilose. Don't run the program from inside the archive.
3. The folder must contain four files: antilose.exe, al_w_gi.dll, hyperland_driver.sys and iqvw64e.sys.
4. Right-click antilose.exe → Run as administrator and confirm in UAC. To avoid doing this every time, open Properties → Compatibility and check Run this program as an administrator.
5. Enter the key when the program asks for it.
6. After that, the program loads the driver, launches the game and injects the DLL on its own. Follow the prompts in the console and don't close its window: if you close it, the program stops.
7. The key's term starts the moment you enter it in the program, even if the program closes right away. If you've just bought a key, reinstalled Windows or changed PCs, contact support right away so you don't lose subscription days.
8. The menu has a Settings section with a toggle called Unlock Dangerous Functions. It covers the Multi Hit, Multi Animation, Quest TP, Map TP, Custom TP, Rapid Dialogs, Auto Loot, Auto Chests, Game Speed, Open Map, Auto Challenge and Kill Aura features.
2. Unpack the archive into C:\antilose. Don't run the program from inside the archive.
3. The folder must contain four files: antilose.exe, al_w_gi.dll, hyperland_driver.sys and iqvw64e.sys.
4. Right-click antilose.exe → Run as administrator and confirm in UAC. To avoid doing this every time, open Properties → Compatibility and check Run this program as an administrator.
5. Enter the key when the program asks for it.
6. After that, the program loads the driver, launches the game and injects the DLL on its own. Follow the prompts in the console and don't close its window: if you close it, the program stops.
7. The key's term starts the moment you enter it in the program, even if the program closes right away. If you've just bought a key, reinstalled Windows or changed PCs, contact support right away so you don't lose subscription days.
8. The menu has a Settings section with a toggle called Unlock Dangerous Functions. It covers the Multi Hit, Multi Animation, Quest TP, Map TP, Custom TP, Rapid Dialogs, Auto Loot, Auto Chests, Game Speed, Open Map, Auto Challenge and Kill Aura features.
Common problems
The file gets deleted right after downloading or unpacking — The folder isn't in Defender's exclusions. Go back to step 3 and add the exclusion before downloading.
"Windows protected your PC" — Click "More info" → "Run anyway" or turn off SmartScreen (step 4).
The program window flashes and closes — Open Command Prompt as administrator and run cd C:\antilose, then cmd /k antilose.exe. The window will stay open: take a screenshot of the error.
The program closes immediately, the log shows code 0xDB700002 — Sync the time on your PC: Win + I → Time & language → Date & time → Sync now. Because of the key check, an out-of-sync clock breaks the server response. If the time is correct, think back to when you entered the key: the term runs from the moment it was entered, and the key may have expired.
Access Denied or Driver load failed — Run the program as administrator, check that HVCI and Secure Boot are off, and disable any third-party antivirus.
BYOVD failed or vulnerable driver blocked — Windows blocked a system driver with its blocklist. Check that HVCI is off (step 2), then in Command Prompt as administrator run reg add "HKLM\SYSTEM\CurrentControlSet\Control\CI\Config" /v VulnerableDriverBlocklistEnable /t REG_DWORD /d 0 /f and restart your PC. If that doesn't help, contact support and include your Windows version (Win + R → winver).
DLL not found or Failed to load module — Check that all files are unpacked into one folder, that Defender hasn't deleted al_w_gi.dll (step 3) and that the path has no Cyrillic letters.
Blue screen on launch — Turn off Hyper-V (step 2), close Docker, WSL2 and emulators. Write down the error code (for example SYSTEM_SERVICE_EXCEPTION, CLOCK_WATCHDOG_TIMEOUT or 0xDEAD1337) and include it in your support request.
The game crashes right after the program starts — Restart the game and try again. Check that the program version matches the current game version, and open nero_debug.log in the game folder.
It worked but stopped after a Windows update — The update may have turned HVCI back on (step 2), updated the driver blocklist (see BYOVD above) or turned Secure Boot on after a BIOS update (step 1).
Crash after 2–3 seconds — A conflict with the antivirus or the game's protection.
Crash after 60 seconds — Key server connection timeout (code 0xDB700010): check your internet and restart the program.
Crash after a few minutes — The program version doesn't match the updated game.
"Windows protected your PC" — Click "More info" → "Run anyway" or turn off SmartScreen (step 4).
The program window flashes and closes — Open Command Prompt as administrator and run cd C:\antilose, then cmd /k antilose.exe. The window will stay open: take a screenshot of the error.
The program closes immediately, the log shows code 0xDB700002 — Sync the time on your PC: Win + I → Time & language → Date & time → Sync now. Because of the key check, an out-of-sync clock breaks the server response. If the time is correct, think back to when you entered the key: the term runs from the moment it was entered, and the key may have expired.
Access Denied or Driver load failed — Run the program as administrator, check that HVCI and Secure Boot are off, and disable any third-party antivirus.
BYOVD failed or vulnerable driver blocked — Windows blocked a system driver with its blocklist. Check that HVCI is off (step 2), then in Command Prompt as administrator run reg add "HKLM\SYSTEM\CurrentControlSet\Control\CI\Config" /v VulnerableDriverBlocklistEnable /t REG_DWORD /d 0 /f and restart your PC. If that doesn't help, contact support and include your Windows version (Win + R → winver).
DLL not found or Failed to load module — Check that all files are unpacked into one folder, that Defender hasn't deleted al_w_gi.dll (step 3) and that the path has no Cyrillic letters.
Blue screen on launch — Turn off Hyper-V (step 2), close Docker, WSL2 and emulators. Write down the error code (for example SYSTEM_SERVICE_EXCEPTION, CLOCK_WATCHDOG_TIMEOUT or 0xDEAD1337) and include it in your support request.
The game crashes right after the program starts — Restart the game and try again. Check that the program version matches the current game version, and open nero_debug.log in the game folder.
It worked but stopped after a Windows update — The update may have turned HVCI back on (step 2), updated the driver blocklist (see BYOVD above) or turned Secure Boot on after a BIOS update (step 1).
Crash after 2–3 seconds — A conflict with the antivirus or the game's protection.
Crash after 60 seconds — Key server connection timeout (code 0xDB700010): check your internet and restart the program.
Crash after a few minutes — The program version doesn't match the updated game.
Error codes
0xDB500001 — Initialization error: the library has probably been intercepted. Disable your antivirus and reinstall the program; for Kaspersky and ESET, add it to trusted apps.
0xDB600001, 0xDB600006, 0xDB600007, 0xDB610001, 0xDB610002, 0xDB610003 — Debugger detected. Close x64dbg, IDA, Cheat Engine, Process Hacker and ReClass.
0xDB600002 — The import table was modified: something is hooking the API. Close programs that use hooks; antivirus software can hook too.
0xDB600009 — The protection thread was terminated from outside, possibly by an antivirus. Disable it.
0xDB610004 — Hardware breakpoints detected. Close Cheat Engine and x64dbg.
0xDB610005 — Timing anomaly: the system is overloaded or a debugger is running. Close heavy programs.
0xDB610006 — Remote debugger. Turn off debugging over RDP.
0xDB610007 — Instrumentation hook. Close tracers and profilers.
0xDB700001 — No connection to the key server. Check your internet, turn off VPN and proxy: an antivirus may also have blocked the connection.
0xDB700002 — Key check failed. Sync the time on your PC (Win + I → Time & language → Date & time → Sync now), check the key and its expiry date.
0xDB700003 — License file not found: nero_license.dat must be in C:\Windows\System32\.
0xDB700010 — Connection timeout. Check your internet and restart the program.
0xDB700011, 0xDB700012 — The server response or checksum verification failed. Contact support.
0xDB700020, 0xDB700021, 0xDB000CFF — The file is corrupted or the import table protection failed. Download the archive again directly into the excluded folder and reinstall the program.
0xDB800001 — Key check failed: the key is invalid or a debugger is running. Restart the program.
0xDB810001, 0xDB810003 — Kernel debugging detected. Close WinDbg, run bcdedit /debug off, and turn off COM port debugging.
0xDB810002 — The driver isn't responding: three checks in a row were missed. Restart the program.
0xDB810004 — Hypervisor conflict: Hyper-V, VMware or Docker. Turn them off (step 2).
STATUS_INSUFFICIENT_RESOURCES (0xC000009A) — Driver blocklist: see step 2 and the BYOVD item under "Common problems".
STATUS_ACCESS_DENIED (0xC0000022) — No administrator rights. Run it as administrator.
STATUS_OBJECT_NAME_NOT_FOUND (0xC0000034) — The .sys file wasn't found. Check that the folder contains all the files.
STATUS_IMAGE_CERT_REVOKED (0xC0000603) — The driver certificate has been revoked. Turn off Secure Boot (step 1).
CLOCK_WATCHDOG_TIMEOUT (0x101) — Hypervisor conflict. Turn off Hyper-V, Docker and WSL2 (step 2).
SYSTEM_SERVICE_EXCEPTION (0x3B) — An error in kernel-mode code. Contact support and include your Windows version.
KERNEL_DATA_INPAGE_ERROR (0x7A) — Kernel memory read error: a problem with the disk or RAM. Run sfc /scannow.
0xDB600001, 0xDB600006, 0xDB600007, 0xDB610001, 0xDB610002, 0xDB610003 — Debugger detected. Close x64dbg, IDA, Cheat Engine, Process Hacker and ReClass.
0xDB600002 — The import table was modified: something is hooking the API. Close programs that use hooks; antivirus software can hook too.
0xDB600009 — The protection thread was terminated from outside, possibly by an antivirus. Disable it.
0xDB610004 — Hardware breakpoints detected. Close Cheat Engine and x64dbg.
0xDB610005 — Timing anomaly: the system is overloaded or a debugger is running. Close heavy programs.
0xDB610006 — Remote debugger. Turn off debugging over RDP.
0xDB610007 — Instrumentation hook. Close tracers and profilers.
0xDB700001 — No connection to the key server. Check your internet, turn off VPN and proxy: an antivirus may also have blocked the connection.
0xDB700002 — Key check failed. Sync the time on your PC (Win + I → Time & language → Date & time → Sync now), check the key and its expiry date.
0xDB700003 — License file not found: nero_license.dat must be in C:\Windows\System32\.
0xDB700010 — Connection timeout. Check your internet and restart the program.
0xDB700011, 0xDB700012 — The server response or checksum verification failed. Contact support.
0xDB700020, 0xDB700021, 0xDB000CFF — The file is corrupted or the import table protection failed. Download the archive again directly into the excluded folder and reinstall the program.
0xDB800001 — Key check failed: the key is invalid or a debugger is running. Restart the program.
0xDB810001, 0xDB810003 — Kernel debugging detected. Close WinDbg, run bcdedit /debug off, and turn off COM port debugging.
0xDB810002 — The driver isn't responding: three checks in a row were missed. Restart the program.
0xDB810004 — Hypervisor conflict: Hyper-V, VMware or Docker. Turn them off (step 2).
STATUS_INSUFFICIENT_RESOURCES (0xC000009A) — Driver blocklist: see step 2 and the BYOVD item under "Common problems".
STATUS_ACCESS_DENIED (0xC0000022) — No administrator rights. Run it as administrator.
STATUS_OBJECT_NAME_NOT_FOUND (0xC0000034) — The .sys file wasn't found. Check that the folder contains all the files.
STATUS_IMAGE_CERT_REVOKED (0xC0000603) — The driver certificate has been revoked. Turn off Secure Boot (step 1).
CLOCK_WATCHDOG_TIMEOUT (0x101) — Hypervisor conflict. Turn off Hyper-V, Docker and WSL2 (step 2).
SYSTEM_SERVICE_EXCEPTION (0x3B) — An error in kernel-mode code. Contact support and include your Windows version.
KERNEL_DATA_INPAGE_ERROR (0x7A) — Kernel memory read error: a problem with the disk or RAM. Run sfc /scannow.
If nothing helped
Blue screen with code 0xDEAD1337: the second parameter in brackets is the code from the table above, for example 0xDEAD1337 (0xDB810001, 0, 0, 0) means 0xDB810001. If the error screen wasn't saved, after restarting open Win + R → eventvwr.msc → Windows Logs → System and find the BugCheck event.
On a crash, the program writes the log nero_debug.log. If the DLL crashed, the log is in the game folder, for example C:\Program Files\Genshin Impact\Genshin Impact Game\. The last lines contain the error code; look it up in the table above.
If there's no code, contact support: https://t.me/CheatForce_support_bot. Include your Windows version (Win + R → winver), CPU model (AMD or Intel), game version, a screenshot of the program console, the contents of nero_debug.log and the time from launch to crash.
On a crash, the program writes the log nero_debug.log. If the DLL crashed, the log is in the game folder, for example C:\Program Files\Genshin Impact\Genshin Impact Game\. The last lines contain the error code; look it up in the table above.
If there's no code, contact support: https://t.me/CheatForce_support_bot. Include your Windows version (Win + R → winver), CPU model (AMD or Intel), game version, a screenshot of the program console, the contents of nero_debug.log and the time from launch to crash.