Where does the bug appear (feature/product)?
Grok Bot
Describe the Bug
Grok Bot 0.78.1 works correctly on my Windows 11 machine, but Grok Bot repeatedly forces an upgrade to 0.79.3, which introduces a regression that prevents me from using the application correctly.
I rolled back from 0.79.3 to 0.78.1 multiple times and reproduced the same behavior each time.
Automatic Updates is turned OFF in Grok Bot settings, but 0.78.1 still checks for, downloads, and stages the 0.79.3 Windows installer.
I observed the installer being downloaded to a randomly generated folder similar to:
Plain Text
%LOCALAPPDATA%\Temp\sand-update-XXXXXX
sand-update-0.79.3-1.exe
The 0.79.3 installer I observed was:
Plain Text
125,407,304 bytes
After the download, Grok Bot displays:
Plain Text
Update ready
Grok Bot 0.79.3
Restart to update
If allowed to continue, 0.79.3 replaces the working 0.78.1 installation.
For diagnostic purposes, I removed the staged sand-update-0.79.3-1.exe before exiting Grok Bot. Doing this successfully kept the installed version at 0.78.1.
However, after preventing the download/install, Grok Bot eventually becomes unusable and displays:
Plain Text
Update required
Couldn’t download the update.
Check your connection and try again.
with only:
Plain Text
Try again
Download the latest version
This makes it appear that 0.79.3 is being enforced as a mandatory/minimum client version, despite Automatic Updates being disabled.
Steps to Reproduce
Install Grok Bot 0.78.1 on Windows 11 x64.
Open Grok Bot.
Go to Grok Bot update settings.
Turn Automatic Updates OFF.
Use Grok Bot normally.
Wait several minutes.
Monitor:
Plain Text
%LOCALAPPDATA%\Temp
A randomly named folder appears:
Plain Text
sand-update-XXXXXX
Inside it, Grok Bot downloads:
Plain Text
sand-update-0.79.3-1.exe
Grok Bot then displays:
Plain Text
Update ready
Grok Bot 0.79.3
Restart to update
If Grok Bot is allowed to proceed normally, the installed application changes from 0.78.1 to 0.79.3.
Roll back to 0.78.1 and repeat. The same behavior occurs.
For diagnostic purposes, delete the staged sand-update-0.79.3-1.exe before application exit.
Confirm that Windows continues reporting Grok Bot 0.78.1.
Grok Bot eventually displays:
Plain Text
Update required
Couldn’t download the update.
Check your connection and try again.
Normal application use is blocked until the update succeeds.
I reproduced the download multiple times with different randomly generated sand-update-* folders.
Expected Behavior
When Automatic Updates is OFF, Grok Bot should not automatically download, stage, and effectively force installation of a newer desktop client.
If a newer version must be offered, I would expect to be able to postpone it temporarily, particularly if the current stable build introduces a blocking regression.
There should also be a supported method to temporarily pin or roll back to a known-working build such as 0.78.1 or 0.78.4.
If 0.79.3 is intentionally configured as a mandatory minimum client version, the UI should clearly communicate that and the documentation should explain the supported recovery path when that mandatory version has a regression.
Operating System
Windows 10/11
Version Information
Grok Bot for Windows x64
Known-working version: 0.78.1
Problematic/forced version: 0.79.3
Release track: Stable
Operating System: Windows 11 x64
Additional Information
I investigated this specifically to rule out an external Windows updater.
The unwanted update does not appear to originate from Windows Update, a Windows Scheduled Task, Startup application, or the legacy Squirrel updater.
The Grok Bot desktop client itself initiates the update.
During troubleshooting I observed the application creating randomly named folders under:
%LOCALAPPDATA%\Temp\sand-update-*
and downloading:
sand-update-0.79.3-1.exe
The downloaded executable observed during multiple reproductions was 125,407,304 bytes.
Removing the downloaded installer before Grok Bot exits prevents that particular staged update from replacing 0.78.1. However, this is not a viable workaround because Grok Bot subsequently presents a blocking “Update required” screen.
I am NOT requesting instructions to bypass update security, signature verification, or application integrity protections. I am looking for a supported rollback or version-pinning mechanism while the 0.79.3 regression is investigated.
Could the Grok Bot team please confirm:
- Is 0.79.3 currently configured as a mandatory/minimum Windows client version?
- What exactly does the “Automatic Updates” setting control?
- Why does the client still automatically download 0.79.3 when Automatic Updates is OFF?
- Is there a supported method to temporarily pin the Windows client to 0.78.1 or 0.78.4?
- Can affected users temporarily be exempted from the forced update?
- Is there a known Windows regression in 0.79.3?
- Is a replacement build planned, and if so, is there an ETA?
- What is the supported recovery procedure when the mandatory stable client introduces a blocking regression?
Does this stop you from using Cursor
No - Cursor works, but with this issue