6 people reported

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

MXC startup fails with error 1326

“My Windows computer appears connected and authorized in the ChatGPT desktop app, but local command execution and screen inspection cannot start.”

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

Local sandbox commands fail at MXC startup with error 1326. MXC launcher tries to "enumerate MXC volume" on an inaccessible mapped network drive; persists after Windows app Repair.

Is this your bug?

File my report
Where
Windows MXC launcher
Error text
MXC launcher: enumerate MXC volume Z:\: The user name or password is incorrect. (os error 1326): The user name or password is incorrect. (os error 1326)
Versions
0.162.0-alpha.2 to 26.1007.2314.0
Platforms
Windows
How bad
Breaks a normal workflow.

Not quite your bug?

  1. MXC launcher startup failure3 people
  2. Sandbox setup refresh fails308 people
  3. MXC sandbox startup failure11 people

Original reports2, newest first

  1. Windows local computer tools fail before startup with MXC error 1326, including after RepairOn GitHub#53361
  2. Windows MXC: unrelated inaccessible mapped drive blocks all sandbox command startup (error 1326)On GitHub#52908

Do you work on Codex?

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