What version of the Codex App are you using (From “About Codex” dialog)?
26.1007.21434
What subscription do you have?
Pro
What platform is your computer?
Microsoft Windows NT 10.0.26300.0 x64
What issue are you seeing?
A connected multi-format USB card reader exposes five empty drive letters, F: through J:. With the reader attached, even a Get-Date command fails before PowerShell executes. The working directory is unrelated to those drives.
Exact error, exit code 1:
MXC launcher: enumerate MXC volume F:: A device which does not exist was specified. (os error 433): A device which does not exist was specified. (os error 433)
This sequence has reproduced repeatedly. A fresh task also failed, naming G: instead of F:. Updating and restarting the desktop app did not fix it. Enabling Explorer’s “Hide empty drives” option did not fix it either.
What steps can reproduce the bug?
- Connect the reader with all slots empty.
- Ask Codex to run Get-Date.
- Command startup fails with the error above.
- Disconnect the reader so its drive letters disappear.
- Retry Get-Date; it succeeds.
What is the expected behavior?
Empty removable slots should not prevent commands in an accessible workspace from starting.
Additional information
Environment collected:
- Windows Professional, x64; display version 26H2, build 26300.9550
- PowerShell 7.6.6
- Desktop release identifier in logs: 26.1007.21434
- App-server version reported in logs: 0.162.0-alpha.17.2
Reader:
unbranded multi-format USB card reader; USBView reports VID 0x05E3 (Genesys Logic, Inc.), PID 0x0748. Five empty slots appear as F:–J:.
Source-level lead:
At upstream commit cc7ba33, Codex enumerates drive roots and builds the filesystem policy before calling the native MXC launcher. Its inaccessible_volume() handling omits Windows error 433. This appears to let an unavailable card-reader slot abort policy construction. This is an inspection of current upstream source, not a trace of the installed binary.
Relevant source: volume enumeration and error handling.
A possible regression test would cover io::Error::from_raw_os_error(433), while preserving appropriate failures for explicitly requested inaccessible paths.
What version of the Codex App are you using (From “About Codex” dialog)?
26.1007.21434
What subscription do you have?
Pro
What platform is your computer?
Microsoft Windows NT 10.0.26300.0 x64
What issue are you seeing?
A connected multi-format USB card reader exposes five empty drive letters, F: through J:. With the reader attached, even a Get-Date command fails before PowerShell executes. The working directory is unrelated to those drives.
Exact error, exit code 1:
MXC launcher: enumerate MXC volume F:: A device which does not exist was specified. (os error 433): A device which does not exist was specified. (os error 433)
This sequence has reproduced repeatedly. A fresh task also failed, naming G: instead of F:. Updating and restarting the desktop app did not fix it. Enabling Explorer’s “Hide empty drives” option did not fix it either.
What steps can reproduce the bug?
What is the expected behavior?
Empty removable slots should not prevent commands in an accessible workspace from starting.
Additional information
Environment collected:
Reader:
unbranded multi-format USB card reader; USBView reports VID 0x05E3 (Genesys Logic, Inc.), PID 0x0748. Five empty slots appear as F:–J:.
Source-level lead:
At upstream commit cc7ba33, Codex enumerates drive roots and builds the filesystem policy before calling the native MXC launcher. Its inaccessible_volume() handling omits Windows error 433. This appears to let an unavailable card-reader slot abort policy construction. This is an inspection of current upstream source, not a trace of the installed binary.
Relevant source: volume enumeration and error handling.
A possible regression test would cover io::Error::from_raw_os_error(433), while preserving appropriate failures for explicitly requested inaccessible paths.