Windows download
Download and install Grok Bot on Windows
One official installer, one installed copy. Pick x64 or Arm64 from x.ai/bot. If Windows already lists Grok Bot twice, remove the older one before you debug the network.
Pick x64 or Arm64 on purpose
Open Settings, then System, then About, and read System type. That line is the whole architecture choice. x64 is the usual 64-bit Intel or AMD PC. Arm64 is a Windows on Arm machine. The product page offers both. The FAQ lists Windows on x64 and Arm64, so a failed launch is not evidence that Windows is unsupported.
Download only from x.ai/bot. A search result that wraps the installer in another site is how people end up with a build the app later rejects. Run the installer, then open Grok Bot from the Start menu. Sign in with Cursor in the browser popup. There is still no Grok Bot account to register on the desktop.
Two copies is a stuck app
Settings, then Apps, then Installed apps. If Grok Bot appears twice, uninstall the older copy and keep the latest. Close the window after that is not enough. Quit from the system tray so the leftover process dies, then open the remaining copy once. People hit Can't reach your computer on a fresh Windows profile when an older install was still registered beside the new one. Fix the duplicate before you change DNS, and before you Reset a computer that may not be the problem.
The same tray quit matters later. Staff tell Windows users who still have a local-exec daemon to quit from the tray, end Grok Bot and the daemon in Task Manager, wait about a minute, and re-register. That is a local-execution cleanup, not a reinstall of the cloud computer. Do not confuse it with Recover.
Proxy, TUN, and company tunnels
If the installer finished and the app stops at Can't reach your computer, the download is probably fine. Staff have said the computer on their side was up the whole time, and recreating it does not help, because the Windows app connects directly. It does not use the system proxy or a local HTTP proxy such as 127.0.0.1:7890. DNS and browser checks that go through the proxy can pass while the app still fails.
Staff test, in PowerShell, after you fully quit Grok Bot and switch the tunnel from system-proxy mode to TUN (also called Enhanced, Global, or virtual network adapter):
curl.exe --noproxy "*" -I https://test123.us10.cursorvm.comA working path returns quickly with HTTP/1.1 404 Not Found and Server: awselb/2.0. The 404 is success: that hostname is only a probe, and the load balancer answered. A hang, timeout, or connection reset means the app will fail the same way. Fix TUN, then open Grok Bot. Do not install that tunnel inside the Agent Computer.
Do the opposite inside the product. Never install a VPN, proxy, or DNS changer on the Agent Computer. A bot-installed VPN can cut the always-on path so every bot on the account fails until Recover restores routing. A company Zscaler-style tunnel has also left Windows 11 on a black loading screen. A phone hotspot on another carrier is the clean A/B test: if the hotspot works and the office network does not, the installer is fine and the path is not. The can't-reach page has the DNS and antivirus order. Antivirus products that scan HTTPS replace the certificate issuer, and Grok Bot trusts public authorities only, so the browser can load while the app cannot.
What a finished install looks like
You should get a Cursor browser popup, then a roster starting in the background, then Meet a future teammate. Tool questions on that path do not connect Gmail, GitHub, or anything else. If the popup never completes, use the login page. If the screen says Connecting and never leaves, save Privacy Mode on the Cursor dashboard before another reinstall. If it says Setting up and you are on a free Cursor plan, the hosted computer was never created. Downloading the exe again will not provision a seat.
The app checks for updates on its own. Settings → Updates → Check for Updates, then Restart to Update, replaces the desktop app. It does not reset the computer. The computer update is the other control in that same screen, Update under Grok Bot's Computer. You do not need a forum installer to get the current build. A white window that survives reinstall can be local config: fully quit, and rename %APPDATA%\Grok Bot to Grok Bot.bak, the Windows twin of the Mac Application Support folder. Linux packages are under More downloads on the same product page.
After Windows is open
Use one bot and one cited job. The first-bot lesson is the short brief. If bots later go silent while the computer view still opens, that is weekly usage more often than a broken Windows install. Uninstalling Windows will not refill the meter. Pricing explains which plans include access, without invented dollar amounts.
FAQ
Where is the Grok Bot Windows download?
On x.ai/bot. Choose x64 or Arm64 to match Settings, System, About, System type. Do not use a repackaged installer from somewhere else.
What if Installed apps shows Grok Bot twice?
Uninstall the older copy and keep the latest. Then quit Grok Bot from the system tray, not only by closing the window, and open it once.
The Windows app ignores my proxy. What do staff say to try?
Staff reports say the app does not follow the system HTTP proxy. People who needed a tunnel used TUN mode, which captures traffic at the adapter. Do not install a VPN inside the Agent Computer.
Windows setup ends on Can't reach your computer. Is that a bad install?
Often it is DNS, a VPN, antivirus HTTPS scanning, or an expired plan that the app mislabels. Follow the can't-reach walkthrough before you Reset.
Related
- Grok Bot guide — Start here if the app is not installed yet.
- Install overview — Official packages for every platform, then Cursor login.
- Mac download — Apple silicon versus Intel, Gatekeeper, and the white window.
- Can't reach your computer — DNS, hotspot, antivirus scanning, and when not to Reset.
- Linux packages — Official deb, rpm, and AppImage versus community ports.
Sources
- Get started
- x.ai/bot
- Windows fresh profile, can't reach
- Zscaler and a black screen
- Official troubleshooting