[Bug] Bash tool fails on Windows 11 with EINVAL when writing temp output files
Status Fixed / completed
Reported on v2.1.53
Maintainer reply None cached
Activity 3 comments · opened Feb 25, 2026 · closed Feb 25, 2026
Bug Description
/bug Bash tool broken on Windows 11 - every command fails with EINVAL: invalid argument when opening temp output file.
Path: C:\Users\USER\AppData\Local\Temp\claude\C--Users-USER-Documents-WorksClaude\tasks\*.output. Manual file
creation in the same path via PowerShell works fine. Started after adding PostToolUse hook (now removed). Persists
across restarts, temp folder deletion, and different project directories.
Environment Info
- Platform: win32
- Terminal: windows-terminal
- Version: 2.1.53
- Feedback ID: 47423f42-93bc-4caf-af84-ea68b89840a0
Errors
[{"error":"Error: EINVAL: invalid argument, open 'C:\\Users\\USER\\AppData\\Local\\Temp\\claude\\C--Users-USER-Documents-WorksClaude\\tasks\\be24vk00k.output'\n at openSync (unknown)\n at $3$ (B:/~BUN/root/claude.exe:1756:2307)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-02-25T01:46:19.161Z"}]
3 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Hi, thanks for reporting. We just released v2.1.55 which should fix this.
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.