Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Windows 11 - claude.exe hangs indefinitely due to CRYPT_E_NO_REVOCATION_CHECK schannel TLS error [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46506•Fetched 2026-04-11 06:18:29
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
tpozzytpozzy
Participants
github-actions[bot]github-actions[bot]tpozzytpozzy
Timeline (top)
labeled ×3commented ×1

Error Message

Error Messages/Logs

Fix Action

Fix / Workaround

Workaround needed: claude.exe needs a way to bypass schannel revocation checking, similar to curl's --ssl-no-revoke flag. Possibly via NODE_OPTIONS or an app-level setting.

Code Example

Windows schannel fails with CRYPT_E_NO_REVOCATION_CHECK (0x80092012) when attempting TLS connection to api.anthropic.com. The server performs a double TLS renegotiation during handshake which appears to trigger the failure.
curl.exe -v https://api.anthropic.com returns:
schannel: next InitializeSecurityContext failed: CRYPT_E_NO_REVOCATION_CHECK (0x80092012)
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Claude Code VS Code extension spins indefinitely and never responds. The CLI (claude.exe --print "hello") also hangs with no output.

What Should Happen?

claude.exe should response to simple commands and not hang.

Error Messages/Logs

Windows schannel fails with CRYPT_E_NO_REVOCATION_CHECK (0x80092012) when attempting TLS connection to api.anthropic.com. The server performs a double TLS renegotiation during handshake which appears to trigger the failure.
curl.exe -v https://api.anthropic.com returns:
schannel: next InitializeSecurityContext failed: CRYPT_E_NO_REVOCATION_CHECK (0x80092012)

Steps to Reproduce

Execute a this command: claude.exe "say hello"

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.100 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

curl.exe --ssl-no-revoke https://api.anthropic.com returns a proper 401 response, confirming the connection works when revocation checking is bypassed. Debug output shows claude.exe makes calls to /api/event_logging/v2/batch and /api/claude_code/settings then hangs and exits with code 1. Things that did NOT fix it:

Clearing certutil URL cache (certutil -urlcache * delete) Disabling "Check for server certificate revocation" in Internet Options Setting HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\CertificateRevocationCheck to 0 Setting NODE_TLS_REJECT_UNAUTHORIZED=0 Setting git config --global http.schannelCheckRevoke false Clean reinstall of Claude Code extension Rebooting

Workaround needed: claude.exe needs a way to bypass schannel revocation checking, similar to curl's --ssl-no-revoke flag. Possibly via NODE_OPTIONS or an app-level setting.

extent analysis

TL;DR

The issue can be worked around by configuring Claude Code to bypass TLS revocation checking, similar to how curl uses the --ssl-no-revoke flag.

Guidance

  • Investigate setting NODE_OPTIONS to include --tls-reject-unauthorized=0 or an equivalent flag to bypass revocation checking in Claude Code.
  • Consider adding a configuration option in Claude Code to explicitly control TLS revocation checking, similar to curl's --ssl-no-revoke flag.
  • Review the debug output to understand the sequence of API calls made by claude.exe and verify if the issue is indeed related to the TLS handshake.
  • Test the workaround using curl.exe --ssl-no-revoke https://api.anthropic.com to confirm that bypassing revocation checking resolves the issue.

Example

No code snippet is provided as the issue is related to configuration and TLS settings.

Notes

The provided workaround using curl.exe --ssl-no-revoke https://api.anthropic.com suggests that bypassing revocation checking may resolve the issue. However, this may have security implications and should be carefully evaluated.

Recommendation

Apply workaround: Configure Claude Code to bypass TLS revocation checking using NODE_OPTIONS or an equivalent mechanism, as this has been shown to resolve the issue in a similar context using curl.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#API routing#API middleware#SSR setup#ISR setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING