Skip to content

docs: fix WSL without GfW paths #2461

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mjcheetham merged 1 commit into from
Oct 1, 2026
Merged

docs: fix WSL without GfW paths #2461

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 15 additions & 9 deletions docs/wsl.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,21 +73,27 @@ _Inside your WSL installation_, run the following command to set GCM as the Git
credential helper:

```shell
# For x64 or ARM64 installations of Git Credential Manager
git config --global credential.helper "/mnt/c/Program\ Files/Git\ Credential\ Manager/git-credential-manager.exe"

# For x86 installations of Git Credential Manager
git config --global credential.helper "/mnt/c/Program\ Files\ \(x86\)/Git\ Credential\ Manager/git-credential-manager.exe"

# For Azure DevOps support only
git config --global credential.https://dev.azure.com.useHttpPath true
```

In **_Windows_** you need to update the `WSLENV` environment variable to include
the value `GIT_EXEC_PATH/wp`. From an _Administrator_ Command Prompt run the
following:

```batch
SETX WSLENV %WSLENV%:GIT_EXEC_PATH/wp
```

After updating the `WSLENV` environment variable, restart your WSL installation.
> [!IMPORTANT]
> In **_Windows_** you need to update the `WSLENV` environment variable to
> include the value `GIT_EXEC_PATH/wp`. From an _Administrator_ Command Prompt
> run the following:
>
> ```batch
> SETX WSLENV %WSLENV%:GIT_EXEC_PATH/wp
> ```
>
> After updating the `WSLENV` environment variable, **restart your WSL
> installation**.

### Using the user-only GCM installer?

Expand Down
Loading