Claude Code /config diagnostics reports "native install not in PATH" even when it is (Windows)
Resolved 💬 3 comments Opened Apr 17, 2026 by LuisLacasaMCHP Closed Apr 17, 2026
Bug
/config diagnostics panel shows:
⚠ Native installation exists but C:\Users\M44041\.local\bin is not in your PATH
Even though the path IS present in both the Windows User PATH and the current process PATH.
Environment
- Claude Code version: 2.1.112
- OS: Windows 11 Enterprise 10.0.26100
- Shell: PowerShell
Details
C:\Users\M44041\.local\bin\claude.exeexistsC:\Users\M44041\.local\binis in the Windows User PATH (verified via[Environment]::GetEnvironmentVariable('Path', 'User'))- The path is also in the process PATH (verified via
$env:Pathin PowerShell) DISABLE_INSTALLATION_CHECKS=1is set — this suppresses the startup warning but NOT the/configdiagnostics panel
Expected behavior
/config should not show the PATH warning when the path is present. Alternatively, DISABLE_INSTALLATION_CHECKS=1 should also suppress the /config diagnostic.
Likely cause
The diagnostics check may be doing a case-sensitive or format-sensitive path comparison that fails even when the binary resolves correctly on Windows.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗