[BUG] Claude Code "process exited with code 1" on Windows MSIX/Store – credential handoff and Git Bash path validation fail inside sandbox

Status Fixed / completed
Reported on v2.1.111
Maintainer reply None cached
Activity 3 comments · opened Apr 16, 2026 · closed Apr 16, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] 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.
  1. 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)

View original on GitHub ↗

3 Comments

github-actions[bot] · 6 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/48362
  2. https://github.com/anthropics/claude-code/issues/47977
  3. https://github.com/anthropics/claude-code/issues/49395

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

2Ntlaks · 6 months ago

_Update: I found the issue on my machine._

The immediate cause was not the MSIX sandbox itself. My Windows ComSpec environment variable had a leading space, which caused shell spawning to fail, and I was also on an outdated Claude Code CLI version.

Fixes that resolved it:

  • corrected ComSpec to C:\Windows\System32\cmd.exe
  • updated @anthropic-ai/claude-code to the latest version

Because of that, this may not be a true duplicate of the linked issues, but it also may not be a product bug in Claude Desktop/MSIX. I’m leaving this update here in case others hit the same symptom with a local Windows environment issue.

github-actions[bot] · 5 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.