If you are a Windows user experiencing an issue where the Antigravity IDE fails to launch after installing Antigravity 2.0, you can resolve it with the following workaround:
PowerShell
cd "C:\Users\Pc\AppData\Local\Programs\Antigravity\resources"
Rename-Item app.asar app.asar.bak
The root cause is in how Google's 2.0 installer was packaged. Electron executables follow a documented resource loading priority: they always look for resources/app.asar first, then fall back to resources/app/. The 2.0 installer drops the new app.asar (containing 2.0 code) into the shared install directory alongside the IDE's existing app/ folder, without isolating it from the previous install. So even when you explicitly run Antigravity IDE.exe, the loader sees the newly added .asar first and loads 2.0 instead of the IDE. Renaming the .asar disables it, and the loader falls back to app/, which is the real IDE.
Caveat: while app.asar is renamed aside, Antigravity.exe (the 2.0 launcher) also falls back to resources/app/ and ends up launching the IDE. Only one of the two products can be active at a time. To use both, uninstall both and reinstall to separate directories.
