Antigravity 1.15.8 Browser Crash on Windows

Google Antigravity
1

:hammer_and_wrench: Fix: Antigravity 1.15.8 Browser Crash on Windows

If your Antigravity browser (or other Playwright-based tools) crashes instantly upon launch in Windows, it’s likely because the system fails to locate a “Home” directory for storing temporary browser data. This guide helps you fix it permanently.

:police_car_light: The Issue

Modern browser engines (like Playwright) require a HOME environment variable to look for configuration files and store cache. On some Windows systems, this variable isn’t set by default, causing the browser process to terminate immediately.

:white_check_mark: The Solution

Create a permanent user-level environment variable named HOME that points to your Windows user profile folder.

:memo: Step-by-Step Instructions

1. Open PowerShell as Administrator

  • Press Win key.

  • Type PowerShell.

  • Right-click “Windows PowerShell” and select “Run as administrator”.

2. Run the Fix Command Copy and paste the following code into PowerShell. It automatically detects your current username and sets the variable correctly.

[Environment]::SetEnvironmentVariable(“HOME”, “C:\Users\$($env:USERNAME)”, “User”)

Note: Using $env:USERNAME ensures it picks the correct folder for the currently logged-in user.

3. Verify the Fix Run this command to check if it was saved successfully:

[Environment]::GetEnvironmentVariable(“HOME”, “User”)

You should see an output like C:\Users\YourName.

4. Restart Antigravity

  • Close Antigravity completely.

  • Restart the application.

  • The browser features should now launch without issues!

2

Hello @Om_Choudhary, welcome to AI Forum!
Thank you so much for documenting this manual repair report! It is incredibly helpful to see the specific root cause and the steps you took to resolve the browser crash in version 1.15.8.

Your contribution will definitely help other users facing the same issue while we look into a more permanent fix for the installer. We appreciate you taking the time to share this workaround with the community!

1 Like