This was the codex output when I told it the issue:
I found the cause. You do not need to try again.
Codex version `26.707.9981.0` contains an incompatible native `serialport.node` module. When browser content opens, it requests the Node function `napi_module_register` from `ChatGPT.exe`, but that function is actually exported by Codex’s `chrome.dll`. Windows raises `0xc06d007f` / error 127 (“procedure not found”), preventing the browser content from loading.
This explains why both websites and local HTML fail—the content is irrelevant. It is not a network, HTML, or graphics-driver issue.
The evidence points to an update regression:
* Current build installed July 14: `26.707.9981.0`
* 118 identical crashes recorded for that build
* No matching crashes from the previous installed build
* The crash dump identifies `@serialport/bindings-cpp` and `napi_module_register` precisely
For now, use an external browser for websites and generated HTML. Reinstalling the same Codex version is unlikely to help; this needs a corrected Codex package. I did not modify the app or your system.
I installed a reversible workaround without modifying the signed Codex app. The crash is caused by a faulty optional Codex Micro hardware component in version `26.707.9981.0`.
Please fully quit Codex, reopen it normally, return to this task, and try opening a webpage or local HTML again. That restart is required before I can confirm the fix.
If it still crashes, reopen Codex and tell me. The workaround can be safely removed using the included [instructions](C:/Users/---/Documents/Codex/2026-07-15/can/outputs/codex-browser-workaround/README.md).
You are welcome to discuss Codex issues on the forum, however the official place to report and track them is the GitHub issue tracker for OpenAI Codex.
Not sure if you are seeking help, reporting useful information or other.
So, I had ChatGPT look for the closest related issue and it identified:
If that issue matches your problem, consider adding a reaction on the GitHub issue page itself, not just on the forum topic, as reactions on GitHub help the developers gauge impact and prioritize work.
If it is not the same issue, try searching the existing GitHub issues for a closer match. If you cannot find one, then open a new issue with as much detail as possible.
The reply is based on a template I use for posts like this that others may also find helpful, so some of the wording is intentionally general.
reaction on the GitHub issue page itself, not just on the forum topic, as reactions on GitHub help the developers gauge impact and prioritize work.