codex - 💡(How to fix) Fix Codex sandbox fails to start on Windows mapped drive workspace [3 comments, 3 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#19599Fetched 2026-04-26 05:14:09
View on GitHub
Comments
3
Participants
3
Timeline
7
Reactions
0
Timeline (top)
labeled ×4commented ×3

Error Message

Environment: - Windows - Workspace path: L:\cs-web - Also related UNC path: \video1\node\cs-web - Shell: PowerShell - Sandbox mode: workspace-write Observed: Normal shell_command calls fail before command execution with errors: - windows sandbox: CreateProcessWithLogonW failed: 267 - windows sandbox: setup refresh failed with status exit code: 1 Examples: - Get-Content -LiteralPath .\context\README.md with workdir L:\cs-web fails - Get-ChildItem from C:\Users\eric also failed once with setup refresh error Workaround: Escalated PowerShell commands from C:\Users\eric using explicit L:\cs-web paths work. Expected: Sandboxed commands should initialize and read workspace files normally, especially after the project path is trusted in Codex config.

  • Get-ChildItem from C:\Users\eric also failed once with setup refresh error

Fix Action

Fix / Workaround

Environment: - Windows - Workspace path: L:\cs-web - Also related UNC path: \video1\node\cs-web - Shell: PowerShell - Sandbox mode: workspace-write Observed: Normal shell_command calls fail before command execution with errors: - windows sandbox: CreateProcessWithLogonW failed: 267 - windows sandbox: setup refresh failed with status exit code: 1 Examples: - Get-Content -LiteralPath .\context\README.md with workdir L:\cs-web fails - Get-ChildItem from C:\Users\eric also failed once with setup refresh error Workaround: Escalated PowerShell commands from C:\Users\eric using explicit L:\cs-web paths work. Expected: Sandboxed commands should initialize and read workspace files normally, especially after the project path is trusted in Codex config.

Workaround: Escalated PowerShell commands from C:\Users\eric using explicit L:\cs-web paths work.

RAW_BUFFERClick to expand / collapse

What version of the IDE extension are you using?

7.711.473

What subscription do you have?

Plus

Which IDE are you using?

vscode

What platform is your computer?

Environment: - Windows - Workspace path: L:\cs-web - Also related UNC path: \video1\node\cs-web - Shell: PowerShell - Sandbox mode: workspace-write Observed: Normal shell_command calls fail before command execution with errors: - windows sandbox: CreateProcessWithLogonW failed: 267 - windows sandbox: setup refresh failed with status exit code: 1 Examples: - Get-Content -LiteralPath .\context\README.md with workdir L:\cs-web fails - Get-ChildItem from C:\Users\eric also failed once with setup refresh error Workaround: Escalated PowerShell commands from C:\Users\eric using explicit L:\cs-web paths work. Expected: Sandboxed commands should initialize and read workspace files normally, especially after the project path is trusted in Codex config.

What issue are you seeing?

Codex sandbox fails to start on Windows mapped drive workspace

Environment:

  • Windows
  • Workspace path: L:\cs-web
  • Also related UNC path: \video1\node\cs-web
  • Shell: PowerShell
  • Sandbox mode: workspace-write

Observed: Normal shell_command calls fail before command execution with errors:

  • windows sandbox: CreateProcessWithLogonW failed: 267
  • windows sandbox: setup refresh failed with status exit code: 1

Examples:

  • Get-Content -LiteralPath .\context\README.md with workdir L:\cs-web fails
  • Get-ChildItem from C:\Users\eric also failed once with setup refresh error

Workaround: Escalated PowerShell commands from C:\Users\eric using explicit L:\cs-web paths work.

Expected: Sandboxed commands should initialize and read workspace files normally, especially after the project path is trusted in Codex config.

What steps can reproduce the bug?

always

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

The issue can be mitigated by using explicit paths for PowerShell commands, such as L:\cs-web instead of relying on relative paths.

Guidance

  • The error CreateProcessWithLogonW failed: 267 suggests an issue with process creation in the sandboxed environment, potentially related to the mapped drive workspace.
  • Using explicit paths for PowerShell commands, as in the provided workaround, may help resolve the issue.
  • Verify that the project path is correctly trusted in the Codex config to ensure sandboxed commands can access workspace files.
  • Test commands with both relative and absolute paths to identify any path-related issues.

Example

No code snippet is provided as the issue is more related to configuration and environment setup.

Notes

The issue seems to be specific to the Windows environment and mapped drive workspace, so the solution may not apply to other platforms or setups.

Recommendation

Apply workaround: Using explicit paths for PowerShell commands can help mitigate the issue until a more permanent fix is found, as it allows commands to execute correctly even in the sandboxed 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 Codex sandbox fails to start on Windows mapped drive workspace [3 comments, 3 participants]