GameLoop stuck at 99% (or black screen) and won't launch — fix

HighGameLoop3 solutions

GameLoop freezing at 99% (or opening to a black screen) is almost never a broken install — it's usually a Windows virtualization conflict, the wrong graphics engine, or antivirus blocking the AOW engine. Work the three fixes below in order — free up virtualization from Hyper-V/WSL, switch the render engine to match your GPU, and whitelist GameLoop in your security software — re-testing after each. Reinstalling won't help and isn't needed.

GameLoop installs fine, but when you start it the loading bar freezes at 99% and never finishes — or it reaches 100%, the emulator window opens to a black screen, and the game never appears. Sometimes it sits there for minutes, sometimes it throws you back to the desktop. The installer worked, your internet is fine, and reinstalling changes nothing.

What's actually happening: GameLoop runs a real Android virtual machine through its AOW Engine. The 99% step is where it boots that VM and hands it to your GPU. It hangs there for one of a small number of reasons, almost always in this order of likelihood:

  1. A Windows virtualization feature is holding the hardware — Hyper-V, WSL2, Virtual Machine Platform, or Memory Integrity sit on the same CPU virtualization layer the AOW Engine needs, and Windows won't share it. This is the #1 cause on Windows 11.
  2. The graphics engine is set wrong for your GPU — GameLoop defaults to one renderer (DirectX or OpenGL / "Smart" or "Compatible"); if it doesn't match your card or driver, the VM boots but the screen never paints, so it looks frozen at 99% or black.
  3. Antivirus or firewall is blocking the AOW Engine — third-party security software often quarantines AndroidProcess.exe / the AOW Engine driver, so the VM can't fully start.
  4. Hardware virtualization (VT-x/SVM) is off in BIOS — less common as a pure "99% hang" (you usually get a warning instead), but worth ruling out.

This is a configuration conflict, not a corrupt game. Switching game versions or redownloading the game files won't help, because the emulator never finishes starting in the first place. Work the fixes below in order and re-test after each one.

Last updated 1 day ago0 users reported this issue1
Sign in to interact

Solutions

solution #1400

free-up-virtualization-from-windows (sortOrder=1, isMostHelpful)

Stop Windows (Hyper-V / WSL / Memory Integrity) from holding the virtualization layer. This clears the 99% hang for most people.

  1. Press Win, type Turn Windows features on or off, and open it. Uncheck Hyper-V, Virtual Machine Platform, Windows Subsystem for Linux, and Windows Hypervisor Platform if any are ticked. Click OK and reboot when asked.
  2. Core Isolation / Memory Integrity: open Windows Security → Device security → Core isolation details and turn Memory integrity Off, then reboot. (On Windows 11 this alone is often the whole fix.)
  3. If you still need Hyper-V for other software, instead of removing it you can disable it just for now: open an Admin Command Prompt and run bcdedit /set hypervisorlaunchtype off, then reboot. (Run bcdedit /set hypervisorlaunchtype auto + reboot to turn it back on later.)
  4. Reopen GameLoop and let the bar run to 100%.

Confirm the layer is free: open Task Manager (Ctrl+Shift+Esc) → PerformanceCPU and check Virtualization: Enabled. Stated honestly: Memory Integrity is a security feature; turning it off is standard practice for Android emulators, but on a work or shared PC confirm it's allowed and re-enable it when you're done. If Task Manager shows Virtualization Disabled, it's off in BIOS — see EmuDesk's VT-x / SVM virtualization guide first, then come back here.

solution #1401

switch-the-graphics-engine (sortOrder=2)

VM boots but the screen stays black or sticks at 99%? The renderer doesn't match your GPU. Switching it usually paints the screen instantly.

  1. Open GameLoop's Settings (the gear / hamburger menu, top-right) → Engine.
  2. Under Graphics rendering / Image rendering, switch between OpenGL+ (Smart), OpenGL, and DirectX (DirectX+) — try the one you're not currently on. Many NVIDIA/AMD desktops work best on DirectX+; some integrated-graphics laptops need OpenGL.
  3. Under Engine, also enable Virtualization (VT) if there's a toggle, and set a sane resource allocation — roughly half your CPU cores and half your RAM. Over-allocating can stall the VM at boot.
  4. Click Save — GameLoop will restart the engine. Relaunch the game.

If the bar now completes but the game itself is a black screen, update your GPU driver with a clean install — see EmuDesk's clean GPU-driver guide.

solution #1402

unblock-the-aow-engine-in-antivirus (sortOrder=3)

Still stuck after S1 and S2? Your security software is quarantining the engine.

  1. Open your antivirus (Windows Security, or third-party like Avast/AVG/Bitdefender/Kaspersky) and check the Quarantine / Protection history for anything from the GameLoop folder — typically AndroidProcess.exe, AndroidEmulatorEx.exe, or files under ...\TxGameAssistant\.
  2. Restore any quarantined GameLoop files and add the whole GameLoop install folder to your antivirus exclusions / allow list (default is C:\Program Files\TxGameAssistant).
  3. Do the same in Windows Firewall: allow GameLoop and its engine through (Settings → Privacy & security → Windows Security → Firewall & network protection → Allow an app through firewall).
  4. Right-click the GameLoop shortcut → Run as administrator and try again.

If GameLoop still hangs after freeing virtualization, switching engines, and clearing antivirus, do a clean reinstall: uninstall, delete any leftover TxGameAssistant folder, reboot, and install the latest build from the official site — a half-finished or mismatched-version install can corrupt the Android image so the VM never finishes booting.

Experiencing a different problem?Report a new issue to help the community find solutions.

Comments (0)

No other comments yet. Be the first to share your thoughts.

Sign in to_leave_comment

On This Page