windows sandbox: setup refresh failed with status exit code: 1 #14409

Activity

1. i-schuyler

   added

   bugSomething isn't workingSomething isn't working

   on Mar 11, 2026
2. github-actions

   added

   CLIIssues related to the Codex CLIIssues related to the Codex CLI

   windows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems

   sandboxIssues related to permissions or sandboxingIssues related to permissions or sandboxing

   on Mar 11, 2026
3. github-actions commented on Mar 11, 2026

   

   github-actionsBot

   on Mar 11, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • v0.107.0 Windows Sandbox ACL Failure (Error 5) and Unintended Permission Pollution on User Home Directory #13378

   Powered by Codex Action
4. etraut-openai

   removed

   CLIIssues related to the Codex CLIIssues related to the Codex CLI

   on Mar 11, 2026
5. Shubender commented on Mar 12, 2026

   

   Shubender

   on Mar 12, 2026

   More actions

   The same problem in VS Code and Codex App.
6. GitMurf commented on Mar 20, 2026

   

   GitMurf

   on Mar 20, 2026

   More actions

   @i-schuyler I have had same issues on Codex App for Windows! For what its worth, the only "workaround" / fix for now is using the Codex CLI directly and rolling back to v0.113. See my comment here in another similar gh issue: #14675 (comment)

   Can't use the Codex App or the VScode extension, but can at least use the Codex CLI directly for now.
7. GitMurf commented on Mar 20, 2026

   

   GitMurf

   on Mar 20, 2026

   More actions

   @i-schuyler @Shubender I was able to get a little further in debugging the issue. Here is a workaround that should work with current version of Codex: #14675 (comment)
8. Shubender commented on Mar 26, 2026

   

   Shubender

   on Mar 26, 2026

   More actions

   @GitMurf thanks for your comment and solution. I came up with a solution that wasn't exactly the smartest, but it saved me from errors and unnecessary queries - I simply “asked” it not to use apply_patch in AGENTS.md

   ## Editing policy
   
   Absolute rule: never use `apply_patch`, `apply_patch`-like tools, or any internal file-editing tool.
   
   Never use any tool or workflow that may invoke sandboxed editing, virtualized editing, or sandbox setup/refresh.
   
   For all file modifications, use shell-only editing commands such as PowerShell `Get-Content` / `Set-Content` / .NET file APIs.
   
   If any edit tool fails with a sandbox-related error, do not retry it and do not use any internal editing tool again in that turn.
   
9. notnotype commented on Apr 3, 2026

   

   notnotype

   on Apr 3, 2026

   More actions

   On Windows, sandboxed file edits fail with:

   windows sandbox: helper_firewall_rule_create_or_add_failed: SetRemoteAddresses failed: Error { code: HRESULT(0x80070057), message: "参数错误。" }

   What I verified:

   • BFE and MpsSvc are running
   • inside sandbox, Get-NetFirewallProfile / New-NetFirewallRule return access denied
   • outside sandbox (elevated), Get-NetFirewallProfile works
   • outside sandbox (elevated), creating/removing a temporary firewall rule works

   This suggests Windows Firewall itself is healthy, and the failure is specific to Codex's Windows sandbox helper when configuring firewall rules.