[Bug] Bash tool fails on Windows 11 with EINVAL when writing temp output files

Resolved 💬 3 comments Opened Feb 25, 2026 by jun2077681 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"}]

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗