claude-code - 💡(How to fix) Fix [BUG] Claude Code "process exited with code 1" on Windows MSIX/Store – credential handoff and Git Bash path validation fail inside sandbox [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#49451Fetched 2026-04-17 08:40:49
View on GitHub
Comments
2
Participants
2
Timeline
8
Reactions
0
Author
Timeline (top)
labeled ×5commented ×2closed ×1

Error Message

[info] Using Claude Code binary at: C:\Users<user>\AppData\Roaming\Claude\claude-code\2.1.111\claude.exe [error] Session local_<uuid> query error: Claude Code process exited with code 1 [info] [CCD CycleHealth] unhealthy cycle (1s, hadFirstResponse=false, reason=no_response)

CLI output: "Not logged in · Please run /login" CLI output: "Claude Code was unable to find CLAUDE_CODE_GIT_BASH_PATH path"

Fix Action

Fix / Workaround

  • OS: Windows 11 (10.0.26200), AMD Ryzen 7 PRO 250 x64
  • Claude Desktop: Claude_1.3036.0.0_x64__pzs8sxrjxfjjc (Microsoft Store MSIX)
  • Node.js: v24.14.0 (system), v22.22.1 (bundled by other tools)
  • Git: 2.48.1 at C:\Program Files\Git
  • Related issues: #48362 (EXDEV in MSIX), #37022 (exit code 1), #32533 (cross-device rename)
  • Workaround attempted: Junction points, short paths, CLI auth — none resolve it within MSIX
  • The standalone Win32 installer is no longer available from claude.ai/download (only Store stub)

Code Example

[info] Using Claude Code binary at: C:\Users\<user>\AppData\Roaming\Claude\claude-code\2.1.111\claude.exe
[error] Session local_<uuid> query error: Claude Code process exited with code 1
[info] [CCD CycleHealth] unhealthy cycle (1s, hadFirstResponse=false, reason=no_response)

CLI output: "Not logged in · Please run /login"
CLI output: "Claude Code was unable to find CLAUDE_CODE_GIT_BASH_PATH path"
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Claude Code in the Desktop app (Microsoft Store / MSIX) immediately crashes with "Claude Code process exited with code 1" on every message. Regular claude.ai chat works fine. The bundled claude.exe (v2.1.111) works perfectly when run manually from the command line.

Two issues compound inside the MSIX sandbox:

  1. OAuth credential handoff fails. The Desktop app stores its OAuth token in the MSIX-virtualized config.json, but the spawned Claude Code subprocess cannot read it. Running the subprocess manually shows "Not logged in · Please run /login". Even after creating <a class="file-link" data-path="~/.claude/.credentials.json" title="Click to open">~/.claude/.credentials.json</a> via CLI auth, the second issue blocks startup.

  2. Git Bash path validation fails. CLAUDE_CODE_GIT_BASH_PATH is correctly set (confirmed via echo $env:CLAUDE_CODE_GIT_BASH_PATH and dir on the path succeeds), but Claude Code reports "was unable to find CLAUDE_CODE_GIT_BASH_PATH path". The jH8() validation function in cli.js runs dir "<path>" via execSync, which succeeds in isolation, but fails when launched from the MSIX sandbox context. Tested with: original path (C:\Program Files\Git\bin\bash.exe), 8.3 short path (C:\PROGRA~1\Git\bin\bash.exe), and junction (C:\Git\bin\bash.exe) — all fail from the Store app, all succeed from a normal shell.

The combination means Claude Code can never start from the MSIX Desktop app.

What Should Happen?

Claude code on desktop should work

Error Messages/Logs

[info] Using Claude Code binary at: C:\Users\<user>\AppData\Roaming\Claude\claude-code\2.1.111\claude.exe
[error] Session local_<uuid> query error: Claude Code process exited with code 1
[info] [CCD CycleHealth] unhealthy cycle (1s, hadFirstResponse=false, reason=no_response)

CLI output: "Not logged in · Please run /login"
CLI output: "Claude Code was unable to find CLAUDE_CODE_GIT_BASH_PATH path"

Steps to Reproduce

  1. Install Claude Desktop from Microsoft Store on Windows 10/11
  2. Ensure Git is installed (C:\Program Files\Git)
  3. Set CLAUDE_CODE_GIT_BASH_PATH=C:\Program Files\Git\bin\bash.exe (User env var)
  4. Open Code tab, select any folder
  5. Send any message
  6. Result: "Claude Code process exited with code 1" — crash in <1 second
<img width="1919" height="1198" alt="Image" src="https://github.com/user-attachments/assets/c66cda6f-dcd7-4200-a707-942ec2e2e0d1" />

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

2.1.111

Claude Code Version

2.1.111

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

  • OS: Windows 11 (10.0.26200), AMD Ryzen 7 PRO 250 x64
  • Claude Desktop: Claude_1.3036.0.0_x64__pzs8sxrjxfjjc (Microsoft Store MSIX)
  • Node.js: v24.14.0 (system), v22.22.1 (bundled by other tools)
  • Git: 2.48.1 at C:\Program Files\Git
  • Related issues: #48362 (EXDEV in MSIX), #37022 (exit code 1), #32533 (cross-device rename)
  • Workaround attempted: Junction points, short paths, CLI auth — none resolve it within MSIX
  • The standalone Win32 installer is no longer available from claude.ai/download (only Store stub)

extent analysis

TL;DR

The most likely fix involves addressing the OAuth credential handoff failure and Git Bash path validation failure within the MSIX sandbox context.

Guidance

  1. Investigate OAuth token storage and access: Ensure the Claude Code subprocess can read the OAuth token stored in the MSIX-virtualized config.json. This might involve modifying the token storage location or adjusting the subprocess's permissions.
  2. Modify the Git Bash path validation: Update the jH8() validation function in cli.js to handle the MSIX sandbox context correctly. This could involve using a different method to validate the Git Bash path or adjusting the execSync command to work within the sandbox.
  3. Test with modified environment variables: Verify that setting environment variables, such as CLAUDE_CODE_GIT_BASH_PATH, works as expected within the MSIX sandbox. This might involve using a different approach to set these variables or adjusting the sandbox's configuration.
  4. Explore alternative authentication methods: Consider using alternative authentication methods that do not rely on the MSIX-virtualized config.json, such as storing the OAuth token in a secure, sandbox-accessible location.

Example

No code snippet is provided due to the complexity of the issue and the need for further investigation.

Notes

The provided information suggests that the issue is specific to the MSIX sandbox context and may require modifications to the Claude Code application or the MSIX configuration. Further debugging and testing are necessary to determine the root cause and develop a comprehensive solution.

Recommendation

Apply a workaround by modifying the OAuth token storage and Git Bash path validation to accommodate the MSIX sandbox context, as the issue seems to be related to the interaction between the Claude Code application and the MSIX environment.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Claude Code "process exited with code 1" on Windows MSIX/Store – credential handoff and Git Bash path validation fail inside sandbox [2 comments, 2 participants]