BBugs

GameLoop won't open — Task Manager tells you which of three faults you have

GameLoop not opening is three separate failures wearing the same silence. Which one you have is visible in Task Manager before you change a single setting.

When GameLoop does nothing on double-click, the first useful move is not a fix. It is Task Manager, because three visibly different faults hide behind the same silence.

Press Ctrl + Shift + Esc, open the Processes tab, and launch GameLoop while you watch:

  • A GameLoop process appears and vanishes within seconds. The launcher runs; the engine dies. Driver and runtime territory.
  • Nothing appears at all. The launcher never got off the ground. Permissions, antivirus, or a damaged install.
  • A GameLoop process is already listed. A previous session never exited and is holding the lock.

Process names differ between builds — GameLoop.exe, MobileGamePC.exe, tgame.exe, GameDownload.exe and AndroidPlayer.exe all turn up. So do install paths: Program Files\GameLoop, Program Files\Tencent\GameLoop and Program Files\TxGameAssistant are all in current circulation. Read the target of your own shortcut rather than trusting any path written down elsewhere, this article included.

Why it breaks at all

GameLoop is not an ordinary desktop application. It boots an Android system inside a hypervisor, installs kernel-level components, and writes into protected directories. All three are things Windows, antivirus engines and competing hypervisors are entitled to refuse — and all three tend to refuse quietly, with no dialog box.

That is the whole reason this fault looks mysterious. There is usually no error text to search for.

What actually fixes it, in order

1. Kill leftover processes. End every GameLoop-named task, wait a few seconds, relaunch. Free, and it is the entire fix whenever the emulator was force-closed last time.

2. Run as administrator. Right-click the shortcut, Run as administrator. If it opens, make it permanent under Properties, Compatibility, "Run this program as an administrator". This is not a workaround — the app writes where a standard user account cannot.

3. Update the graphics driver. Take it from the GPU vendor's own site rather than Windows Update, which tends to ship older builds, then reboot. This is the standard answer to the "appears, then disappears" pattern and to crashes on the splash screen.

4. Sort out virtualisation — in both directions. Task Manager, Performance, CPU shows a Virtualization line. If it reads Disabled, Intel VT-x or AMD SVM is off in firmware. The opposite problem is now more common on Windows 11: Hyper-V, Windows Hypervisor Platform, WSL2, Docker or memory integrity claim the hardware virtualisation extensions, and a third-party hypervisor gets what is left. Turn Hyper-V off in Windows Features (optionalfeatures) and reboot to test.

5. Exclude GameLoop from antivirus. Kernel drivers plus an emulator are a combination heuristics dislike. Exclude the install folder and the GameLoop folder under AppData. Excluding is the fix; leaving real-time protection off is not.

6. Install the Microsoft runtimes. Visual C++ Redistributables, both x86 and x64, and .NET Framework 3.5 via optionalfeatures. Relevant mainly on fresh Windows installs.

7. Clean reinstall, last. Uninstall, then delete leftover GameLoop, Tencent and TxGameAssistant folders under Program Files, %appdata% and %localappdata% before reinstalling — from the vendor's own site only. Modified or "premium unlocked" emulator builds are a well-known carrier for account-stealing malware, and this is software that runs with high privilege.

What does not fix it

Popular adviceWhy it is misplaced
Compatibility mode for Windows 10Aimed at legacy Win32 apps. It does nothing about drivers, hypervisor conflicts or file permissions, which is where this fault lives.
Deleting GameLoop keys in regeditRarely the cause, and one slip in the wrong hive breaks Windows. Reserve it for a reinstall that has already failed once.
Matching a "minimum requirements" tableTencent publishes no system requirements. The tables in circulation are third-party guesses that contradict each other.
Reinstalling DirectXWrong layer entirely if the launcher never starts.
Turning off antivirus permanentlyTrades a launch problem for a security problem. Exclusions do the same job.

If GameLoop opens but shows nothing but black, that is a rendering fault rather than a launch fault, and it has its own set of causes.