Problems & fixes, Escape From Tarkov

This is a common issue caused by Windows driver security components. Follow these steps:

• Download the Sordum utility (archive password: sordum), run it, click Search, and wait for it to finish.
• Apply the win_driver_OFF.reg file provided by support — it disables Windows driver signature enforcement. Reboot your PC afterwards.
• Make sure User Account Control (UAC) is disabled — the loader handles this automatically, but verify it manually if needed.
• If the issue persists, run sc query vgk, sc query faceit, sc query wdfilter in CMD and send a screenshot to support.

This is a common issue caused by Windows driver security components. Follow these steps:

• Download the Sordum utility (archive password: sordum), run it, click Search, and wait for it to finish.
• Apply the win_driver_OFF.reg file provided by support — it disables Windows driver signature enforcement. Reboot your PC afterwards.
• Make sure User Account Control (UAC) is disabled — the loader handles this automatically, but verify it manually if needed.
• If the issue persists, run sc query vgk, sc query faceit, sc query wdfilter in CMD and send a screenshot to support.

This is a common issue caused by Windows driver security components. Follow these steps:

• Download the Sordum utility (archive password: sordum), run it, click Search, and wait for it to finish.
• Apply the win_driver_OFF.reg file provided by support — it disables Windows driver signature enforcement. Reboot your PC afterwards.
• Make sure User Account Control (UAC) is disabled — the loader handles this automatically, but verify it manually if needed.
• If the issue persists, run sc query vgk, sc query faceit, sc query wdfilter in CMD and send a screenshot to support.

This is a common issue caused by Windows driver security components. Follow these steps:

• Download the Sordum utility (archive password: sordum), run it, click Search, and wait for it to finish.
• Apply the win_driver_OFF.reg file provided by support — it disables Windows driver signature enforcement. Reboot your PC afterwards.
• Make sure User Account Control (UAC) is disabled — the loader handles this automatically, but verify it manually if needed.
• If the issue persists, run sc query vgk, sc query faceit, sc query wdfilter in CMD and send a screenshot to support.

This is a common issue caused by Windows driver security components. Follow these steps:

• Download the Sordum utility (archive password: sordum), run it, click Search, and wait for it to finish.
• Apply the win_driver_OFF.reg file provided by support — it disables Windows driver signature enforcement. Reboot your PC afterwards.
• Make sure User Account Control (UAC) is disabled — the loader handles this automatically, but verify it manually if needed.
• If the issue persists, run sc query vgk, sc query faceit, sc query wdfilter in CMD and send a screenshot to support.

This is a common issue caused by Windows driver security components. Follow these steps:

• Download the Sordum utility (archive password: sordum), run it, click Search, and wait for it to finish.
• Apply the win_driver_OFF.reg file provided by support — it disables Windows driver signature enforcement. Reboot your PC afterwards.
• Make sure User Account Control (UAC) is disabled — the loader handles this automatically, but verify it manually if needed.
• If the issue persists, run sc query vgk, sc query faceit, sc query wdfilter in CMD and send a screenshot to support.

This is a common issue caused by Windows driver security components. Follow these steps:

• Download the Sordum utility (archive password: sordum), run it, click Search, and wait for it to finish.
• Apply the win_driver_OFF.reg file provided by support — it disables Windows driver signature enforcement. Reboot your PC afterwards.
• Make sure User Account Control (UAC) is disabled — the loader handles this automatically, but verify it manually if needed.
• If the issue persists, run sc query vgk, sc query faceit, sc query wdfilter in CMD and send a screenshot to support.

This is a common issue caused by Windows driver security components. Follow these steps:

• Download the Sordum utility (archive password: sordum), run it, click Search, and wait for it to finish.
• Apply the win_driver_OFF.reg file provided by support — it disables Windows driver signature enforcement. Reboot your PC afterwards.
• Make sure User Account Control (UAC) is disabled — the loader handles this automatically, but verify it manually if needed.
• If the issue persists, run sc query vgk, sc query faceit, sc query wdfilter in CMD and send a screenshot to support.

This is a common issue caused by Windows driver security components. Follow these steps:

• Download the Sordum utility (archive password: sordum), run it, click Search, and wait for it to finish.
• Apply the win_driver_OFF.reg file provided by support — it disables Windows driver signature enforcement. Reboot your PC afterwards.
• Make sure User Account Control (UAC) is disabled — the loader handles this automatically, but verify it manually if needed.
• If the issue persists, run sc query vgk, sc query faceit, sc query wdfilter in CMD and send a screenshot to support.

This is a common issue caused by Windows driver security components. Follow these steps:

• Download the Sordum utility (archive password: sordum), run it, click Search, and wait for it to finish.
• Apply the win_driver_OFF.reg file provided by support — it disables Windows driver signature enforcement. Reboot your PC afterwards.
• Make sure User Account Control (UAC) is disabled — the loader handles this automatically, but verify it manually if needed.
• If the issue persists, run sc query vgk, sc query faceit, sc query wdfilter in CMD and send a screenshot to support.

This is a common issue caused by Windows driver security components. Follow these steps:

• Download the Sordum utility (archive password: sordum), run it, click Search, and wait for it to finish.
• Apply the win_driver_OFF.reg file provided by support — it disables Windows driver signature enforcement. Reboot your PC afterwards.
• Make sure User Account Control (UAC) is disabled — the loader handles this automatically, but verify it manually if needed.
• If the issue persists, run sc query vgk, sc query faceit, sc query wdfilter in CMD and send a screenshot to support.

This is a common issue caused by Windows driver security components. Follow these steps:

• Download the Sordum utility (archive password: sordum), run it, click Search, and wait for it to finish.
• Apply the win_driver_OFF.reg file provided by support — it disables Windows driver signature enforcement. Reboot your PC afterwards.
• Make sure User Account Control (UAC) is disabled — the loader handles this automatically, but verify it manually if needed.
• If the issue persists, run sc query vgk, sc query faceit, sc query wdfilter in CMD and send a screenshot to support.

These errors indicate a previous load did not complete cleanly, or conflicting anticheat software is present on the system.

• Uninstall Vanguard (Valorant Anti-Cheat) and FaceIt AC if they are installed.
• Download the Sordum utility (archive password: sordum), run it, click «Search», and wait for it to finish.
• Perform a full PC restart and make sure Windows Defender is disabled.
• Launch the loader as Administrator.

This is a common issue caused by Windows driver security components. Follow these steps:

• Download the Sordum utility (archive password: sordum), run it, click Search, and wait for it to finish.
• Apply the win_driver_OFF.reg file provided by support , it disables Windows driver signature enforcement. Reboot your PC afterwards.
• Make sure User Account Control (UAC) is disabled , the loader handles this automatically, but verify it manually if needed.
• If the issue persists, run sc query vgk, sc query faceit, sc query wdfilter in CMD and send a screenshot to support.

If the game crashes or your PC reboots after injection, start with a system diagnostic. Download the Sordum utility (archive password: sordum), run it, click Search, and wait for the scan to finish.

Take a screenshot of the results and send it to support , the developer will use this data to identify the cause and fix the launch issue for your system.

Loader connection errors are usually caused by ISP-level blocking. Try the following steps:

• Enable a VPN (any country), launch the loader and click Inject. Once injected successfully, disable the VPN before starting the game.
• If VPN does not help: download the networkmanager.zip utility, run it, select «Find Best IP» and click Apply. Then try launching the loader again.

Loader connection errors are usually caused by ISP-level blocking. Try the following steps:

• Enable a VPN (any country), launch the loader and click Inject. Once injected successfully, disable the VPN before starting the game.
• If VPN does not help: download the networkmanager.zip utility, run it, select «Find Best IP» and click Apply. Then try launching the loader again.

Loader connection errors are usually caused by ISP-level blocking. Try the following steps:

• Enable a VPN (any country), launch the loader and click Inject. Once injected successfully, disable the VPN before starting the game.
• If VPN does not help: download the networkmanager.zip utility, run it, select «Find Best IP» and click Apply. Then try launching the loader again.

Loader connection errors are usually caused by ISP-level blocking. Try the following steps:

• Enable a VPN (any country), launch the loader and click Inject. Once injected successfully, disable the VPN before starting the game.
• If VPN does not help: download the networkmanager.zip utility, run it, select «Find Best IP» and click Apply. Then try launching the loader again.

Loader connection errors are usually caused by ISP-level blocking. Try the following steps:

• Enable a VPN (any country), launch the loader and click Inject. Once injected successfully, disable the VPN before starting the game.
• If VPN does not help: download the networkmanager.zip utility, run it, select «Find Best IP» and click Apply. Then try launching the loader again.

Loader connection errors are usually caused by ISP-level blocking. Try the following steps:

• Enable a VPN (any country), launch the loader and click Inject. Once injected successfully, disable the VPN before starting the game.
• If VPN does not help: download the networkmanager.zip utility, run it, select «Find Best IP» and click Apply. Then try launching the loader again.

Loader connection errors are usually caused by ISP-level blocking. Try the following steps:

• Enable a VPN (any country), launch the loader and click Inject. Once injected successfully, disable the VPN before starting the game.
• If VPN does not help: download the networkmanager.zip utility, run it, select «Find Best IP» and click Apply. Then try launching the loader again.

Loader connection errors are usually caused by ISP-level blocking. Try the following steps:

• Enable a VPN (any country), launch the loader and click Inject. Once injected successfully, disable the VPN before starting the game.
• If VPN does not help: download the networkmanager.zip utility, run it, select «Find Best IP» and click Apply. Then try launching the loader again.

Loader connection errors are usually caused by ISP-level blocking. Try the following steps:

• Enable a VPN (any country), launch the loader and click Inject. Once injected successfully, disable the VPN before starting the game.
• If VPN does not help: download the networkmanager.zip utility, run it, select «Find Best IP» and click Apply. Then try launching the loader again.

Loader connection errors are usually caused by ISP-level blocking. Try the following steps:

• Enable a VPN (any country), launch the loader and click Inject. Once injected successfully, disable the VPN before starting the game.
• If VPN does not help: download the networkmanager.zip utility, run it, select «Find Best IP» and click Apply. Then try launching the loader again.

Loader connection errors are usually caused by ISP-level blocking. Try the following steps:

• Enable a VPN (any country), launch the loader and click Inject. Once injected successfully, disable the VPN before starting the game.
• If VPN does not help: download the networkmanager.zip utility, run it, select «Find Best IP» and click Apply. Then try launching the loader again.

Switch the game to Borderless Window mode , fullscreen conflicts with the injector.

If crashes persist, repair system files. Open cmd as Administrator and run each command, waiting for it to finish:

• DISM /Online /Cleanup-Image /RestoreHealth
• sfc /scannow

Then reboot. Blue screens on the Terminal map are a known game-side issue unrelated to the cheat.

This issue is usually caused by network-level blocking. Try the following steps:

• Enable a VPN and relaunch the loader.
• Download the Network Manager utility, run it, select "Find Best IP", wait for the scan to finish, click "Apply", then relaunch the loader.

System freeze when entering the key is usually caused by HDR or antivirus conflicts. Do the following in order:

• Disable HDR in Windows display settings.
• Disable Windows Defender and make sure any third-party antivirus (e.g. Kaspersky) is fully uninstalled.
• Run the Sordum utility to disable system security drivers, then reboot your PC.

System freeze when entering the key is usually caused by HDR or antivirus conflicts. Do the following in order:

• Disable HDR in Windows display settings.
• Disable Windows Defender and make sure any third-party antivirus (e.g. Kaspersky) is fully uninstalled.
• Run the Sordum utility to disable system security drivers, then reboot your PC.

System freeze when entering the key is usually caused by HDR or antivirus conflicts. Do the following in order:

• Disable HDR in Windows display settings.
• Disable Windows Defender and make sure any third-party antivirus (e.g. Kaspersky) is fully uninstalled.
• Run the Sordum utility to disable system security drivers, then reboot your PC.

System freeze when entering the key is usually caused by HDR or antivirus conflicts. Do the following in order:

• Disable HDR in Windows display settings.
• Disable Windows Defender and make sure any third-party antivirus (e.g. Kaspersky) is fully uninstalled.
• Run the Sordum utility to disable system security drivers, then reboot your PC.

System freeze when entering the key is usually caused by HDR or antivirus conflicts. Do the following in order:

• Disable HDR in Windows display settings.
• Disable Windows Defender and make sure any third-party antivirus (e.g. Kaspersky) is fully uninstalled.
• Run the Sordum utility to disable system security drivers, then reboot your PC.

System freeze when entering the key is usually caused by HDR or antivirus conflicts. Do the following in order:

• Disable HDR in Windows display settings.
• Disable Windows Defender and make sure any third-party antivirus (e.g. Kaspersky) is fully uninstalled.
• Run the Sordum utility to disable system security drivers, then reboot your PC.

System freeze when entering the key is usually caused by HDR or antivirus conflicts. Do the following in order:

• Disable HDR in Windows display settings.
• Disable Windows Defender and make sure any third-party antivirus (e.g. Kaspersky) is fully uninstalled.
• Run the Sordum utility to disable system security drivers, then reboot your PC.

System freeze when entering the key is usually caused by HDR or antivirus conflicts. Do the following in order:

• Disable HDR in Windows display settings.
• Disable Windows Defender and make sure any third-party antivirus (e.g. Kaspersky) is fully uninstalled.
• Run the Sordum utility to disable system security drivers, then reboot your PC.

System freeze when entering the key is usually caused by HDR or antivirus conflicts. Do the following in order:

• Disable HDR in Windows display settings.
• Disable Windows Defender and make sure any third-party antivirus (e.g. Kaspersky) is fully uninstalled.
• Run the Sordum utility to disable system security drivers, then reboot your PC.

System freeze when entering the key is usually caused by HDR or antivirus conflicts. Do the following in order:

• Disable HDR in Windows display settings.
• Disable Windows Defender and make sure any third-party antivirus (e.g. Kaspersky) is fully uninstalled.
• Run the Sordum utility to disable system security drivers, then reboot your PC.

System freeze when entering the key is usually caused by HDR or antivirus conflicts. Do the following in order:

• Disable HDR in Windows display settings.
• Disable Windows Defender and make sure any third-party antivirus (e.g. Kaspersky) is fully uninstalled.
• Run the Sordum utility to disable system security drivers, then reboot your PC.

System freeze when entering the key is usually caused by HDR or antivirus conflicts. Do the following in order:

• Disable HDR in Windows display settings.
• Disable Windows Defender and make sure any third-party antivirus (e.g. Kaspersky) is fully uninstalled.
• Run the Sordum utility to disable system security drivers, then reboot your PC.

The most common cause is third-party antivirus or security software blocking the loader. Completely uninstall 360 Total Security, Vanguard (Valorant anti-cheat — must be uninstalled, not just disabled), and any other third-party antivirus.

After removal: download the Sordum utility (archive password — sordum), run it, click Search, and wait for it to finish. Then reboot your PC and try launching the loader again.

If errors persist, send a screenshot of your installed programs list to support. As a last resort, a clean Windows reinstall resolves the issue.

The most common cause is third-party antivirus or security software blocking the loader. Completely uninstall 360 Total Security, Vanguard (Valorant anti-cheat — must be uninstalled, not just disabled), and any other third-party antivirus.

After removal: download the Sordum utility (archive password — sordum), run it, click Search, and wait for it to finish. Then reboot your PC and try launching the loader again.

If errors persist, send a screenshot of your installed programs list to support. As a last resort, a clean Windows reinstall resolves the issue.

The most common cause is third-party antivirus or security software blocking the loader. Completely uninstall 360 Total Security, Vanguard (Valorant anti-cheat — must be uninstalled, not just disabled), and any other third-party antivirus.

After removal: download the Sordum utility (archive password — sordum), run it, click Search, and wait for it to finish. Then reboot your PC and try launching the loader again.

If errors persist, send a screenshot of your installed programs list to support. As a last resort, a clean Windows reinstall resolves the issue.

The most common cause is third-party antivirus or security software blocking the loader. Completely uninstall 360 Total Security, Vanguard (Valorant anti-cheat — must be uninstalled, not just disabled), and any other third-party antivirus.

After removal: download the Sordum utility (archive password — sordum), run it, click Search, and wait for it to finish. Then reboot your PC and try launching the loader again.

If errors persist, send a screenshot of your installed programs list to support. As a last resort, a clean Windows reinstall resolves the issue.

The most common cause is third-party antivirus or security software blocking the loader. Completely uninstall 360 Total Security, Vanguard (Valorant anti-cheat — must be uninstalled, not just disabled), and any other third-party antivirus.

After removal: download the Sordum utility (archive password — sordum), run it, click Search, and wait for it to finish. Then reboot your PC and try launching the loader again.

If errors persist, send a screenshot of your installed programs list to support. As a last resort, a clean Windows reinstall resolves the issue.

The most common cause is third-party antivirus or security software blocking the loader. Completely uninstall 360 Total Security, Vanguard (Valorant anti-cheat — must be uninstalled, not just disabled), and any other third-party antivirus.

After removal: download the Sordum utility (archive password — sordum), run it, click Search, and wait for it to finish. Then reboot your PC and try launching the loader again.

If errors persist, send a screenshot of your installed programs list to support. As a last resort, a clean Windows reinstall resolves the issue.

The most common cause is third-party antivirus or security software blocking the loader. Completely uninstall 360 Total Security, Vanguard (Valorant anti-cheat — must be uninstalled, not just disabled), and any other third-party antivirus.

After removal: download the Sordum utility (archive password — sordum), run it, click Search, and wait for it to finish. Then reboot your PC and try launching the loader again.

If errors persist, send a screenshot of your installed programs list to support. As a last resort, a clean Windows reinstall resolves the issue.

The most common cause is third-party antivirus or security software blocking the loader. Completely uninstall 360 Total Security, Vanguard (Valorant anti-cheat — must be uninstalled, not just disabled), and any other third-party antivirus.

After removal: download the Sordum utility (archive password — sordum), run it, click Search, and wait for it to finish. Then reboot your PC and try launching the loader again.

If errors persist, send a screenshot of your installed programs list to support. As a last resort, a clean Windows reinstall resolves the issue.

The most common cause is third-party antivirus or security software blocking the loader. Completely uninstall 360 Total Security, Vanguard (Valorant anti-cheat — must be uninstalled, not just disabled), and any other third-party antivirus.

After removal: download the Sordum utility (archive password — sordum), run it, click Search, and wait for it to finish. Then reboot your PC and try launching the loader again.

If errors persist, send a screenshot of your installed programs list to support. As a last resort, a clean Windows reinstall resolves the issue.

The most common cause is third-party antivirus or security software blocking the loader. Completely uninstall 360 Total Security, Vanguard (Valorant anti-cheat — must be uninstalled, not just disabled), and any other third-party antivirus.

After removal: download the Sordum utility (archive password — sordum), run it, click Search, and wait for it to finish. Then reboot your PC and try launching the loader again.

If errors persist, send a screenshot of your installed programs list to support. As a last resort, a clean Windows reinstall resolves the issue.

The most common cause is third-party antivirus or security software blocking the loader. Completely uninstall 360 Total Security, Vanguard (Valorant anti-cheat — must be uninstalled, not just disabled), and any other third-party antivirus.

After removal: download the Sordum utility (archive password — sordum), run it, click Search, and wait for it to finish. Then reboot your PC and try launching the loader again.

If errors persist, send a screenshot of your installed programs list to support. As a last resort, a clean Windows reinstall resolves the issue.

The most common cause is third-party antivirus or security software blocking the loader. Completely uninstall 360 Total Security, Vanguard (Valorant anti-cheat — must be uninstalled, not just disabled), and any other third-party antivirus.

After removal: download the Sordum utility (archive password — sordum), run it, click Search, and wait for it to finish. Then reboot your PC and try launching the loader again.

If errors persist, send a screenshot of your installed programs list to support. As a last resort, a clean Windows reinstall resolves the issue.

The most common cause is third-party antivirus or security software blocking the loader. Completely uninstall 360 Total Security, Vanguard (Valorant anti-cheat — must be uninstalled, not just disabled), and any other third-party antivirus.

After removal: download the Sordum utility (archive password — sordum), run it, click Search, and wait for it to finish. Then reboot your PC and try launching the loader again.

If errors persist, send a screenshot of your installed programs list to support. As a last resort, a clean Windows reinstall resolves the issue.

Third-party antivirus software (especially Kaspersky and Norton) conflicts with the launcher. You need to fully uninstall the antivirus — disabling it is not enough.

• Uninstall Kaspersky / Norton via "Programs and Features" or the vendor's dedicated removal tool.
• Restart your PC after uninstalling.
• Make sure no antivirus components remain in the installed programs list.
• Windows Defender is sufficient — disable real-time protection temporarily if prompted.

Make sure your antivirus is completely removed , including Kaspersky and Windows Defender. Uninstalling from Programs is not enough; remnants can still run in the background. Use the sordum utility (archive password: sordum): download it, launch it, click Search, and wait for it to finish.

If the issue persists, connect a VPN and try again. In Windows Defender settings, disable the reputation-based protection (Trusted Driver or similar option).

The loader requires Hyper-V to be fully disabled and no PIN or password set in Windows sign-in options. First, remove PIN and password: Settings → Accounts → Sign-in options.

Then open PowerShell as Administrator and run the following commands one by one:

• 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"

After running all commands, reboot your PC and launch the loader again.

Faceit Anticheat and Vanguard (Valorant AC) load before Windows starts at the driver level and block unsigned cheat drivers, even if they appear disabled inside Windows.

You must fully uninstall these programs , disabling them is not enough. Reboot after uninstalling and try launching the loader again.

A blue screen when activating the cheat usually indicates a driver conflict. Follow these steps:

• Apply the win11_driver_OFF.reg file from support and reboot your PC.
• Disable Core Isolation / Memory Integrity in Windows Security settings.
• Make sure your Windows version is supported (10 or 11 21H2,23H2).

If BSOD only occurs with the spoofer enabled, try running the cheat without it.

Run a system file repair: open Command Prompt as Administrator and execute two commands — first DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. After that, make sure Fast Boot is disabled in BIOS/UEFI, then reboot.

If the issue persists, a clean Windows reinstall is required. Use the Pro edition only — Home versions may lack required components for the loader to function correctly.

Run a system file repair: open Command Prompt as Administrator and execute two commands — first DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. After that, make sure Fast Boot is disabled in BIOS/UEFI, then reboot.

If the issue persists, a clean Windows reinstall is required. Use the Pro edition only — Home versions may lack required components for the loader to function correctly.

Run a system file repair: open Command Prompt as Administrator and execute two commands — first DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. After that, make sure Fast Boot is disabled in BIOS/UEFI, then reboot.

If the issue persists, a clean Windows reinstall is required. Use the Pro edition only — Home versions may lack required components for the loader to function correctly.

Run a system file repair: open Command Prompt as Administrator and execute two commands — first DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. After that, make sure Fast Boot is disabled in BIOS/UEFI, then reboot.

If the issue persists, a clean Windows reinstall is required. Use the Pro edition only — Home versions may lack required components for the loader to function correctly.

Run a system file repair: open Command Prompt as Administrator and execute two commands — first DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. After that, make sure Fast Boot is disabled in BIOS/UEFI, then reboot.

If the issue persists, a clean Windows reinstall is required. Use the Pro edition only — Home versions may lack required components for the loader to function correctly.

Run a system file repair: open Command Prompt as Administrator and execute two commands — first DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. After that, make sure Fast Boot is disabled in BIOS/UEFI, then reboot.

If the issue persists, a clean Windows reinstall is required. Use the Pro edition only — Home versions may lack required components for the loader to function correctly.

Run a system file repair: open Command Prompt as Administrator and execute two commands — first DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. After that, make sure Fast Boot is disabled in BIOS/UEFI, then reboot.

If the issue persists, a clean Windows reinstall is required. Use the Pro edition only — Home versions may lack required components for the loader to function correctly.

Run a system file repair: open Command Prompt as Administrator and execute two commands — first DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. After that, make sure Fast Boot is disabled in BIOS/UEFI, then reboot.

If the issue persists, a clean Windows reinstall is required. Use the Pro edition only — Home versions may lack required components for the loader to function correctly.

Run a system file repair: open Command Prompt as Administrator and execute two commands — first DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. After that, make sure Fast Boot is disabled in BIOS/UEFI, then reboot.

If the issue persists, a clean Windows reinstall is required. Use the Pro edition only — Home versions may lack required components for the loader to function correctly.

Run a system file repair: open Command Prompt as Administrator and execute two commands — first DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. After that, make sure Fast Boot is disabled in BIOS/UEFI, then reboot.

If the issue persists, a clean Windows reinstall is required. Use the Pro edition only — Home versions may lack required components for the loader to function correctly.

Run a system file repair: open Command Prompt as Administrator and execute two commands — first DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. After that, make sure Fast Boot is disabled in BIOS/UEFI, then reboot.

If the issue persists, a clean Windows reinstall is required. Use the Pro edition only — Home versions may lack required components for the loader to function correctly.

Run a system file repair: open Command Prompt as Administrator and execute two commands — first DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. After that, make sure Fast Boot is disabled in BIOS/UEFI, then reboot.

If the issue persists, a clean Windows reinstall is required. Use the Pro edition only — Home versions may lack required components for the loader to function correctly.

Run a system file repair: open Command Prompt as Administrator and execute two commands — first DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. After that, make sure Fast Boot is disabled in BIOS/UEFI, then reboot.

If the issue persists, a clean Windows reinstall is required. Use the Pro edition only — Home versions may lack required components for the loader to function correctly.

Some browsers have built-in protection that blocks downloading and running loader executable files.

• Open browser settings and disable the built-in protection feature (e.g. Protect / Safe Browsing).
• If the file still won't download from the main server, install the MEGA extension and download via it.
• Note: each user gets an individual launcher file — it cannot be shared with others.

If the loader throws an error on startup, first try connecting a VPN — the VPN is only required during the download and activation stage; once the loader is running you can disconnect it.

If VPN does not help, check the following in BIOS and Windows settings:

• Secure Boot must be disabled in BIOS.
• Core Isolation (Memory Integrity) must be disabled. Find it in Windows Security → Device Security → Core Isolation.

After changing these settings, reboot and try launching the loader again.

Yes, this is a false positive. The loader is protected with obfuscation and VMProtect — standard anti-reverse-engineering measures that antivirus software often flags as suspicious. The file is safe. Before launching, disable real-time protection in Windows Defender and add the loader folder to exclusions.

To diagnose the issue, follow these steps:

• Download the Sordum utility (archive password: sordum).
• Run it, click Search, and wait for the scan to finish.
• Take a screenshot of the result and send it to support , this allows the team to identify the exact cause.

Anticheat errors and loader crashes when starting the game are typically resolved by enabling a VPN. Connect to a VPN, then relaunch the loader and the game.

Also ensure Windows Defender is disabled (e.g. via Defender Control), no third-party antivirus is running, and no unnecessary background software is active.

If after injection only the loader window appears and the cheat menu never shows, follow these steps:

• Download the Sordum utility (archive password: sordum).
• Run it, click Search, and wait for it to finish.
• Take a screenshot of the result, then repeat the loader launch procedure.

This clears conflicting processes that prevent the menu from appearing.

Restart your computer. If the error persists, re-download the loader from the website and launch the fresh version , this resolves most connection issues after an update.

Restart your computer. If the error persists, re-download the loader from the website and launch the fresh version , this resolves most connection issues after an update.

The cause is an antivirus blocking the cheat. Fully uninstall all third-party antivirus software (Avast, Kaspersky, etc.) , disabling them is not enough.

After uninstalling, reboot your PC, re-download the cheat, and launch it again.

Loader connection errors are usually caused by ISP-level blocking. Try the following steps:

• Enable a VPN (any country works), launch the loader and click Inject. Once injected successfully, disable the VPN before starting Tarkov.
• If VPN doesn't help: download the networkmanager.zip utility, run it, select «Find Best IP» and click Apply. Then try launching the loader again.

Download the Sordum utility (archive password: sordum). Run it, click the Search button, and wait for the scan to finish.

This resolves conflicts with system components that cause the launcher to fail with a 'file corrupted' error or trigger a PC restart. After the scan completes, try launching the radar again.

If the cheat menu does not appear after inject, download the Sordum utility (archive password: sordum). Launch it, click Search and wait for the scan to finish. Take a screenshot of the result and contact support , this helps diagnose process conflicts.

Faceit or VGK service remnants may remain active even after uninstalling the app. Open Command Prompt as Administrator and run:

• sc query vgk
• sc query faceit
• sc query wdfilter

If any service is not in a STOPPED / not-found state, remove it manually or use the official Faceit uninstaller. Then reboot your PC.

Check that you are using the correct hotkey , in some builds the menu opens with F2, not Insert. Also make sure the game is running in borderless windowed mode, not fullscreen.

If crashes continue, disable HDR in your Windows display settings or in-game. HDR mode conflicts with the injector and causes a crash when the overlay opens.

The cause is Windows HDR being enabled. Disable HDR in display settings (Settings → System → Display → HDR) and restart the loader.

This is expected behavior related to the hardware spoofer. Follow these steps:

• Open Device Manager, find your network adapter, disable it, wait 10 seconds, then re-enable it.
• Use the spoofer only after a full PC reboot, not before.
• You do not need to reset HWID every time unless explicitly required.

Download and install the latest DirectX package from Microsoft's official site (DirectX End-User Runtime Web Installer), reboot, and try launching again.

Restart your computer. If the error persists, re-download the loader from the website and launch the fresh version , this resolves most connection issues after a cheat update.

Apply the win_driver_OFF.reg registry file (available from support), reboot your PC, then try launching again.

If the error persists, make sure antivirus software and Windows Core Isolation are disabled, then reapply the file and reboot.

This error most often occurs due to an unsupported Windows version. Check the product page for the maximum supported OS version and downgrade if necessary.

System freeze when entering the key is usually caused by HDR or antivirus conflicts. Do the following in order:

• Disable HDR in Windows display settings.
• Disable Windows Defender and make sure any third-party antivirus (e.g. Kaspersky) is fully uninstalled.
• Run the Sordum utility to disable system security drivers, then reboot your PC.

This is caused by the cheat driver conflicting with the network adapter. To fix it:

• Open Device Manager.
• Find your network adapter, disable it for 15,20 seconds.
• Re-enable the adapter , the connection will be restored.

Yes, a VPN is required to download and launch the loader. Enable VPN before starting , the loader will then load correctly.

The archive password is sordum. After extracting, run the file and click Search, then wait for it to finish.

The archive password for the spoofer is sordum. Extract the archive, run the program, and click Search , wait for the scan to complete.

If the program crashes or shows an error on launch, follow these steps in order:

• Restart your computer and try again.
• Disable Core Isolation (Memory Integrity) in Windows Security → Device Security.
• Open CMD as Administrator and run:
  sfc /scannow
  DISM /Online /Cleanup-Image /RestoreHealth
  Wait for completion, then reboot.

If none of the above helped, contact support for a remote assistance session.

The password for the cheat archive is sordum. Enter it when unpacking the archive.

If Windows Defender or your antivirus blocks the extraction, temporarily disable real-time protection before unpacking the files.

If the software fails to start, uninstall FaceIt Anti-Cheat and any other third-party anti-cheats from your PC , they conflict with the loader. Restart your system after removal and try again.

It is also recommended to clean your system of anti-cheat traces using the sordum utility (archive password: sordum): download it, run it, click Search, and wait for the scan to complete.

Use WinRAR to extract the archive. The archive password is: sordum.

• Download and install WinRAR if it is not already installed.
• Extract the archive using the password sordum.
• Run the program, click the Search button, and wait for it to finish.
• Take a screenshot of the result and send it to support if the issue persists.

The socks init/9 error indicates a network connectivity issue with the radar servers. Try enabling a VPN , this resolves the issue in some cases. If VPN does not help, contact support: the developer can reset the connection on the server side.

The cheat may be temporarily disabled due to a game update. During this period it is undergoing maintenance by the developer and cannot be launched.

Check the product page for the current status or contact support to find out when it will be available again.

Download and run the diagnostic utility from the archive (password: sordum), click Search, and send a screenshot of the result to support , this helps identify conflicting services or software.

OBS may conflict with certain cheat components , try launching the game without OBS to isolate the issue.

If the cheat crashes when pressing F2 in borderless mode, clean up leftover files from a previous installation:

• Download the Sordum utility (archive password: sordum), launch it and click Search.
• Once the scan finishes, delete the found leftovers, then reboot your PC.
• After rebooting, try launching the cheat again.

If the site redirects to the instruction page but the file does not appear, disable your browser's download blocker or pop-up blocker. If the issue persists, contact support , an operator will send you a direct download link.

After a successful injection, you need to activate the cheat inside the game. Enter a raid and press F2 , this opens the in-game console which activates ESP/chams display.

If nothing appears after pressing F2, press F7 and send a screenshot of the log (4 lines) to support. Note that settings are not saved between sessions , you must repeat this each time you launch.

The Ancient External menu only opens when the game is running in windowed mode. Go to Escape From Tarkov graphics settings, switch the display mode from fullscreen to windowed, then press Insert again.

To close the cheat menu, press Insert, Home, or End. If the physical keys do not respond (e.g. on a compact keyboard), open the Windows On-Screen Keyboard and press Home from there.

The noclip function (and god mode, flight) works only in PVE mode on a local server. These features are unavailable on official BSG servers , this is a game limitation, not a cheat issue.

The Discord stream bypass is built-in and works automatically. The key requirement is to select Game Capture mode when streaming , not Screen Capture. This way the cheat window will not be visible to viewers.

If ESP does not show players or loot, first check whether your version of Windows is supported. The current list of compatible OS versions is listed on the product page.

If your OS version is not on the list, the cheat may not function correctly. Contact support and specify your Windows version.

Yes, this is expected behavior. In thermal vision mode, scopes and glass surfaces render as black , this is how the thermal rendering works. No additional settings are required.

Yes, you need to relaunch the software each time you re-enter the game. This is expected behavior , simply close and reopen the loader before each new session.

The snow effect is only visible while the cheat menu is open. To remove it, simply close the menu by pressing Insert , the effect will disappear. There is no separate toggle to disable it.

The NoRecoil function was intentionally removed by the developer due to an increased risk of anti-cheat detection. This is not a bug , the change is permanent.

No Escape From Tarkov cheat can display items inside closed containers , this data is not available on the client until the container is opened. The radar shows the containers themselves, but not their contents.

Yes, this is normal behavior. When the spoofer seed changes, the system detects "new hardware" and sends a confirmation code to your email. This does not raise flags with the anti-cheat , you can continue as normal.

Important: always launch the game after activating the spoofer to avoid exposing your real hardware IDs.

Transferring activation to another computer is done manually by support. Contact support with your login and the details of the new PC , the operator will reassign the license.

Supported versions: Windows 10 (all builds) and Windows 11 (21H2, 22H2, 23H2).

Windows 11 25H2 and newer builds are not supported. If the cheat stopped working after a Windows update, roll back to a supported version.

This software does not support Windows 11 24H2 or 25H2. Only versions up to 23H2 are supported; 22H2 is recommended.

You need to reinstall Windows using a supported version. After installing 22H2 or 23H2, the cheat will run without issues.

Hyper-V must be fully disabled and the Windows PIN sign-in option must be removed (Settings → Accounts → Sign-in options).

If disabling Hyper-V through Windows Features doesn't work, run the following in an Administrator PowerShell session:

• takeown /F "C:\Windows\System32\hvix64.exe"
• icacls "C:\Windows\System32\hvix64.exe" /grant *<SID>:F
• Repeat for hvax64.exe, then delete both files with del.

Reboot and try the loader again.

Medusa RAGE works stably on Windows 10 22H2. Versions 23H2 and Windows 11 may cause instability, blue screens, and crashes during inject.

If you are running Windows 10 23H2 or Windows 11, it is recommended to roll back to Windows 10 22H2. Check the supported OS list on the product page.

This usually means your Windows version is not supported or was recently updated to an unsupported build. Check the list of supported Windows versions on the product page.

If the update happened recently, roll back Windows via Settings → Update & Security → Recovery → Go back.

This issue is most commonly caused by antivirus interference or network restrictions. First, fully remove all antivirus software (including hidden remnants , use the sordum utility). Then connect a VPN and restart the loader.

The Tarkov cheat and the Arena cheat are two separate products. One cheat does not work in both games simultaneously.

If you switch between Tarkov and Arena: the cheat should not activate automatically in Arena. When returning to Tarkov, you will need to relaunch the loader.

The cheat supports up to Windows 11 23H2. Version 25H2 is not supported. You need to downgrade Windows to 22H2 or 23H2 , the current maximum supported build is listed on the product page.

FaceIT Anti-Cheat is incompatible with this software. Completely uninstall FaceIT Anti-Cheat via Windows «Apps & Features», then reboot your PC and launch the loader again.

Before launching, make sure your Windows version is on the supported list. You can check your current OS version by running winver via Win+R. The up-to-date list of compatible Windows versions is listed on the product page.

This product supports only specific Windows builds. Build 25H2 is not supported , check the system requirements on the product page (press WIN+R and type winver to see your current version).

If your build is not on the compatibility list, the product cannot run on that system. Use a PC with a supported Windows version.