[BUG] Claude Code stays frozen when loading, and no errors are printed when using --verbose.
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?
Whenever I try to use claude anywhere, it asks for using claude in that folder, but then it gets stuck, completely, with no errors, i even tried using --verbose but no errors were printed.
I am kinda skeptical this has already been issued but I'm not sure, i already searched and the issues are slightly different, because mine is just claude code being frozen at startup after the folder permission screen.
What Should Happen?
Open the TUI chat app as expected.
Error Messages/Logs
No errors.Steps to Reproduce
- Open any terminal app (Ex. Windows Terminal or Git Bash)
- Run
claude - Accept the folder permission window
- Now the TUI app is stuck.
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.69 (Claude Code)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
I also tried the Git Bash terminal app but that didn't change anything. I verified everything was installed correctly and it was.
I also tried adding "env": {
"CLAUDE_CODE_GIT_BASH_PATH": "C:\\Program Files\\Git\\bin\\bash.exe"
}
to the settings.json file but that didn't change anything either.
Also tried the "Enter" trick that most said worked, but for me, it didn't.
To regain control of my terminal, I have to create a new terminal window and remove the old one.
9 Comments
experiencing the same bug
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
So, my issue isn't any of these, since most of these have error outputs, meanwhile I don't, at all.
For the last one, its still a bit different.
Similar error for me. Open terminal, type claude, the prompt appears :
Quick safety check: Is this a project you created or one you trust? (Like your own code, a well-known open source
project, or work from your team). If not, take a moment to review what's in this folder first.
Claude Code'll be able to read, edit, and execute files here.
I select 1. Yes, I trust this folder ✔ -> now the terminal is stuck, nothing is happening.
I can exit if I press 2.
I just reverted to latest stable version instead of .69 and it fixed the issue, so I believe it's an error with the latest version.
this seems to be because of the readOnly attribute on the user folder
you can check this by running
attrib C:\Users\<username>when R is shown it is most likely the problem.
possible fixes is to downgrade to v2.1.68 or remove the readOnly attribute with
attrib -R C:\Users\<username>I experience the exact same bug on Windows 11. Claude Code CLI hangs during start up, nothing is shown, no logo etc.
It started today with new version 2.1.69. Yesterday, with 2.1.66 CC worked.
I don't see any suspicious events in debug log.
I even tried uninstalling and re-installing CC, but the recommended native PowerShell installation of the latest version 2.1.69 does not finish - installer also hangs without any error.
So, I tried re-installing older version 2.1.66 and it worked. Though, the method of installing older versions in documentation is not correct and does not work (it always installs the latest version no matter what), when I manually downloaded and installed 2.1.66 version, it worked as expected.
I also tried downloading 2.1.66 installer, but let it install the latest version (2.1.69). CC 2.1.69 installed correctly this way, it launched, but during first setup, when selecting Dark/Light mode, it did not do anything after pressing Enter.
The problem is clearly with new version 2.1.69 on Windows platform.
fixed it! thank you @SaiKai, seems like for me that was the issue and indeed a duplicate, sorry!
However, they should fix the bug without removing readonly.
The problem is not solved. Version 2.1.69 does not work on Windows 11. Not even the new installation of 2.1.69 works. However, 2.1.66 works correctly. Something is wrong with 2.1.69. Please see my previous post for more details.
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.