Fix spawn git ENOENT in Universal Modder Installation

The error spawn git ENOENT means the process could not start Git, or its requested working directory was unavailable. Check both in the environment that ran the extension installation before retrying. A general clone failure can instead be a network or permission problem.

Checks

In the same Windows PowerShell terminal where installation failed:

powershell

Select code

Get-Command git -All
git --version
Get-Location
Test-Path -LiteralPath (Get-Location).Path

You can select the code to copy it manually.

On Bash or Zsh, use command -v git and git --version, and confirm that your current project directory still exists and is accessible. Git installed on Windows is not automatically available inside WSL.

If Git is missing, use Git for Windows or the Git installation page for your environment, then open a new terminal. If only an older terminal or agent cannot see it, restart those processes. Do not replace the whole PATH or delete the extension cache as a first step.

If the working directory was removed or became unavailable, move to an existing local folder you own. Recheck the directory and Git there. A visible Git version does not repair a missing directory.

Launcher restrictions

If the error is specifically that PowerShell cannot run gemini.ps1, inspect Get-Command gemini.cmd. Use that installed launcher with the same arguments if it exists. For npm.ps1, the corresponding installed npm.cmd can serve the same purpose. This changes the launcher; it does not fix a missing Git executable. Do not use Set-ExecutionPolicy Unrestricted for this diagnosis.

Verify

Repeat git --version and the directory check in the original target environment. Then return to Gemini extension installation and retry the documented install command. Check the extension and skill lists in a fresh session; configure optional fal access only if you want to use that service.

If Git and the directory pass but the installation still fails, preserve the command, time, environment and actual error. Inspect which Gemini launcher is running and whether its process inherits the same environment. A new authentication, network or permission error needs its own check; do not label it solved solely because Git is visible.

If the next error names a missing gemini-extension.json, use the plugin discovery and manifest checks. For a different failure stage, return to Universal Modder troubleshooting with the new message.

Continue

Return to Gemini install skill, or review environment requirements. After extension discovery succeeds, use the um CLI reference to check the separate command-line tools; optional asset authentication is another check.

Older environments

The installation failure tracked in issue #109 occurred on Windows 10 with gemini.cmd; its Gemini CLI, Node and Git versions are unknown, so do not assume your versions match that case.

For a Windows 10 installation, record the actual Node, Git and Gemini versions before applying current instructions. Compare the installed agent’s current requirements with your operating system, since older setups can fall outside them.

Keep your actual error locally. Remove credentials and personal paths before sharing it with a support channel you choose.

After installation succeeds, use the Universal Modder tutorial to plan and check a small first mod.