fix(install): correct Windows PATH troubleshooting docs (#28102)

* fix(install): correct Windows PATH troubleshooting — no \bin suffix needed (closes #19921)

* fix(docs): apply same PATH fix to FAQ
This commit is contained in:
Glucksberg
2026-03-02 13:07:07 -04:00
committed by GitHub
parent 11562c452a
commit 7a55a3ca07
2 changed files with 2 additions and 2 deletions

View File

@@ -578,7 +578,7 @@ Two common Windows issues:
npm config get prefix
```
- Ensure `<prefix>\\bin` is on PATH (on most systems it is `%AppData%\\npm`).
- Add that directory to your user PATH (no `\bin` suffix needed on Windows; on most systems it is `%AppData%\npm`).
- Close and reopen PowerShell after updating PATH.
If you want the smoothest Windows setup, use **WSL2** instead of native Windows.

View File

@@ -384,7 +384,7 @@ Use non-interactive flags/env vars for predictable runs.
</Accordion>
<Accordion title='Windows: "openclaw is not recognized"'>
Run `npm config get prefix`, append `\bin`, add that directory to user PATH, then reopen PowerShell.
Run `npm config get prefix` and add that directory to your user PATH (no `\bin` suffix needed on Windows), then reopen PowerShell.
</Accordion>
<Accordion title="Windows: how to get verbose installer output">