Codex Windows sandbox setup failed

Opening the app and completing sandbox setup are separate checks. Capture the setup error, distinguish a missing administrator prompt from a helper failure, and use the documented fallback only with its security limits understood.

Error message

These are separate exact messages from Windows desktop issue #40550 and issue #37940:

Windows setup didn’t finish • helper_failed
Windows setup didn't finish
hide users: failed to hide current user profile dir (C:\Users\Default): SetFileAttributesW failed for C:\Users\Default: 5 (Access is denied.)

The first report had a UAC prompt followed by helper_failed; the second saw no UAC prompt and found the SetFileAttributesW line in a sandbox log. These are not interchangeable causes. A screen that merely says “Finish Windows setup” has not identified the failing step.

When it happens

This guide is for the Windows desktop app’s local sandbox setup, with public reports on builds 26.818.8289.0 and 26.803.10989.0. No fixed build or universal remedy is established. The official Windows sandbox documentation describes elevated setup, policy constraints and an unelevated fallback with weaker isolation. It does not say that every setup loop is an antivirus problem or that broad file-permission changes are safe.

Separate the app window from command execution. A window can open even though the sandbox helper cannot start or a sandboxed command cannot read a Windows-managed path. Similarly, approval of a UAC prompt shows that elevation was requested, not that the helper finished. Record the exact wording, app build, time and whether UAC appeared; then follow the corresponding branch below. Keep logs private until you have removed personal paths and credentials.

Fix it step by step

  1. Capture the first specific failure. Write down the full banner and whether the setup offered “Try Windows setup again.” Record the Windows and Codex app versions. If the error includes helper_failed, preserve that label and any earlier helper output. If the screen only loops, find the sandbox log documented by OpenAI under your active CODEX_HOME/.sandbox/sandbox.log. Use the home of the affected Windows app, not a WSL home or an assumed path from another machine.
  2. Classify the elevation path. If a genuine UAC prompt appeared and was declined, retry only if you intend and are allowed to approve the one-time setup. If no prompt appeared, do not infer that UAC is disabled: issue #37940 reported working UAC elsewhere while this flow produced no prompt. Save the exact failure and policy context. If you approved a prompt and then got helper_failed, move to the helper branch rather than repeating the approval indefinitely.
  3. Check the installed app without changing protection settings. On Windows, Get-AppxPackage OpenAI.Codex | Select-Object Name,Version,Status can show package identity and status. In issue #40550, the package status was Ok, the helper existed and had a valid signature, yet the helper still failed with access denied. Those checks narrow the failure but do not prove that sandbox initialization succeeded. Do not download a replacement helper from an unofficial site.
  4. If UAC is blocked by a managed-device policy, use the official path. The Windows sandbox guide lists policies involving local users, groups, firewall configuration and logon rights among setup constraints. Give your administrator the app build, failing operation, timestamp and the relevant log line. Do not apply a blanket ownership or Full Control command to Windows system profiles. In issue #37940, the reporter deliberately avoided changing the ACL on C:\Users\Default; that report does not establish that such a change would repair the product.
  5. If the helper fails after approval, inspect its actual error. A signed helper can still be blocked from launching or fail during later work. Issue #40550 reported Program 'codex-windows-sandbox-setup.exe' failed to run: Access is denied after signature validation. Preserve the first specific line, not only the final “setup didn’t finish” banner. If the log names a directory, determine whether it is user-owned or Windows-managed before any targeted repair. Simply reinstalling or disabling security software did not establish a fix in that report.
  6. Consider the documented fallback only with its tradeoff. OpenAI documents an unelevated Windows sandbox for systems where elevated setup cannot complete. It offers weaker isolation, so use it only if the machine’s policy and your task permit that mode. It does not prove the original elevated sandbox is repaired. The no-UAC report says its unelevated test still returned Access is denied; therefore even this fallback cannot be promised as a fix. Full Access broadens permissions further and is not a substitute for diagnosing a failed setup helper.
  7. Verify local execution, not just an app response. After one repair or a deliberate fallback, check the active sandbox mode and ask Codex to run a harmless read-only local command in the intended project, such as listing top-level filenames. A text answer without a local command does not test the sandbox. Record separately whether elevated setup completed, a fallback was selected and the read-only command worked. If the error changed, keep the new message; do not continue treating every local-execution failure as the original setup loop.

Still not working?

  • If no UAC prompt appears on a managed device, give IT the exact setup attempt time, app build and sandbox log excerpt. Repeated clicks without a changed condition provide no additional evidence.
  • If helper_failed persists after approval, report the first helper error and whether the installed package and helper were present. A valid signature alone did not resolve issue #40550.
  • If the app opens but the read-only command fails, keep the command’s own error. The problem may now be command execution, a missing companion binary or policy, rather than the setup banner itself.

FAQ

Why does Windows setup say helper_failed after I approved UAC?

Approval only lets the helper attempt its work. One public report had a signed installed helper but still got access denied when it ran. Inspect the first helper error and the sandbox log before choosing a repair; the label alone does not identify the blocked operation.

Does no UAC prompt mean my UAC is turned off?

No. Issue #37940 reported ordinary UAC prompts elsewhere but none in this setup flow. Record the exact app build and setup error, especially on a managed device. Do not change global UAC settings based only on this symptom.

Is the unelevated sandbox a fix for Windows setup?

It is an officially documented fallback with weaker isolation, not proof that elevated setup completed. It can still fail under other local restrictions, as one public report found. Check the active mode and perform a harmless local read-only operation to verify your particular setup.

Compare another message in the Codex error guide library. First check whether this is a Codex service-side problem → View live Codex status.

Sources

Each source lists what it is used to support. Sources are re-read on the review schedule, not continuously.

  • Official Windows sandbox troubleshooting

    Official documentation · checked 2026-10-02

    Documents elevated setup prerequisites, UAC and enterprise-policy failure categories, and the unelevated fallback with weaker isolation.

  • Windows setup helper_failed despite an installed signed helper

    Public issue report · checked 2026-10-02

    Windows 11 report on build 26.818.8289.0: setup fails after UAC; package and helper signature checks alone do not verify setup.

  • Windows setup retry with no UAC prompt

    Public issue report · checked 2026-10-02

    Windows desktop build 26.803.10989.0 report distinguishes absent setup elevation from ordinary UAC working elsewhere. It does not establish a universal permissions repair.

How this page is checked
Evidence level
Reported - based on public reports, not reproduced here
Last reviewed
2026-10-02
Content updated
2026-10-03
Full version scope
Windows desktop reports include builds 26.803.10989.0 and 26.818.8289.0. Official sandbox guidance was reviewed separately; no fixed desktop build or universal repair is asserted.
Symptoms indexed
  • Windows setup returns the same failure on retry
  • No Windows administrator prompt appears
  • The setup helper exists but setup still fails with access denied

Reviewer note

Official sandbox documentation and issue bodies re-read on 2026-10-02. No setup error was reproduced locally; no ACL rewrite or security disablement is presented as a generic fix.

Last updated: