38 people reported
All time, since Oct 9, including 12 thumbs-up on GitHub.
MXC launcher browser init failure
“MXC launcher: cannot locate required Windows platform directory: HRESULT 0x80070003”
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/11137/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
Browser control fails to initialize with MXC launcher HRESULT 0x80070003 on Windows. The node_repl kernel exits with code 1 when cua.getState() or cua.createBrowserTab() is called, before any browser state or tab is returned.
Is this your bug?
File my report- Where
- Browser control (CUA)
- Error text
MXC launcher: cannot locate required Windows platform directory: HRESULT 0x80070003- Versions
- 0.162.0 to 26.1007.71326
- Platforms
- macOS, Windows
- How bad
- Some reports say it blocks them completely.
Part of: Browser/Computer Use runtime won't start8 bugs
- Browser control fails at startup with sandbox-exec TIOCSTI error19 people
- MXC sandbox startup failure11 people
- Browser control fails with trusted Node process exiting on Windows5 people
- Computer use initialization fails3 people
- MXC launcher startup failure3 people
- Computer Use startup failure2 people
- Node REPL calls time out2 people
Not quite your bug?
- Sandbox setup refresh fails308 people
Original reports27, newest first
- ChatGPT Plus is unable to access AgentFire WordPress account when signed in with ChatGPT browser.On GitHub#54663
- Windows browser control fails before tab access: MXC launcher HRESULT 0x80070003On GitHub#54658
- Windows DOT fresh-task browser launch loses SystemDrive after update; local restricted browser worksOn GitHub#54477
- Windows: @Chrome fails with “MXC launcher: cannot locate required Windows platform directory” (HRESULT 0x80070003)On GitHub#54338
- Windows 26.1007.2314.0: CUA MXC known-folder failure and native Computer Use app-server not foundOn GitHub#54225
- Windows app 26.1007.9446.0: CUA MXC 0x80070003 persists; desktop applicability of #54027/#54069 and scoped diagnosticsOn GitHub#54157
- Windows Chrome control fails: MXC launcher cannot locate required Windows platform directory (0x80070003)On GitHub#54153
- Windows computer control fails to start: MXC launcher HRESULT 0x80070003On GitHub#54116
- [Windows] CUA initialization exits before inventory in ChatGPT 26.1007.9446.0On GitHub#54101
- Windows delegated CUA: MXC known-folder startup failure before Chrome inventoryOn GitHub#54085
Show all 27Show only the newest 10
- [Windows][Codex Desktop] Dot-Delegated CUA Fails with HRESULT 0x80070003 — Missing SystemDrive Environment VariableOn GitHub#53970
- Windows: PC and browser control unavailable in Work — MXC 0x80070003On GitHub#53941
- Windows Chrome control fails before tab inspection: required platform directory missing (0x80070003)On GitHub#53813
- Windows CUA initialization still fails with MXC HRESULT 0x80070003 after desktop app reinstallOn GitHub#53783
- Computer and Browser Connection Issues with DotOn GitHub#53735
- [Windows] Codex/Dot Computer Use Fails — MXC Launcher HRESULT 0x80070003, CUA Timeouts, Browser Control UnavailableOn GitHub#53694
- Windows: delegated browser runtime fails before tab inventory (MXC 0x80070003, then trusted Node exits)On GitHub#53564
- Windows browser-control runtime exits before inventory: MXC launcher HRESULT 0x80070003On GitHub#53518
- Windows Dot Computer Use fails with MXC HRESULT 0x80070003; local chat worksOn the forum#1405767
- [Windows] Work Mode browser CUA initialization still fails after app repair: MXC HRESULT 0x80070003On GitHub#53397
- MXC launcher: cannot locate required Windows platform directory: HRESULT 0x80070003.On GitHub#53356
- Windows 26.1007: native node_repl tools absent while browser CUA kernel fails in MXCOn GitHub#53255
- [Windows] Browser tools fail to initialize: MXC launcher HRESULT 0x80070003On GitHub#53188
- Windows 26.1007.21434: browser CUA launcher fails with HRESULT 0x80070003; desktop runtime not exposedOn GitHub#53130
- Computer Use fails on Windows — HRESULT 0x80070003On GitHub#52858
- Windows browser control fails with MXC platform directory HRESULT 0x80070003 on Desktop 26.1007.2314.0On GitHub#52857
- Windows Dots: CUA MXC launcher fails with HRESULT 0x80070003 after direct shell recoveryOn GitHub#52407