Description:
Hi team, I am unable to install the application on Windows using the default installation path. The setup fails during the file extraction process when it reaches a deeply nested node_modules directory related to @react-native.
The error message incorrectly suggests that Visual Studio Code is running, but I have verified via Task Manager that no VS Code processes are active. The issue seems to be that the 32-bit installer does not support or respect the Windows Long Paths feature.
Error Message:
codeText
There was an error while Opening file handle:
"C:\Users\Admin\AppData\Local\Programs\Antigravity\node_modules\@react-native\community-cli-plugin\node_modules\@react-native\debugger-frontend\dist\third-party\front_end\models\issues_manager\descriptions\arNavigationRegistrationWithoutTransientUserActivation.md":
Failed to create file handle: The system cannot find the path specified.
Please verify there are no Visual Studio Code processes still executing.
Steps to Reproduce:
-
Update using “Restart to Update“ button.
-
Keep the default destination path (C:\Users\[Username]\AppData\Local\Programs\Antigravity\).
-
The installation halts with the error mentioned above.
Troubleshooting Steps I’ve Already Taken:
-
Checked Task Manager: Verified that absolutely zero code.exe or Visual Studio Code processes were running in the background.
-
Enabled Windows Long Paths: I manually enabled LongPathsEnabled = 1 in the Registry (HKLM\SYSTEM\CurrentControlSet\Control\FileSystem), via PowerShell, and restarted my PC. The installer still throws the exact same error.
-
Run as Administrator: Attempted to run the setup as Admin, but the result is the same.
Environment:
-
OS: Windows 11
-
Antigravity Version: 1.19.6
VSCode OSS Version: 1.107.0 (user setup)
Commit: d2597a5c475647ed306b22de1e39853c7812d07d
Date: 2026-02-26T23:07:23.202Z
Electron: 39.2.3
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200
Language Server CL: 875890115
Additional Context:
Because the path length exceeds the standard 260-character limit of Windows, and the installer itself (being 32-bit or built with an older setup compiler) doesn’t seem to have long path awareness manifested, it fails.
