GameLoop on Windows 11 — the three conflicts and how to fix each one
GameLoop runs on Windows 11, but three Win11-specific features block it by default. They look identical from the outside — the launcher silently crashes or the emulator never starts — and each one has a different fix.
GameLoop ran on Windows 10 the way it was designed to. Windows 11 ships with three new defaults that did not exist then, and all three conflict with GameLoop's core mechanism: a kernel-level Android virtualization layer that needs exclusive access to the CPU's hardware virtualisation extensions.
None of these conflicts give you a useful error message. The launcher may disappear without a word, produce an "environment check failed" message, or display a vague "GameLoop cannot start" screen. The three causes look the same from the outside, so the right starting point is finding out which one you have before changing anything.
Finding out which conflict you have
Open Task Manager (Ctrl + Shift + Esc), go to the Performance tab, click CPU, and read the bottom of the panel. You will see:
- Virtualization: Enabled or Disabled
- Whether Hyper-V appears in the CPU title
If virtualization shows Disabled, start with the BIOS (see the VT-x/AMD-V guide) — this is the same step on Windows 11 as on Windows 10.
If virtualization shows Enabled and GameLoop still will not launch, the problem is one of the three Windows 11-specific conflicts below.
Conflict 1 — Memory Integrity (Core Isolation / HVCI)
Windows 11 enables Memory Integrity by default on new installs on supported hardware. It is part of the Core Isolation feature, formally called Hypervisor-Protected Code Integrity (HVCI). It prevents any kernel-mode driver that is not signed by Microsoft or a trusted vendor from loading.
GameLoop's Android virtualization layer installs components at the kernel level. On machines where Memory Integrity has been on since initial setup, those components cannot load, and GameLoop silently fails to start.
How to turn it off:
- Open Settings → Privacy & Security → Windows Security.
- Click Device Security.
- Click Core isolation details.
- Toggle Memory integrity off.
- Restart the PC.
After the restart, try launching GameLoop. Most silent launch failures on new Windows 11 installs clear with this step alone.
Conflict 2 — Hyper-V running in the background
GameLoop requires exclusive access to the CPU's virtualisation extensions (VT-x on Intel, AMD-V on AMD). Hyper-V, Microsoft's own virtual machine platform, takes those extensions and partitions them — which means GameLoop can no longer reach them directly.
On Windows 11, Hyper-V is more commonly running than it was on Windows 10, because several applications enable it silently:
- Docker Desktop (the Windows container backend requires Hyper-V on most configurations)
- Windows Subsystem for Linux 2 (WSL2 uses a lightweight Hyper-V VM)
- Android emulators from other vendors that run in Hyper-V mode (Visual Studio device emulators, certain gaming emulators)
If any of these applications are installed and running, Hyper-V is active.
How to check: Open an elevated Command Prompt (Run as administrator) and run:
`` bcdedit | findstr hypervisor ``
If the output shows hypervisorlaunchtype Auto, Hyper-V is enabled.
How to disable Hyper-V:
In the same elevated Command Prompt:
`` bcdedit /set hypervisorlaunchtype off ``
Restart the PC. Run the check again to confirm the output now shows hypervisorlaunchtype Off.
What this does to Docker and WSL2: Docker Desktop on Windows will switch to its WSL2 backend automatically if Hyper-V is off. WSL2 itself uses a different kernel path when Hyper-V is unavailable and still works for most purposes. Test your other applications after the change. If something breaks, re-enable with bcdedit /set hypervisorlaunchtype auto and restart.
Conflict 3 — Windows Subsystem for Android
Windows 11 shipped with Windows Subsystem for Android (WSA), a built-in Android runtime powered by the Amazon Appstore. Microsoft discontinued WSA in March 2024 and removed it from new installs, but machines that installed it before that date may still have it active.
WSA runs on Hyper-V. If WSA is installed and active, the same conflict described in Conflict 2 applies, with one additional layer: WSA holds a persistent Hyper-V partition even when no Android apps are actively running.
How to check: Open Settings → Apps → Installed apps, search for Windows Subsystem for Android.
How to remove it: Click the three-dot menu next to the entry and select Uninstall. Restart.
After uninstalling WSA, the Hyper-V dependency it introduced may still require disabling Hyper-V separately (see Conflict 2) if Docker or WSL2 also keeps it active.
What does not change on Windows 11
A few things GameLoop guides often flag as Windows 11 issues that are not:
| Thing said to be different | Actual status |
|---|---|
| Secure Boot must be off | Secure Boot does not block GameLoop. Leave it on. |
| TPM 2.0 interferes | TPM is a Windows 11 prerequisite and unrelated to emulator virtualisation. |
| DirectX version is different | Win11 and Win10 share the same DirectX support. GameLoop's renderer menu — DirectX+, OpenGL+, DirectX, OpenGL, Auto — is identical on both. |
| Administrator rights work differently | They do not — the same "Run as administrator" fix applies on both. |
The VT-x/AMD-V check in the BIOS is also identical on Windows 11 — the setting path differs between motherboard vendors, not between Windows versions. If your BIOS has virtualisation, it exposes it the same way regardless of which Windows is installed.
TAC on Windows 11
TAC (Tencent Android Connect), the newer Tencent emulator client that runs alongside GameLoop, uses Intel Bridge Technology — a different execution model that translates Android ARM instructions to x86 using a software layer rather than a hardware-virtualised Android kernel. This architecture has different interactions with Windows 11's security features.
In practice, users who cannot get GameLoop working on Windows 11 — particularly on laptops with aggressive HVCI or strict Secure Boot enforcement — sometimes report that TAC launches without the conflicts described above. TAC's tradeoff is that its game library is smaller than GameLoop's and its compatibility with older CODM builds is lower.
If you have tried all three fixes and GameLoop still will not start, TAC is worth testing as an alternative. The TAC explained article covers the difference in detail.
Order to try the fixes
If you are not sure which conflict you have:
- Check Memory Integrity first. It is the most common cause on new Windows 11 installs and takes one restart to test.
- If Memory Integrity was already off, check Hyper-V. Run the
bcdeditcheck and disable if active. - If Hyper-V was off or not applicable, check for WSA. Uninstall it, restart, and test.
- If all three are already clear and GameLoop still fails, the cause is on the GameLoop side — see GameLoop won't open for the full diagnostic tree including driver and installer faults that apply on all Windows versions.