ChatGPT or Codex Browser Crashes on Windows? Recover Safely

If the ChatGPT or Codex Windows app closes when the built-in Browser opens, then Windows says "This app can't open" or reports Modified, NeedsRemediation, stop reopening the affected chat. Use Chrome, the Codex IDE extension, or the Codex CLI for web work, repair the Microsoft Store app to recover it, and leave the built-in Browser disabled until a newer build is confirmed to fix the incident.

Do not disable the GPU sandbox, turn off Windows Code Integrity, replace vk_swiftshader.dll, download an unofficial older package, or reset the app as a first step. Those options weaken security or can erase local app data without fixing the packaged component.

Confirm You Have This Specific Crash

The July 2026 reports share a narrow signature:

• Windows 11 with the Microsoft Store OpenAI.Codex package;

• ChatGPT or Codex closes as the built-in Browser navigates or restores a browser-backed chat;

• relaunching shows "This app can't open," error 0x3CFC, or a Store Repair or Restore prompt;

• Get-AppxPackage reports Modified, NeedsRemediation;

• Windows Code Integrity Event 3033 names ChatGPT.exe and vk_swiftshader.dll;

• affected reports commonly name app build 26.721.4979.0, although related browser failures were reported on earlier builds.

This guide is not for a generic renderer crash, an ARM64 serialport.node crash, a stalled shell, or a website that fails to load while the desktop app stays open. Match the package status and Event 3033 before assuming SwiftShader is involved.

Prerequisites

Before changing the app:

1. Save or commit repository work from a separate terminal.

2. Close every ChatGPT and Codex window.

3. Record the app version, Windows version, and affected chat.

4. Keep %USERPROFILE%\.codex intact. Do not delete it as a troubleshooting shortcut.

5. Have the Codex CLI, IDE extension, or an ordinary browser available as a temporary path.

The app package and your repositories are separate. Repairing the app should not replace repository files, but an interrupted agent may have left uncommitted changes. Check those changes before continuing.

Step 1: Check the Package Status

Open PowerShell and run:

$codexPackage = Get-AppxPackage OpenAI.Codex
$codexPackage | Select-Object Name, Version, Status, InstallLocation

On a healthy installation, Status should be Ok. The incident reports often show:

Modified, NeedsRemediation

If no package is returned, confirm that you installed the official Microsoft Store app and that PowerShell is running as the same Windows user who installed it.

Step 2: Check Code Integrity Event 3033

Use this read-only query for the last 24 hours:

Get-WinEvent -FilterHashtable @{
  LogName = 'Microsoft-Windows-CodeIntegrity/Operational'
  Id = 3033
  StartTime = (Get-Date).AddDays(-1)
} |
  Where-Object { $_.Message -match 'ChatGPT\.exe|vk_swiftshader\.dll' } |
  Select-Object -First 10 TimeCreated, Id, Message

The relevant event says ChatGPT.exe attempted to load vk_swiftshader.dll and that the file did not meet the required Microsoft signing level. Multiple independent reports correlated that event with a Chromium GPU-process exit and the package moving into remediation.

That correlation is strong, but it is not an official OpenAI root-cause statement. Do not generalize it to every Windows crash.

Step 3: Switch Browser Work to a Safe Path

Do not reopen the browser-backed chat just to reproduce the failure. Choose one of these paths instead:

• Use the Codex Chrome extension when the task needs your existing signed-in Chrome session.

• Use the Codex IDE extension or CLI for repository work and ordinary web search.

• Open public sources yourself in an external browser.

• Use a connected, read-only integration Action instead of browser automation when an API can answer the task.

OpenAI documents Chrome as the path for tasks that need your Chrome profile, cookies, open tabs, or extensions. It also keeps the affected built-in Chromium path out of the immediate recovery loop.

Step 4: Repair the Microsoft Store App

In Windows 11:

1. Open Settings.

2. Select Apps, then Installed apps.

3. Find ChatGPT or Codex.

4. Open the three-dot menu and select Advanced options.

5. Select Repair.

Microsoft says Repair reloads an MSIX app while retaining its data. Reset is different: it permanently deletes the app's data and reinstalls the app. Use Repair first.

After Repair finishes, run the status command again:

(Get-AppxPackage OpenAI.Codex).Status

Expected result:

Ok

If Repair is unavailable or the status does not return to Ok, use the official Microsoft Store update or reinstall flow. Preserve repository work and %USERPROFILE%\.codex before any destructive recovery step.

Step 5: Avoid the Trigger Until a Fixed Build Arrives

Repair restores the package, but reports on 26.721.4979.0 show the crash can return when the built-in Browser runs again. Repair is recovery, not proof that the browser defect is fixed.

For the affected build:

• start a fresh non-browser chat if the app opens;

• do not restore the browser tab or affected chat;

• keep browser tasks in Chrome, the IDE extension, the CLI, or an integration Action;

• install only official Microsoft Store updates;

• monitor the linked upstream issues for a confirmed fixed build.

One GitHub report demonstrated that launching with --disable-gpu-sandbox avoided the crash. The reporter also correctly described that as a reduced-isolation diagnostic, not an acceptable permanent fix. This guide does not recommend it.

Step 6: Verify the Recovery Without Retesting the Bug

On the affected build, verify only that:

1. package status is Ok;

2. ChatGPT or Codex opens;

3. a fresh non-browser chat works;

4. your repository and local Codex data are still present;

5. external Chrome, IDE, CLI, or integration work succeeds.

Do not use the built-in Browser as the recovery test. After OpenAI or the Microsoft Store provides a newer build with a confirmed fix, test from a fresh chat against a harmless public page such as https://example.com. Success means the page loads, the app stays open, package status remains Ok, and no new matching Event 3033 appears.

Keep Web Research Moving With Aident Loadout

Aident Loadout can give an agent read-only web search Actions through Aident Vault, so you do not need to paste a provider key into the prompt or depend on the broken in-app Browser.

Install or refresh the Aident skill:

Follow https://aident.ai/SETUP.md

Then verify authentication and connections from a trusted shell:

aident account auth status
aident vault vault --action status

Search for a read-only web Action:

aident capabilities search \
  --queries '["search the public web with read-only results"]' \
  --types '["action"]'

Inspect the current schema before execution, keep the query bounded, and reject any unexpected write-capable result. Measure success as one public query returned, zero provider credentials copied into chat, zero repository changes, and no built-in Browser launch.

Common Failure Modes

Why This Recovery Path Works

The built-in Browser uses a Chromium GPU child process inside the desktop app. In the reported incident, Windows Code Integrity rejected the packaged SwiftShader library, the GPU process exited, and the MSIX package entered a state that prevented relaunch.

Repair reloads the official package while retaining app data. Moving browser work to Chrome, the IDE, the CLI, or an integration Action avoids the failing embedded path. Neither step changes the packaged library, so a permanent correction still has to arrive through an official app update.

The practical lesson matches the traffic pattern of Aident's Ollama networking guide: start with the exact error, give a safe diagnostic, show the expected result, and explain why the workaround is temporary. That is more useful than a generic "reinstall the app" answer.

For related Windows failures, see How to Fix Codex Windows Sandbox Errors Safely. For repository recovery before changing agent settings, see How to Prevent Codex from Deleting Files.

Sources

• Using the built-in browser in the ChatGPT desktop app, OpenAI, updated July 2026

• ChatGPT Chrome extension guide, OpenAI, accessed July 28, 2026

• Reset or Repair MSIX apps, Microsoft, accessed July 28, 2026

• Embedded browser GPU process crash and blocked SwiftShader, OpenAI Codex issue, opened July 25, 2026

• Code Integrity 3033, package remediation, and relaunch failure, OpenAI Codex issue, opened July 27, 2026

• Windows desktop GPU process exits when loading SwiftShader, OpenAI Codex issue, opened July 27, 2026

• Windows x64 in-app Browser crash report, OpenAI Developer Community, posted July 25, 2026

• Codex crashes when the Browser opens and Store Restore repeats, r/codex, posted July 22, 2026

• Aident setup instructions, accessed July 28, 2026