Forumics logo Forumics
Issue 01

Back to issue

All Codex known issues

CLAIM C052 Supported 2026-11-07

GitHub issue #50915 in openai/codex, opened 2026-10-04 by Kizron, records a report that on Windows 11 build 26200 with Codex Desktop 26.930.3930.0 and bundled codex-cli 0.160.0, the MXC sandbox fails before launching any child process when an unrelated BitLocker data volume is present but locked, that the workspace is on another drive and does not reference the locked volume, and that MXC exits with a locked-volume enumeration error before the command starts.

Verbatim Excerpts from Cited Records
“On Windows, Codex's MXC sandbox fails before launching any child process when an unrelated BitLocker data volume is present but locked.”
— Kizron · openai/codex (issue 50915 opening body, Summary section) · 2026-10-04T17:04:06Z ·GitHub Issue ↗
“The project/workspace is on another drive and does not reference the locked volume.”
— Kizron · openai/codex (issue 50915 opening body, Summary section) · 2026-10-04T17:04:06Z ·GitHub Issue ↗
“MXC launcher: enumerate MXC volume E:\: This drive is locked by BitLocker Drive Encryption. You must unlock this drive from Control Panel. (os error -2144272384)”
— Kizron · openai/codex (issue 50915 opening body, Reproduction section) · 2026-10-04T17:04:06Z ·GitHub Issue ↗
“An unrelated locked BitLocker volume should be treated like another unavailable logical volume during generated volume-root expansion and should not prevent commands scoped to accessible volumes from launching.”
— Kizron · openai/codex (issue 50915 opening body, Expected behavior section) · 2026-10-04T17:04:06Z ·GitHub Issue ↗
Counter-record: Issue remains open with 30 comments as of 2026-11-05; no maintainer comment appears in the surveyed thread. Commenters reproduced the failure across many Windows builds through 2026-11-05, including VeraCrypt volumes, an optical-drive case with a different Windows error, and cases where the MXC failure also blocked browser and computer-use runtimes. Reported workarounds include a named permission profile without the root grant, switching to the legacy sandbox backend, switching the agent environment to WSL2, and unlocking the unrelated drive, which restores launch. A community member posted a minimal patch on 2026-10-22 classifying the locked-volume error as an inaccessible volume; it is a community proposal, not a maintainer fix. The claim documents only the original report, not a verified current state. Falsification probe: If issue 50915 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn. Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by scripts/verify_claim_verbatim.py.

See also: Codex vs Cursor head-to-head comparison on 9bests