2 people reported
All time, since Oct 11.
D: drive missing in local tasks
“In a local Codex task on Windows, the execution environment does not expose the D: drive at all.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/codex/issues/11554/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
D: drive not visible in Windows local Codex tasks. The task environment only sees the C: workspace while D: stays available in Windows outside the task; restarting does not restore it.
Is this your bug?
File my report- Where
- Windows desktop app
- Error text
Cannot find drive. A drive with the name 'D' does not exist.- Versions
- 26.1007.21434 to 26.1011.11113
- Platforms
- Windows
- How bad
- Breaks a normal workflow.
Not quite your bug?
- Local commands hang on Windows3 people