Grok Bot is completely stuck in a “Reset failed” loop and cannot connect to the backend computer on Windows.
CRUCIAL CONTEXT: This issue is strictly isolated to the Windows application. I have a dual-boot setup on this exact same machine, and Grok Bot works perfectly fine on my Ubuntu partition. It also works flawlessly on my mobile phone. This confirms my hardware, local network, and router are working correctly, and the issue is either a Windows-specific bug or a corrupted VM state tied specifically to my Windows session.
Retrying does not work at all. Troubleshooting steps already taken to isolate the issue on Windows:
Reinstalled Grok bot
Completely disabled Kaspersky antivirus and its network/SSL traffic inspection.
Manually deleted the local .grokbot data folder to force a clean environment.
Flushed DNS and verified that nslookup test.us8.cursorvm.com successfully resolves the IPs.
Tested on a completely different external network (mobile phone hotspot).
Steps to Reproduce
Open the Grok Bot desktop application on Windows.
Attempt to connect to the bot environment.
Click on “Recover computer” or “Retry Reset” when prompted.
Observe the permanent “Reset failed… partial state” error loop.
Important Network/IPv6 Context I discovered:
When IPv6 is ENABLED on my Windows network adapter: The app gets completely stuck on the initial startup logo screen with the message “Grok Bot is having trouble connecting” (see attached image). It doesn’t even load the main UI.
When IPv6 is DISABLED (and using custom IPv4 DNS like 1.1.1.1): The app bypasses the splash screen and loads the main UI, but gets stuck at “Can’t reach your computer” on the left sidebar (see attached image). From here, clicking “Recover computer” triggers the unsolvable “Reset failed” pop-up.
Hey, thanks for the detailed report and especially for testing on Ubuntu and your phone. That comparison is the key clue. I see both screenshots, the splash screen saying “having trouble connecting” and the main UI saying “Can’t reach your computer”.
On our side, the Grok Bot computer has been up and running the whole time. Your phone and Ubuntu on the same hardware can reach it fine, but the Windows app stopped sending requests to us. “Reset failed” here means the request never left your PC, so it’s best not to click Recover or Reset right now. Your Bots are safe.
Everything points to something on Windows intercepting HTTPS. Grok Bot uses its own certificate store, so any product that re-signs encrypted traffic, like Kaspersky’s “Encrypted connections scanning”, breaks it. Cursor, browsers, and curl keep working because they trust the Windows system certificate store. This also explains why Ubuntu on the same hardware and network is fine. One important detail is that fully disabling the antivirus often still leaves the scanning driver active, so just “turning off Kaspersky” might not help.
Can you check this and tell me what you see?
In Edge or Chrome on Windows, open https://api2.cursor.sh. A blank page or an error is OK.
Click the lock icon in the address bar, then Connection is secure, then the certificate icon.
Check the Issued by field. It should be Amazon RSA 2048 M01. If it says Kaspersky or anything else, that’s the interception.
If yes, open Kaspersky, Settings, Security settings, Network settings, Encrypted connections scanning, and choose Do not scan encrypted connections. Another option is to add Grok Bot under Threats and Exclusions as a trusted application with Do not scan encrypted traffic.
Fully quit Grok Bot, right click the tray icon, Quit, then confirm in Task Manager there are no Grok Bot processes left. Start it again and give it a couple minutes.
If the issuer already shows Amazon and the problem still happens, please attach this file: %APPDATA%\Grok Bot\desktop-structured-log-spill.v1.json. Paste %APPDATA% into the Explorer address bar. It contains the app’s own connection errors from the last about 18 hours, which we can’t see from our side.
About IPv6, our servers only publish IPv4 addresses, so IPv6 can’t be the cause by itself. The difference between the splash screen and the sidebar depends on whether the app had a saved list of Bots to display, not on the network.
Thank you so much for the detailed explanation. I checked the certificate for api2.cursor.sh in my browser, and indeed, the issuer was showing up as Kaspersky Anti-Virus Personal Root Certificate instead of Amazon.
I went into the Kaspersky settings, disabled the encrypted connections scanning just as you suggested, made sure to fully quit Grok Bot from the system tray, and started it again. It is now working perfectly. I really appreciate you taking the time to explain the why behind this.
