Fixing the Antigravity 2.0 Installer Directory Conflict

Google Antigravity
1

The Core Conflict

Upgrading to Antigravity 2.0 creates a file overlap because the new installer places its data inside the existing directory of version 1.107.0. Due to how Electron architecture works, the system gives execution priority to .asar archives over standard folders. Consequently, launching either executable always triggers version 2.0.

Quick Workaround: Swapping Versions

You can force the application to run the older version by temporarily hiding the new update file.

  1. Launch PowerShell on your Windows machine.

  2. Navigate to the asset folder using this command:

    powershell

    cd "$env:LOCALAPPDATA\Programs\Antigravity\resources"

    Use o código com cuidado.

  3. Change the extension of the main package to bypass version 2.0:

    powershell

    Rename-Item app.asar app.asar.bak

    Use o código com cuidado.

Outcome: The environment will automatically revert to the classic 1.107.0 setup. To restore version 2.0 in the future, simply reverse the process by removing the .bak extension.

Permanent Fix

This issue stems from the installer failing to isolate individual products. To resolve this permanently:

  1. Wipe all current Antigravity installations from your device.

  2. Run a clean installation for each version separately.

  3. Assign a unique, dedicated folder for each deployment.

  4. If installing via the command line, use the /DIR="your_chosen_path" argument to manually separate the directories.

1 Like