codex - 💡(How to fix) Fix execution error: Io(Custom { kind: Other, error: "windows sandbox: spawn setup refresh" }) [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
openai/codex#19277Fetched 2026-04-24 10:39:28
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×4commented ×1unlabeled ×1

Error Message

execution error: Io(Custom { kind: Other, error: "windows sandbox: spawn setup refresh" })

RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

0.124.0.0

What subscription do you have?

api

Which model were you using?

gpt-5.4

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What terminal emulator and version are you using (if applicable)?

PowerShell 7.6

What issue are you seeing?

I keep getting errors when reading files, even after granting permissions. execution error: Io(Custom { kind: Other, error: "windows sandbox: spawn setup refresh" })

What steps can reproduce the bug?

Get-ChildItem -Name | Select-Object -First 40

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

The issue may be related to the Windows sandbox environment, and adjusting the execution policy or running the command in a different context might resolve the error.

Guidance

  • The error message "windows sandbox: spawn setup refresh" suggests a potential issue with the Windows sandbox environment, which might be interfering with the file reading operation.
  • Try running the command Get-ChildItem -Name | Select-Object -First 40 in a different terminal emulator or as an administrator to see if the issue persists.
  • Consider adjusting the execution policy using the Set-ExecutionPolicy cmdlet to allow scripts to run in the current scope.
  • Verify that the file permissions are correctly set and that the user running the command has the necessary access rights.

Notes

The issue might be specific to the Windows sandbox environment and the Codex CLI version 0.124.0.0. Further investigation into the sandbox settings and the CLI's interaction with the Windows environment may be necessary to fully resolve the issue.

Recommendation

Apply workaround: Adjust the execution policy and run the command in a different context to see if it resolves the error, as the root cause is likely related to the Windows sandbox environment.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix execution error: Io(Custom { kind: Other, error: "windows sandbox: spawn setup refresh" }) [1 comments, 2 participants]