Where GameLoop's update bar stops tells you which fix applies
A stall at 0% and a stall at 99% are different failures with different fixes. The percentage is the most useful diagnostic GameLoop's updater gives you, because it gives you nothing else.
GameLoop's updater reports almost nothing when it fails. There is no error code worth searching, no log a normal user can read, and no status page to check against. What it does give you is a number, and the number is genuinely diagnostic.
| Where it stalls | What that points at |
|---|---|
| 0%, indefinitely | The download never really started — name resolution, CDN routing, or a blocked process |
| Somewhere in the middle | An interrupted transfer, and corrupted staging files blocking the retry |
| 99%, or "Update Failed" right at the end | Validation and write — permissions or antivirus on the final file swap |
| Downloading, but very slowly | Network path to Tencent's CDN, which is the hardest case to prove |
Why it fails
Five things go wrong, and they map onto those rows. Network and DNS problems stop the download from starting. A previous interrupted attempt leaves partial files that the next attempt refuses to reconcile. Antivirus blocks an updater that is downloading and replacing executables, which is behaviour worth flagging in the abstract. Windows blocks a write into the install directory. And server-side load, which is real during a major game season launch and completely unfalsifiable from your side of the connection.
Fixes, in the order worth trying them
Close it properly and retry. Not the window X — end every GameLoop, TxGameAssistant and MobileGamePC process in Task Manager, then start again. If the far end was busy, that is the whole fix, and it costs nothing to rule out first.
Run as administrator. The updater must write into its own install directory. If you have seen 0x80070005, this is not a guess: that code is Windows' generic access-denied result, and elevation is the direct answer to it.
Exclude, do not disable, your antivirus. Add the GameLoop install folder to the exclusion list and allow its executables through the firewall for both private and public networks. Switching real-time protection off for the length of a download is the advice you will read everywhere; it works, and it also means you are pulling and executing a large binary with no protection running.
Clear the staging files. With GameLoop fully closed, empty the Download, Cache or Temp subfolders in the install directory. This is the specific fix for a bar that stops partway and stops in the same place on every retry.
Flush DNS, then change it. From an elevated command prompt, ipconfig /flushdns costs one line and occasionally solves a 0% stall outright. If it helps but does not finish the job, pointing the adapter at a public resolver such as Cloudflare or Google is the next step.
Install the current build over the top. Take the full installer from the vendor's own site and run it against the existing installation. This is the strongest fix on the list and the most under-used, because it replaces the update mechanism itself rather than asking a broken updater to repair itself. Vendor site only — modified emulator builds are a known malware carrier, and this one runs with high privilege.
Clean reinstall, last. Uninstall, delete leftover TxGameAssistant folders under Program Files, %localappdata% and %appdata%, reboot, install fresh.
What does not fix it
A VPN, as a default move. It is a legitimate test if your ISP demonstrably throttles the route and you have measured the difference. As blanket advice it adds a variable, frequently makes throughput worse, and points readers at whichever provider pays the most affiliate commission. Measure first.
Deleting everything in %temp%. Broad, indiscriminate, and it removes files other applications are mid-way through using. Clear GameLoop's own staging folders instead.
Deleting registry keys. Reserve it for a reinstall that has already failed once for the same reason. It is not a first-line fix, and the downside of a mistake is not proportionate to the upside.
Waiting for off-peak hours. Sound prevention, useless as a cure. If the download is stalled at 45% on corrupted staging files, it will still be stalled at 45% at four in the morning.