Codex sandbox fails to start on Windows mapped drive workspace

Open 💬 4 comments Opened Apr 25, 2026 by ericvanduser8-lgtm
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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_

View original on GitHub ↗

4 Comments

ericvanduser8-lgtm · 4 months ago

always requires about 3 permission click to allow Codex to read anything, very annoying

github-actions[bot] contributor · 4 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #19277
  • #18620

Powered by Codex Action

albertc71 · 4 months ago

Curious if you experience the same thing in Codex app. Or this is unique to the Codex plugin in VS Code?

pke · 14 days ago
Curious if you experience the same thing in Codex app. Or this is unique to the Codex plugin in VS Code?

Thats for the codex Windows 11 app from the appstore too!