Sandbox Schannel HTTPS fails

“curl: (35) schannel: AcquireCredentialsHandle failed: SEC_E_NO_CREDENTIALS (0x8009030e)”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/14185/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports in the last two weeks, down from 1 a week at the mid-September peak.

Schannel HTTPS fails with SEC_E_NO_CREDENTIALS in Windows sandbox. Sandboxed commands, including curl and CLI login, fail before the TLS handshake; the same request succeeds from normal PowerShell.

Is this your bug?

File my report

Where: Windows sandbox
Error text: curl: (35) schannel: AcquireCredentialsHandle failed: SEC_E_NO_CREDENTIALS (0x8009030e)
Versions: 0.163.0 to 26.928.20755
Platforms: Windows
How bad: Breaks a normal workflow. Some reports say it blocks them completely.

Related: Full access/network setting not applied

Not quite your bug?

Sandbox setup lock failure12 people
Sandbox children exit 0xC00001422 people
Network blocked despite setting on6 people

Original reports3, newest first

Oct 20, 2026Windows restricted execution context: Schannel TLS acquisition returns SEC_E_NO_CREDENTIALS before isolated Codex login completes (0.163.0)On GitHub#55492
Oct 3, 2026Windows sandbox processes run without a loaded user profile — all Schannel HTTPS fails with SEC_E_NO_CREDENTIALS (creating the profile does not fix it)On GitHub#50582
Sep 19, 2026[Windows] Codex sandbox Schannel fails with SEC_E_NO_CREDENTIALS; elevated sandbox launches without loaded user profileOn GitHub#46726