Policy
System requirements
Last updated 13 November 2026. This policy applies to all products sold on this store, regardless of game or product version.
These tools load a kernel driver. They do not work while Windows virtualization security, Hyper-V or CPU virtualization is active. If you cannot meet every requirement below, do not purchase the tool.
Windows
- Windows 10 22H2 or Windows 11, 64-bit
- Intel or AMD x64 processor (ARM and Windows S Mode are not supported)
- An administrator account — the loader must elevate
- DirectX 11-capable GPU for the overlay
- Microsoft Edge WebView2 Runtime installed
- At least 500 MB free for the extracted tool payload
- Internet access for license activation and updates
Windows security settings
All of the following must be disabled before the loader can map its driver. Windows may re-enable some of them after a feature update.
- Open Windows Security → Device security → Core isolation details and set Memory integrity to Off.
- Open Turn Windows features on or off and uncheck Hyper-V, Virtual Machine Platform, Windows Hypervisor Platform, Windows Sandbox, Windows Subsystem for Linux, Containers and Application Guard.
- Run these in an elevated Command Prompt:
bcdedit /set hypervisorlaunchtype off bcdedit /set vsmlaunchtype off
- Reboot Windows, then verify in msinfo32 that Virtualization-based security is not enabled.
On managed or corporate devices, Group Policy or an MDM may force VBS/HVCI back on. Those devices are not supported.
BIOS / UEFI
Windows settings alone are not enough. The motherboard must also stop presenting a hypervisor to Windows.
- Intel Virtualization Technology (VT-x), AMD-V or SVM: Disabled
- Hypervisor / virtual machine extensions: Disabled
- Secure Boot: disable only if the loader reports the kernel driver cannot be mapped
- No BIOS/UEFI password or management lock that prevents changing these settings
The exact names vary by vendor: Intel Virtualization Technology, VT-x, AMD-V, SVM Mode or Secure Virtual Machine. Disable it, save the BIOS settings and boot Windows again.
The launcher can apply the Windows registry, BCD and optional-feature changes automatically when run as administrator. BIOS changes are always manual.
Verification checklist
msinfo32shows Virtualization-based security as not enabled.systeminfodoes not report “A hypervisor has been detected”.- Task Manager → Performance → CPU shows Virtualization: Disabled.
- The loader reaches “driver ready” and the overlay opens without a VBS or driver-mapping error.
Antivirus and network
Some antivirus products quarantine the loader or driver. If that happens, add the tool folder to your antivirus exclusions and restore the quarantined files. A managed antivirus policy that prevents this is not supported.
A stable internet connection is required for sign-in, license activation and release downloads. Game-specific requirements are separate and are listed on each product page.
Policy
These requirements are a condition of use for every product. Support cannot make a tool work on a machine that blocks kernel drivers through VBS, HVCI, Hyper-V, CPU virtualization or an enforced device policy. If your machine cannot be configured this way, do not buy the tool.
Disabling these security features lowers the machine's protection. You are responsible for the configuration and for any effect it has on other software, including Hyper-V, WSL2, Docker, Windows Sandbox and Android emulators.