Rank, 14 days: 243 on the Codex sheet
12 people reported

All time, since Oct 4, including 10 thumbs-up on GitHub.

Sandbox fails on unreadable volume

“An unrelated encrypted/unreadable volume should not prevent sandboxed commands from running.”

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/13480/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

Sandbox fails on Windows when an unreadable volume exists. MXC launcher errors on volume enumeration of an unrelated VeraCrypt-encrypted or locked BitLocker drive before any command starts.

Is this your bug?

File my report
Where
MXC sandbox
Error text
MXC launcher: enumerate MXC volume F:\: The volume does not contain a recognized file system. (os error 1005)
Versions
0.160.0 to 26.1002.52244
Platforms
Windows
How bad
Breaks a normal workflow.

Not quite your bug?

  1. MXC volume enumeration failure3 people
  2. MXC startup fails with error 13266 people
  3. MXC launcher startup failure3 people

Original reports2, newest first

  1. Unrelated Veracrypt encrypted volumes or other unreadable volumes cause the sandbox to fail on volume enumerationOn GitHub#51686
  2. MXC fails before command launch when an unrelated BitLocker volume is lockedOn GitHub#50915

Do you work on Codex?

Claim its RAP Sheet to see what your users report and answer them in one place.