Severe impact on my work, planned leave, expenses, and paid usage allowance
I am a paying ChatGPT Pro subscriber on the 20x Codex plan, using it for intensive work across multiple concurrent tasks.
I am extremely angry about this incident and the lack of a meaningful explanation while serious disruption continues. This is the most severe failure I have experienced using ChatGPT/Codex. The consequences extend far beyond a slow interface.
Time set aside for important work has been consumed by the failure
I had arranged time off work in advance so that I could concentrate on very important work over September 26–29, combining the weekend with Monday and Tuesday. I did not take leave in order to troubleshoot this app. After the update late on Saturday, the failures disrupted the work I had planned for Sunday and Monday. Tuesday was also part of the planned work period; I am not claiming that future time has already been lost.
Over roughly a day and a half of troubleshooting, I have spent substantial time and effort investigating, waiting for the interface to recover, repeating explanations, re-entering lost text and voice input, and redoing work. This has also affected my sleep. These were hours I had deliberately reserved to make progress on important tasks.
Actual additional expenditure: JPY 34,320 including tax
During Codex-assisted troubleshooting, the investigation focused on PC hardware before matching reports of problems with this app version were identified. I ordered a 32 GB RAM upgrade for JPY 34,320 including tax. That is an actual additional purchase made in the course of dealing with this incident. RAM shortage has not been established as the cause, and the upgrade has not been shown to resolve these failures.
The purchase amount does not measure the total impact on my time, leave, sleep, effort, or paid usage allowance. My compensation request is for additional usage allowance / a banked Full reset credit; I am not asking for reimbursement of the RAM purchase. Order identifiers, payment details, and the receipt are kept private.
A Full reset was used, but troubleshooting and repeated work consumed the allowance
I use the Pro 20x plan and have actually used a banked Full reset. The UI failures continued afterward. Restoring the allowance did not restore my ability to work normally: substantial allowance has gone into investigating the failure and repeating work.
I run multiple tasks using Astra. The failure also prevents me from supervising and correcting those tasks at the right time:
- I need to open a conversation to check progress or correct the direction of a task.
- The interface freezes, will not switch conversations, or will not accept input.
- Work continues while I cannot intervene, sometimes in a direction I did not intend.
- By the time I can give instructions, substantial work has already been done and has to be sent back and repeated.
- Both the initial work and the rework consume time and paid usage allowance.
Background agents continuing to run does not mean that I can work normally. Being unable to supervise them creates additional rework and consumption, beyond the time spent waiting for the UI. I have not calculated an exact token count, number of repeated runs, or monetary value for this additional consumption. I ask Support to examine whatever reset and usage records can be correlated with this incident.
Why I am angry, and what I need OpenAI to do
I am losing time reserved for important work, sleep, effort, money spent on hardware, and paid usage allowance. The continuing lack of an adequate explanation compounds the disruption and damages my trust. From an affected user's perspective, a severe recurring failure without clear public acknowledgment feels like the problem is being concealed. That describes my experience of the lack of transparency.
Please provide a clear acknowledgment of this Windows app problem, the known affected versions and scope, progress on the investigation and fix, and a safe workaround that preserves existing conversations, projects, and running work. I also request a substantive explanation and apology, and a concrete decision on additional usage allowance / Full reset compensation for the loss of usable service and additional consumption. A reset credit granted before this incident must not be presented as new compensation for it.
I am publishing this experience from Japan so that other users can understand the practical consequences and avoid spending the same time and money. The technical evidence below accompanies this report of harm to my work and daily life.
Version and system
- Microsoft Store package: OpenAI.Codex_26.924.2738.0_x64__2p2nqsd0c76g0.
- App update checker: 26.924.22138, build 11645, production channel, up_to_date. Previous installed package: 26.908.9136.0.
- Windows 11 Pro 25H2, build 26200.9457, x64.
- HP Pavilion Gaming Desktop TG01 series; AMD Ryzen 5 3500 (6 cores / 6 threads); 16 GB DDR4-3200 (2 x 8 GB); NVIDIA GeForce RTX 3060 with 12 GB VRAM; 256 GB Samsung NVMe system SSD with approximately 57 GB free at inspection.
- Model is not established as a trigger: symptoms occur while typing, scrolling, or switching tasks without submitting a prompt.
What happened
I had not experienced these symptoms before updating the Windows desktop app. Windows AppXDeploymentServer events 855 and 400 show the update from 26.908.9136.0 to 26.924.2738.0 completing at 2026-09-26 22:53:47 JST. The first retained Crashpad sidecar for a renderer crash was modified at 23:07:08 JST, 13 minutes 21 seconds later.
Since then, the desktop UI repeatedly turns white and reloads to Home. Unsent typed text or voice dictation can be lost. Switching Codex tasks, scrolling a conversation, typing one romanized-Japanese keystroke, or deleting one character with Backspace can stall noticeably. Some stalls last tens of seconds or several minutes; a few required force-quitting after waiting over five minutes. During severe episodes, even the desktop mouse pointer becomes hard to move. The problem also occurs without voice input or sending a prompt.
Expected: the desktop UI remains responsive and preserves the current task and unsent draft during normal navigation and input.
Retained crash records
Crashpad sidecar metadata, counted as of 2026-09-28 18:07 JST:
| Date (JST) |
renderer crashes |
browser-process crashes |
| Sep 26 |
2 |
0 |
| Sep 27 |
24 |
0 |
| Sep 28 |
101 |
1 |
| Total |
127 |
1 |
These are retained capture_kind=crash metadata records, not a count of every white screen or stall. Sidecar filesystem modification times are not native stack timestamps. The inspected Crashpad reports directory retained sidecars but no usable native dump or stack. Windows also recorded Codex MoAppHang / Application Hang events on Sep 27 around 01:16, 02:23, and 21:44 JST.
Reproduction and checks
This recurs during ordinary use, but I cannot provide one deterministic click sequence. It happens when moving between tasks, scrolling, and typing in the composer; it has also happened without voice input or submitting any message. Please do not treat task switching as a proven root cause.
- Fully exiting and restarting the app helped only temporarily; failures recurred.
- Collapsing the sidebar did not improve input lag.
- Avast once used substantial CPU and was later uninstalled. Microsoft Defender is active, and Codex crashes continued.
- At sampled times, Windows still reported about 3.7–5.3 GB of available physical memory. These samples were not synchronized to every crash and cannot exclude brief resource spikes. GPU VRAM and SSD activity were not saturated in short observations.
- codex doctor found core installation, app-server connection, HTTP/WebSocket reachability, and inspected SQLite integrity healthy. It reported some history-index warnings, but their relationship to these crashes is unknown.
- No decisive matching GPU reset, disk fault, WHEA hardware error, or Windows-wide memory exhaustion event was found in the inspected System log interval. This does not rule out every local factor.
- A performance trace was captured during a period when the severe freeze did not reproduce; it does not identify the cause.
- No cache/history reset, reinstall, GPU-mode change, WSL switch, or controlled downgrade was performed, to avoid disturbing active work without a causal basis.
Related reports
My corresponding Developer Community report, now approved and published, includes the same user-impact statement: https://community.openai.com/t/windows-26-924-2738-0-repeated-renderer-crashes-white-screen-reloads-and-severe-input-lag-after-update/1401563/2
Other users report problems on the same package or app build, including different Windows hardware. These strengthen the update-regression hypothesis, but may represent different failure paths:
Request and existing private support case
Please investigate the renderer crashes and UI performance regression in 26.924.2738.0 / app build 26.924.22138 (11645), and provide the response requested above. Please also advise how to collect a useful native crash dump or stack privately. If a fix is available or planned, please identify its version and release status.
I escalated a private OpenAI Support conversation on September 28 at about 14:29 JST. At the 18:14 JST check, I had not received a human reply, and I could not find an acknowledgment of this Windows desktop rendering issue on the public status page. These are the times of those observations.
This issue URL and the same correlation code have already been sent directly into my authenticated, existing Support conversation. The code was also sent to [email protected] from the same account. The public reporter and the person raising that existing Support case are the same person. Please connect this report and the user-impact details with that case and share them with the engineering and usage-compensation teams.
Public correlation code: CDX-20260928-8C64E22E07.
No personal name, email address, employer, account or conversation ID, user path, project contents, order identifiers, payment credentials, or unreviewed raw logs are included in this public report.
Severe impact on my work, planned leave, expenses, and paid usage allowance
I am a paying ChatGPT Pro subscriber on the 20x Codex plan, using it for intensive work across multiple concurrent tasks.
I am extremely angry about this incident and the lack of a meaningful explanation while serious disruption continues. This is the most severe failure I have experienced using ChatGPT/Codex. The consequences extend far beyond a slow interface.
Time set aside for important work has been consumed by the failure
I had arranged time off work in advance so that I could concentrate on very important work over September 26–29, combining the weekend with Monday and Tuesday. I did not take leave in order to troubleshoot this app. After the update late on Saturday, the failures disrupted the work I had planned for Sunday and Monday. Tuesday was also part of the planned work period; I am not claiming that future time has already been lost.
Over roughly a day and a half of troubleshooting, I have spent substantial time and effort investigating, waiting for the interface to recover, repeating explanations, re-entering lost text and voice input, and redoing work. This has also affected my sleep. These were hours I had deliberately reserved to make progress on important tasks.
Actual additional expenditure: JPY 34,320 including tax
During Codex-assisted troubleshooting, the investigation focused on PC hardware before matching reports of problems with this app version were identified. I ordered a 32 GB RAM upgrade for JPY 34,320 including tax. That is an actual additional purchase made in the course of dealing with this incident. RAM shortage has not been established as the cause, and the upgrade has not been shown to resolve these failures.
The purchase amount does not measure the total impact on my time, leave, sleep, effort, or paid usage allowance. My compensation request is for additional usage allowance / a banked Full reset credit; I am not asking for reimbursement of the RAM purchase. Order identifiers, payment details, and the receipt are kept private.
A Full reset was used, but troubleshooting and repeated work consumed the allowance
I use the Pro 20x plan and have actually used a banked Full reset. The UI failures continued afterward. Restoring the allowance did not restore my ability to work normally: substantial allowance has gone into investigating the failure and repeating work.
I run multiple tasks using Astra. The failure also prevents me from supervising and correcting those tasks at the right time:
Background agents continuing to run does not mean that I can work normally. Being unable to supervise them creates additional rework and consumption, beyond the time spent waiting for the UI. I have not calculated an exact token count, number of repeated runs, or monetary value for this additional consumption. I ask Support to examine whatever reset and usage records can be correlated with this incident.
Why I am angry, and what I need OpenAI to do
I am losing time reserved for important work, sleep, effort, money spent on hardware, and paid usage allowance. The continuing lack of an adequate explanation compounds the disruption and damages my trust. From an affected user's perspective, a severe recurring failure without clear public acknowledgment feels like the problem is being concealed. That describes my experience of the lack of transparency.
Please provide a clear acknowledgment of this Windows app problem, the known affected versions and scope, progress on the investigation and fix, and a safe workaround that preserves existing conversations, projects, and running work. I also request a substantive explanation and apology, and a concrete decision on additional usage allowance / Full reset compensation for the loss of usable service and additional consumption. A reset credit granted before this incident must not be presented as new compensation for it.
I am publishing this experience from Japan so that other users can understand the practical consequences and avoid spending the same time and money. The technical evidence below accompanies this report of harm to my work and daily life.
Version and system
What happened
I had not experienced these symptoms before updating the Windows desktop app. Windows AppXDeploymentServer events 855 and 400 show the update from 26.908.9136.0 to 26.924.2738.0 completing at 2026-09-26 22:53:47 JST. The first retained Crashpad sidecar for a renderer crash was modified at 23:07:08 JST, 13 minutes 21 seconds later.
Since then, the desktop UI repeatedly turns white and reloads to Home. Unsent typed text or voice dictation can be lost. Switching Codex tasks, scrolling a conversation, typing one romanized-Japanese keystroke, or deleting one character with Backspace can stall noticeably. Some stalls last tens of seconds or several minutes; a few required force-quitting after waiting over five minutes. During severe episodes, even the desktop mouse pointer becomes hard to move. The problem also occurs without voice input or sending a prompt.
Expected: the desktop UI remains responsive and preserves the current task and unsent draft during normal navigation and input.
Retained crash records
Crashpad sidecar metadata, counted as of 2026-09-28 18:07 JST:
These are retained capture_kind=crash metadata records, not a count of every white screen or stall. Sidecar filesystem modification times are not native stack timestamps. The inspected Crashpad reports directory retained sidecars but no usable native dump or stack. Windows also recorded Codex MoAppHang / Application Hang events on Sep 27 around 01:16, 02:23, and 21:44 JST.
Reproduction and checks
This recurs during ordinary use, but I cannot provide one deterministic click sequence. It happens when moving between tasks, scrolling, and typing in the composer; it has also happened without voice input or submitting any message. Please do not treat task switching as a proven root cause.
Related reports
My corresponding Developer Community report, now approved and published, includes the same user-impact statement: https://community.openai.com/t/windows-26-924-2738-0-repeated-renderer-crashes-white-screen-reloads-and-severe-input-lag-after-update/1401563/2
Other users report problems on the same package or app build, including different Windows hardware. These strengthen the update-regression hypothesis, but may represent different failure paths:
Request and existing private support case
Please investigate the renderer crashes and UI performance regression in 26.924.2738.0 / app build 26.924.22138 (11645), and provide the response requested above. Please also advise how to collect a useful native crash dump or stack privately. If a fix is available or planned, please identify its version and release status.
I escalated a private OpenAI Support conversation on September 28 at about 14:29 JST. At the 18:14 JST check, I had not received a human reply, and I could not find an acknowledgment of this Windows desktop rendering issue on the public status page. These are the times of those observations.
This issue URL and the same correlation code have already been sent directly into my authenticated, existing Support conversation. The code was also sent to [email protected] from the same account. The public reporter and the person raising that existing Support case are the same person. Please connect this report and the user-impact details with that case and share them with the engineering and usage-compensation teams.
Public correlation code: CDX-20260928-8C64E22E07.
No personal name, email address, employer, account or conversation ID, user path, project contents, order identifiers, payment credentials, or unreviewed raw logs are included in this public report.