What version of the Codex App are you using (From “About Codex” dialog)?
Historical affected version: 26.707.9981.0 (package OpenAI.Codex_26.707.9981.0_x64__2p2nqsd0c76g0).
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
On the historical Windows build 26.707.9981.0, abnormally terminating the Codex/ChatGPT desktop app while a Codex task was active was followed by a persistent startup crash loop. Reopening the application repeatedly failed before the UI became usable, and recovery required a Microsoft Store update or package repair.
Windows Event Viewer recorded 85 matching Application Error events for the affected package:
Event ID: 1000
Faulting application: ChatGPT.exe
Faulting package: OpenAI.Codex_26.707.9981.0_x64__2p2nqsd0c76g0
Faulting module: unknown
Exception code: 0xc06d007f
Three matching events occurred on 15 July 2026 and 82 occurred on 16 July 2026. Windows Error Reporting used event name MoAppCrash, problem signature P8 c06d007f, and populated fault bucket 2155754486034767662.
A controlled regression test was later performed on current build 26.721.4979.0. All 12 ChatGPT.exe processes belonging to the exact installed OpenAI Codex package were force-terminated while a task was active. The first relaunch attempt produced a visible window, this task could be reopened, and no new matching Application Error or Windows Error Reporting event was created. The historical failure therefore did not reproduce on the current build.
What steps can reproduce the bug?
Historical sequence on affected build 26.707.9981.0:
- Open Codex Desktop on Windows.
- Start a local Codex task and wait until it is actively working.
- Force-terminate the Codex/ChatGPT desktop application.
- Launch Codex again.
- Observe that the application crashes or exits before becoming usable.
- Retry launching it and observe repeated Event ID
1000 entries with exception 0xc06d007f.
- Update or repair Codex through Microsoft Store.
- Observe that the application becomes launchable again.
Minimal PowerShell regression harness used for the current-build test:
# WARNING: Save all work first. This closes every ChatGPT.exe process
# belonging to the installed OpenAI Codex package.
$package = Get-AppxPackage -Name 'OpenAI.Codex'
$installRoot = [IO.Path]::GetFullPath($package.InstallLocation)
$targets = Get-Process -Name 'ChatGPT' -ErrorAction SilentlyContinue |
Where-Object {
try {
$_.Path -and
[IO.Path]::GetFullPath($_.Path).StartsWith(
$installRoot,
[StringComparison]::OrdinalIgnoreCase
)
} catch {
$false
}
}
$targets | Stop-Process -Force
Start-Sleep -Seconds 5
Start-Process -FilePath 'explorer.exe' `
-ArgumentList "shell:AppsFolder\$($package.PackageFamilyName)!App"Current-build validation result:
Tested build: 26.721.4979.0
Processes terminated: 12
Relaunch attempts required: 1
Visible window after relaunch: yes
New matching Application Error events: 0
New matching WER events: 0
Outcome: relaunch-visible; historical failure not reproduced
Session ID: unavailable for the historical 15–16 July incident. Token-limit and context-window usage are not applicable to this native startup failure.
What is the expected behavior?
After an abnormal process termination, Codex should start normally on the next launch. It should recover the previous task safely or abandon incomplete transient state without entering a persistent crash loop. Recovery should not require a Microsoft Store update, repair, or application reset.
Additional information
- Historical first matching crash:
2026-07-15 23:52:48 +08:00.
- Historical last matching crash:
2026-07-16 17:51:03 +08:00.
- Matching historical crash count:
85.
- Representative Windows report IDs:
d65d20f2-ccb6-4592-a926-c691e80ec370148ebb3c-47e2-4800-9675-2e5a4a7bd41b2390b7bb-52b7-496b-a89b-8b2be3b400d8
- A subsequent OpenAI Codex Store update succeeded on
2026-07-17 19:16:56 +08:00; the same crash signature did not recur afterward in the available Application log.
- The current Codex log database begins on 19 July, after the historical incident, and therefore cannot establish the initiating action.
- Historical WER records referenced dump files, but the referenced dump directories are no longer present.
- The exact native module/procedure could not be identified because the original dump is unavailable.
- The current result indicates a historical, likely fixed product bug. No attacker-controlled trigger, data exposure, privilege escalation, or current security impact has been demonstrated.
What version of the Codex App are you using (From “About Codex” dialog)?
Historical affected version:
26.707.9981.0(packageOpenAI.Codex_26.707.9981.0_x64__2p2nqsd0c76g0).What subscription do you have?
ChatGPT Plus
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
On the historical Windows build
26.707.9981.0, abnormally terminating the Codex/ChatGPT desktop app while a Codex task was active was followed by a persistent startup crash loop. Reopening the application repeatedly failed before the UI became usable, and recovery required a Microsoft Store update or package repair.Windows Event Viewer recorded 85 matching
Application Errorevents for the affected package:Three matching events occurred on 15 July 2026 and 82 occurred on 16 July 2026. Windows Error Reporting used event name
MoAppCrash, problem signature P8c06d007f, and populated fault bucket2155754486034767662.A controlled regression test was later performed on current build
26.721.4979.0. All 12ChatGPT.exeprocesses belonging to the exact installed OpenAI Codex package were force-terminated while a task was active. The first relaunch attempt produced a visible window, this task could be reopened, and no new matching Application Error or Windows Error Reporting event was created. The historical failure therefore did not reproduce on the current build.What steps can reproduce the bug?
Historical sequence on affected build
26.707.9981.0:1000entries with exception0xc06d007f.Minimal PowerShell regression harness used for the current-build test:
Current-build validation result:
Session ID: unavailable for the historical 15–16 July incident. Token-limit and context-window usage are not applicable to this native startup failure.
What is the expected behavior?
After an abnormal process termination, Codex should start normally on the next launch. It should recover the previous task safely or abandon incomplete transient state without entering a persistent crash loop. Recovery should not require a Microsoft Store update, repair, or application reset.
Additional information
2026-07-15 23:52:48 +08:00.2026-07-16 17:51:03 +08:00.85.d65d20f2-ccb6-4592-a926-c691e80ec370148ebb3c-47e2-4800-9675-2e5a4a7bd41b2390b7bb-52b7-496b-a89b-8b2be3b400d82026-07-17 19:16:56 +08:00; the same crash signature did not recur afterward in the available Application log.