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
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:
Observed:
Normal shell_command calls fail before command execution with errors:
Examples:
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