[BUG] Windows native version 1.0.117 locks up immediately after starting
Status Fixed / completed
Maintainer reply ✓ Yes — ant-kurt
Workaround ✓ Mentioned in thread ↓
Activity 8 comments · opened Sep 17, 2025 · closed Sep 19, 2025
💡 Likely answer: A maintainer (ant-kurt, collaborator)
responded on this thread — see the highlighted reply below.
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?
After updating to version 1.0.117 on windows using the native installation method, any time I start Claude, it shows the startup messages and input box, but no keystrokes are registered, not even ctrl-C. Only way to exit is to close the terminal.
What Should Happen?
Should not lock up.
Error Messages/Logs
Steps to Reproduce
Install 1.0.117 on windows, attempt to start it.
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
1.0.115
Claude Code Version
1.0.117
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
_No response_
8 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
I don't think this is duplicate as it was working earlier today on 1.0.115.
Yeah, had the same issue since this morning (Windows 11 / native), even wiped all .claude settings from my machine and reinstalled. No dice.
Every version since 1.0.114+ immediately locks up. I rolled back to 1.0.113 for now.
Hey, this is a duplicate of #7693 (affecting versions from 1.0.115 to latest 1.0.117)
Would you mind checking Task Manager and seeing if the Claude process is idle or consuming CPU, and do you see related processes running?
Are you running directly in Windows Terminal or in an IDE terminal?
As a workaround, please try downgrading to 1.0.110 while we continue to investigate this.
Claude looks completely idle in task manager, no CPU, disk or network activity. I am running directly in Windows Terminal.
A few minutes ago I tested this on a second windows pc here, after the update to 1.0.117, the very first run it worked, but starting with the second time I started claude it was hanging and required closing the terminal to exit.
Update: We've got a fix coming in 1.0.118. Alternately, temporarily downgrade to 1.0.113.
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.