[SOLVED]: Windows: Browser control repeatedly crashes with “trusted Node process exited unexpectedly” after update

UPDATE: I HAVE SOLVED THIS ISSUE ON MY PC, REFER TO THE MARKED SOLUTION BELOW. HAPPY CODING :face_blowing_a_kiss:

Exact issue details for “trusted Node process exited unexpectedly“ after latest update.

Surface: Windows desktop app

Browser or app version: Codex 26.1002.52244, build 13536, production channel. Update check reports up to date.

Affected feature and model, if relevant: Browser control and default terminal execution. Model not confirmed.

Bug

Browser control crashes before connecting to the browser, although the browser and extension are open and active. It previously worked. The failure appeared after an update, but the cause is not confirmed.

Expected

The agent connects to the browser and continues authorised work.

Reproduction

Open the Windows desktop app with the browser and extension active.

Ask the agent to inspect the open browser tabs.

Browser control fails immediately.

Reset the tool session and retry. The same failure occurs.

Minimal prompt: “Check my open browser tabs.”

Diagnostics

Exact browser-control error: trusted Node process exited unexpectedly; kernel reset, rerun your request

Default terminal execution also fails: Failed to create unified exec process: helper_unknown_error: setup refresh had errors

An approved elevated terminal command succeeds, but browser control remains unavailable.

When it happened

Reproduced on 8 October 2026, Australia/Sydney timezone (AEDT, UTC+11). Exact time not recorded.

How often

Every browser-control attempt during troubleshooting, including after tool-session resets. Earlier PC and helper-process restarts did not resolve the issue.

Tried installing Chrome to see if issue is rectified as a last resort (I hate Chrome). Same issue persists. Hopefully an update will be released to fix it. Been looking for a way to downgrade my app version so I can get back to work instead of wasting usage on issue diagnosis..

Same here, also on Windows. Started after this morning’s update — browser control was working fine before that. Getting the exact same errors: “trusted Node process exited unexpectedly; kernel reset” and “helper_unknown_error: setup refresh had errors”. Tried restart, clean reinstall — none of it helped. Looks like a bug in the update itself. Following this thread for a fix.

I’m pleased to share a workaround that restored browser access on my PC.

After reviewing the below, you may feed it to your Codex agent to get the necessary links and confirm with it that it is all official.

I personally backed up the 2 folders as my agent recommened all though I DID NOT lose any data, chats, or progress, nor did I have to replace those files after the downgrade.

HAPPY CODING :face_blowing_a_kiss:

  • UPDATE:

Rolling back the Windows desktop app worked for me.

Before rollback, browser tools repeatedly failed with:
“trusted Node process exited unexpectedly; kernel reset, rerun your request”

After rollback, Codex successfully connected to Brave and read my signed-in website. This confirms browser connection and page reading on my machine, not every feature or everyone’s setup.

Version: 26.930.3930.0 (Windows x64).
Reported as available on 3 October 2026. That date comes from a community report, not a verified official release date.

  • FINDING THE INSTALLER:

This forum does not allow me to include links. Ask your Codex agent:

“Find the official Windows x64 ChatGPT/Codex desktop installer for version 26.930.3930.0. Check the OpenAI Codex repository on GitHub, issue #51601, comment 6055892735. Retrieve the OpenAI-hosted installer referenced there. Before installation, verify its Windows digital signature, package version and publisher against my installed app. Do not use a third-party mirror, substitute a CLI downgrade, or change sandbox permissions. Download and verify first; do not close the app or install until I am ready.”

  • VERIFICATION PERFORMED:

• Downloaded from the same OpenAI download host linked by OpenAI’s Windows deployment documentation.
• Windows reported “Signature verified.”
• Package publisher matched my installed app.
• Package identity was OpenAI.Codex, version 26.930.3930.0, x64.

  • INSTRUCTIONS:

  1. Finish or stop active agent work. Save unsent messages and unsaved editor changes.
    ENSURE YOU FULLY QUIT ChatGPT/Codex, INCLUDING ITS SYSTEM TRAY ICON.

  2. Back up these folders to a private local location before downgrading:

%USERPROFILE%\.codex
%LOCALAPPDATA%\Packages\OpenAI.Codex_2p2nqsd0c76g0

These backups can contain credentials and private data. Do not upload or share them.

  1. Download and verify the installer. The commands below assume it is saved in your Downloads folder as ChatGPT-x64.msix. Adjust the path if necessary.

  2. CLOSE ALL INSTANCES OF CHATGPT/CODEX BEFORE INSTALLATION.

  3. Open Windows PowerShell from Start, not PowerShell 7. Run:

Add-AppxPackage -Path "$env:USERPROFILE\Downloads\ChatGPT-x64.msix" -ForceUpdateFromAnyVersion
  1. If you get error 0x80073D02 saying OpenAI.Codex is still in use, a background process is preventing installation. Once no agent is actively working, run:
Add-AppxPackage -Path "$env:USERPROFILE\Downloads\ChatGPT-x64.msix" -ForceUpdateFromAnyVersion -ForceTargetApplicationShutdown

This closes the target app and interrupts active work. Run it in a separate Windows PowerShell window, not inside Codex.

  1. After installation, check the installed package:
Get-AppxPackage OpenAI.Codex | Select-Object Name, Version

Expected version: 26.930.3930.0

  1. Reopen the app and ask it to test browser control. Avoid manually updating again before testing. An automatic update could put you back on a newer version.

Do not uninstall or reset the app, delete its data, disable security software, or change sandbox permissions for this procedure.

  • OPTIONAL DOWNLOAD VERIFICATION :

(I DIDNT PERFORM THIS PERSONALLY)

Run:

Get-FileHash "$env:USERPROFILE\Downloads\ChatGPT-x64.msix" -Algorithm SHA256

SHA256 of the exact installer we verified:

F7B0266D6C00D4743DA01D62BC82488F7EC5560C642501758119CB9885F67C87

If yours differs, stop and investigate before installation. A matching hash confirms identical file contents. The digital signature must also be verified.

  • IMPORTANT:

This is a temporary workaround, not an official guaranteed fix. The installer is signed, but compatibility with newer local app data and continued service support are not guaranteed. Older versions may lack later security fixes. Keep your backups.

References you or your agent can search for:

• OpenAI documentation: “Deploy the Windows app”

• OpenAI Codex GitHub issue #51601, comment 6055892735

• Microsoft Learn: “Add-AppxPackage”, particularly ForceUpdateFromAnyVersion and ForceTargetApplicationShutdown