---
title: "GameLoop stuck at 99% (or black screen) and won't launch — fix"
canonical_url: https://emudesk.com/issues/gameloop-stuck-at-99-percent-wont-launch-fix
content_locale: en
source_locale: en
entity_type: issue
index_status: index
published_at: 2026-08-31T18:22:23.000Z
updated_at: 2026-09-01T00:45:02.680Z
freshness_status: fresh
---

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

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:


  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.
  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.
  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.
  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.