[BUG] Edit/Write tools hang silently on Windows 11 (v2.1.143)
Status Fixed / completed
Maintainer reply None cached
Workaround ✓ Mentioned in description ↑
Activity 5 comments · opened May 18, 2026 · closed May 21, 2026
Environment
- OS: Windows 11 Home 10.0.26200
- Claude Code: v2.1.143 (latest)
- Shell: PowerShell / Bash
Bug
Edit and Write tools hang silently — no error, no output, no file changes.
Sessions freeze for 30+ minutes until manually stopped. On retry, sometimes
succeeds, mostly fails again.
Bash-based file operations (node, printf, sed) succeed on the same files.
Steps to reproduce
- Open any project on Windows 11 with v2.1.143
- Ask Claude to edit a file — Claude uses the Edit or Write tool
- Session hangs indefinitely, no error surfaced — must force-stop manually
Expected
Edit/Write tools modify the file and return success.
Actual
Tool hangs silently. No error reported. File unchanged. Only recovery is
manual stop + retry (non-deterministic — sometimes works, usually doesn't).
Bash workarounds work reliably.
Note
Issue #46767 describes a similar bug from April (v2.1.101). This appears to be
a regression or continuation of that bug in the latest release.
5 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Not a duplicate. #59200 is about tool result delivery failing for Bash/PowerShell calls. This issue is specific to the Edit and Write file-editing tools hanging silently. Different tools, different code path.
Fixed in v2.1.146 — Edit and Write tools work normally again on Windows 11.
I wouldnt say this is closed, I've been experiencing exactly this intermittently for weeks. I've let it run for over an hour and still had to cancel it myself and it's done edits/writes via powershell script instead, but this tanks my quota quicker / builds context faster. v2.1.190.
Windows 11 Home 23H2 22631.5189
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.