[Regression] Antigravity 2.28.0–2.28.2 fails to launch on Windows 11 26H2 (silent crash after 2s) – v2.27.0 works fine

App Version: 2.28.0 through 2.28.2 (Regression introduced in 2.28.0)

Working Version: 2.27.0

OS: Windows 11 (Insider Preview / Build 26H2)

Environment: Laptop (AMD Ryzen / Radeon dGPU)

Issue Description

Starting with version 2.28.0 (and persisting through 2.28.1 and 2.28.2), Antigravity fails to launch completely on Windows 11 26H2.

Upon double-clicking the executable or shortcut:

  1. Antigravity.exe briefly shows up in Task Manager for ~2 seconds.

  2. The process terminates immediately without rendering any UI window or throwing an explicit GUI error dialog.

  3. Downgrading back to v2.27.0 completely resolves the issue and launches reliably every time.

Troubleshooting Steps Already Attempted (Without Success)

Based on common Electron/GPU wrapper recommendations found in previous threads:

  1. Binary & Defender Integrity:

    • Verified that %LOCALAPPDATA%\Programs\Antigravity\resources\bin\language_server.exe is intact and has not been quarantined by Windows Defender.
  2. Clean State / Cache Reset:

    • Cleared %AppData%\Roaming frontend cache.

    • Renamed/reset %USERPROFILE%\.gemini\antigravity (backend state) to a .bak backup.

  3. GPU / DirectComposition Bypass Flags:

    • Attempted launching via PowerShell disabling hardware acceleration and sandbox mechanisms:

    PowerShell

    $env:ELECTRON_DISABLE_GPU="1"
    & "$env:LOCALAPPDATA\Programs\Antigravity\Antigravity.exe" --no-sandbox --disable-gpu --disable-gpu-sandbox --disable-direct-composition --disable-features=CalculateNativeWinOcclusion
    
    
    • Behavior remains identical: early silent exit within 2 seconds.

Questions / Request

  • Is there a known breaking change in the Electron base version, native node module bindings, or Windows API calls introduced in the 2.28.x branch that conflicts with Windows 26H2?

  • What is the recommended way to collect lower-level crash dumps (e.g. Minidumps/WER) for early startup crashes before Electron logging initializes?

Any insights from the team or community members on 26H2 would be appreciated.

Same issue here on Windows build 10.0.26300.9711 (26H2), Antigravity 2.28.2. Antigravity.exe appears in Task Manager for about 2 seconds, then exits with no window. Windows Error Reporting records exception 0x80000003 in Antigravity.exe. I tried a clean user-data directory, --disable-gpu/–no-sandbox flags, DISM /RestoreHealth, and sfc /scannow; no change. The 2.28.1 installer also fails with “Illegal System DLL Relocation.” Please confirm whether 2.27.0 is the safe rollback and whether a fixed build is planned. I can provide WER details if needed.

Version 2.27.0 works for me without any issues. I didn’t even need to uninstall version 2.28.x; I simply ran the 2.27.0 setup and installed it over the existing version.

yeah also i shifted to that version, i done check with an ChatGPT. this what issue was causing The problem was caused by several issues together:

  1. Your Windows 26H2 build has a compatibility problem with Antigravity 2.28.2’s Electron sandbox. Normal launch crashed silently with error 0x80000003.
  2. Antigravity runs helper processes inside a Windows AppContainer, but those processes lacked permission to access:
    • .gemini\config
    • .gemini\antigravity\bin
    • parts of the Antigravity installation
  3. The local https://127.0.0.1 interface was being blocked, so the Agent could not display its UI.
  4. Antigravity had auto-updated itself to the problematic 2.28.x version.

How I fixed it:

  • Granted only Antigravity’s specific Windows package identity the required permissions.
  • Created a separate working UI profile.
  • Added compatibility launch options:
--no-sandbox
--disable-gpu
--disable-features=NetworkServiceSandbox
  • Updated the Desktop and Start Menu shortcuts to use those options.
  • Saved the original shortcuts as .original backups.
  • Confirmed that the Agent opens and your existing conversations/projects are visible.

The Agent is still Electron; the workaround only disables some Electron/Chromium isolation features required by this Windows compatibility problem. Your data was not deleted.

Thanks a lot @Amarsingh_patil for pointing this out! The missing piece in my previous attempts was definitely --disable-features=NetworkServiceSandbox along with granting the AppContainer permissions.

For anyone else hitting this issue on Windows 11 (26H2), here is the consolidated PowerShell workflow to apply the permissions and launch Antigravity 2.28.x:

1. Grant AppContainer Permissions (Run PowerShell as Administrator)

The Electron helper processes need access to both the backend user state and the application binaries:

PowerShell

# Grant "ALL APPLICATION PACKAGES" (S-1-15-2-1) access to backend state and program files
icacls "$env:USERPROFILE\.gemini" /grant "*S-1-15-2-1:(OI)(CI)F" /T
icacls "$env:LOCALAPPDATA\Programs\Antigravity" /grant "*S-1-15-2-1:(OI)(CI)RX" /T

2. Launch with the Workaround Flags

Run this command (normal user PowerShell) to start the app bypassing the sandbox and network isolation block:

PowerShell

& "$env:LOCALAPPDATA\Programs\Antigravity\Antigravity.exe" `
  --no-sandbox `
  --disable-gpu `
  --disable-features=NetworkServiceSandbox

Can confirm this prevents the 2-second silent exit and the UI loads normally again.

Keep in mind that automatic updates or shortcut recreations might strip these launch arguments, so appending them to your desktop/start menu shortcuts or using a launcher script is recommended until the upstream Electron/AppContainer compatibility is resolved natively in an official release.