Native build hangs on non-system drive (E:) -- works from C: drive

Summary

Native (WinGet) Claude Code install starts and accepts input when working directory is on E: drive, but hangs indefinitely in "thinking" state. The same workspace works fine from the npm install. The same native install works fine when working directory is on C: drive.

Steps to Reproduce

1. Install Claude Code via WinGet (native build, v2.1.27)
2. cd E:\MRAMSEYBUILDS (secondary/non-system drive)
3. claude
4. Type continue
5. Claude enters thinking state, never returns

Expected Behavior

Session starts normally (as it does from C: drive, and as npm install handles the same E: drive path).

Actual Behavior

• Claude accepts the input and shows thinking indicator
• Stays in thinking state for 2+ minutes
• Eventually returns overloaded_error or continues "thinking" indefinitely

Exact error output:

❯ continue

  ⎿  529 {"type":"error","error":{"type":"overloaded_error","message":"Overloaded"},"request_id":"req_011CXgPj3NNAcHXYLkZuD3gu"}

     Retrying in 0 seconds… (attempt 5/10)

✻ Elucidating… (2m 45s · ↑ 0 tokens)

Note the ↑ 0 tokens after 2m 45s -- no tokens were sent/received despite the long wait.

Key Detail

Same native build, same machine, same Node (v22.22.0) -- works from C: drive, fails from E: drive. npm install (v2.1.29) works from E: drive without issues.

Environment

• Windows 11
• Node v22.22.0
• Native install: WinGet, v2.1.27
• npm install: v2.1.29 (currently using, works fine)
• E: drive is the workspace drive, C: is system drive

Note

This comment was written by Claude (Opus 4.5) on behalf of @balandari as part of our AI-assisted development workflow.