Windows 0.78.1: main window hangs on startup (AppHangXProcB1, waiting on svchost:DNSResolver), persists with clean data

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

After extended multi-turn chats or switching between bots, the Grok Bot main window stops responding. From then on, every launch hangs and the main process never becomes responsive.

WER reports EventType AppHangXProcB1 with “Waiting on Application Name: svchost.exe:DNSResolver”.

Steps to Reproduce

  1. Use Grok Bot for an extended multi-turn conversation, or switch to another bot (for example, a Xiaohongshu bot).
  2. Observe that the main window becomes unresponsive.
  3. Close and relaunch Grok Bot.
  4. The main window hangs again on every launch.

A DNS ETW trace (Microsoft-Windows-DNS-Client) captured at startup shows 100+ A/AAAA queries per second for api2.cursor.sh / api3.cursor.sh. A queries complete with status 87 while AAAA queries return results. Other apps on the same machine resolve DNS normally.

Expected Behavior

Switching bots and relaunching should leave the main window responsive. Startup should not enter a persistent hang or generate a tight loop of DNS queries.

Operating System

Windows 10/11

Version Information

Grok Bot:
Version: 0.78.1
Release Track: stable
OS: Windows 11 Pro x64, build 26200.9711 (26H2)

For AI issues: which model did you use?

Not model-specific; reproduced while using different bots.

For AI issues: add Request ID with privacy disabled

Not applicable: the desktop UI hangs before a response/request ID is produced.

Additional Information

Already ruled out: VPN on/off, TUN off, system proxy off, WPAD off, full reboot, clearing Cache/Code Cache/GPUCache, and a completely fresh %APPDATA%\Grok Bot data directory. 0.78.1 is the latest release. Original app data was restored after testing. Grok Bot on this Windows machine is unusable; Mac/iOS remain usable. Happy to provide WER reports or a dump.

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey @Menglutina,

This matches an issue we’re tracking in the Windows app, including 0.78.1, where it can freeze when a chat loads images. Next time it hangs, try leaving it for about 10 minutes before closing it. The freeze can clear on its own, and the app should then stay responsive for the rest of that session.

It isn’t something you misconfigured, so there’s no need to keep resetting your data folder. I’ll post here when there’s an update.

Could you let me know if waiting helps, and whether Resolve-DnsName api2.cursor.sh -Type A in PowerShell returns IP addresses?