From 7a55a3ca07f1e4b2a778c75c63dd781bbe3db7eb Mon Sep 17 00:00:00 2001
From: Glucksberg <80581902+Glucksberg@users.noreply.github.com>
Date: Mon, 2 Mar 2026 13:07:07 -0400
Subject: [PATCH] fix(install): correct Windows PATH troubleshooting docs
 (#28102)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

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

* fix(docs): apply same PATH fix to FAQ
---
 docs/help/faq.md          | 2 +-
 docs/install/installer.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/help/faq.md b/docs/help/faq.md
index 0a81714eeff..a82efca6fce 100644
--- a/docs/help/faq.md
+++ b/docs/help/faq.md
@@ -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.
diff --git a/docs/install/installer.md b/docs/install/installer.md
index 331943d0a33..78334681ad4 100644
--- a/docs/install/installer.md
+++ b/docs/install/installer.md
@@ -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">