Title:
Antigravity 2.0 stops launching after reboot on Windows — workaround using Electron flags
Post:
I ran into a persistent issue with Antigravity 2.0 on Windows.
The app worked right after installation. I was able to launch it and use it normally at first. However, after rebooting Windows, Antigravity would no longer launch properly.
What happened:
- Right after a fresh install, Antigravity worked.
- After rebooting the computer, it stopped launching properly.
- Reinstalling or clearing AppData/cache could make it work temporarily again.
- But after another reboot, the same problem came back.
- Some launch attempts did not open the app properly at all.
- Some workaround commands made the window appear, but it only showed a blank/white screen.
- The language_server process could start.
- The local backend port could be active.
- But the UI still failed to render.
The logs showed GPU/Electron/Chromium-related errors, including messages similar to:
GPU process exited unexpectedly
GPU process isn’t usable. Goodbye.
In my case, simply disabling GPU was not enough. It still resulted in a blank/white window. What finally worked was launching Antigravity with both GPU-related flags and the Chromium/Electron sandbox disabled.
I created a batch file with this content:
@echo off
set ELECTRON_DISABLE_GPU=1
taskkill /f /im Antigravity.exe 2>nul
taskkill /f /im language_server.exe 2>nul
start “” “%LOCALAPPDATA%\Programs\Antigravity\Antigravity.exe” --no-sandbox --disable-gpu --disable-gpu-sandbox --disable-direct-composition
Important:
The path in the start command may be different on your system. Please check where Antigravity.exe is installed on your machine and adjust the path accordingly. You can usually find it by right-clicking the Antigravity shortcut, opening Properties, and checking the Target field.
After creating this batch file, I launched Antigravity from the batch file instead of the default Start Menu shortcut.
This suggests the issue may be related to Electron/Chromium renderer initialization after reboot, GPU acceleration, GPU sandboxing, DirectComposition, or how Antigravity restores its runtime state on Windows.
Security note:
This is only a workaround, not a proper fix. Using --no-sandbox weakens Chromium/Electron sandbox protection, so it should be used carefully. A proper fix should ideally come from Antigravity by providing an official safe-mode launch option or handling GPU/rendering fallback more reliably.
For now, this workaround made the app usable again after reboot.