**My Whole computer is completely unusable and super laggy as soon as I start codex after the last update to the windows codex app. the below is the issue and solution (which shouldn’t have to be applied).
What is happening:** Codex Desktop’s Electron main process is running a background CPU/I/O loop. It is creating enough scheduler, cache, and page-fault pressure to delay mouse and keyboard handling across Windows. Your laptop is not short on RAM, and vmmem is no longer involved.
Why it started tonight: Windows forcibly upgraded Codex from 26.803.10989.0 to 26.810.4967.0 at approximately 12:57 AM. The old app was terminated for servicing and the new package launched immediately. Your reported onset and this package transition align exactly.
Direct evidence
For the main ChatGPT.exe process, PID 9736:
- Sustained 1.15–1.22 full CPU cores.
- Read 317–327 MiB/s continuously from cached/local data.
- Generated 45,000–70,000 page faults per second.
- A separate 10-second sample recorded 3.08 GiB read, 13.55 CPU-seconds, and 763,050 page faults.
- Minimizing Codex made essentially no difference:
- Visible: 1.15 cores, 327 MiB/s.
- Minimized: 1.20 cores, 317 MiB/s.
- Restored: 1.22 cores, 327 MiB/s.
Therefore this is not 4K rendering or cursor drawing. It is background work inside the Electron main process.
Additional defects found
Codex repeatedly launches reg.exe and conhost.exe to query the Windows default browser. I observed eight pairs in 22 seconds. That is unnecessary periodic process churn from the packaged application.
The new package also still contains the known Windows process-discovery and Git-origin code paths:
Win32_ProcessWin32_PerfFormattedData_PerfProc_Processchild-process-snapshot-workergit-origins
Those paths have previously been tied to measured system-wide input stalls. A published controlled A/B reduced maximum mouse-event delay from 234 ms to 16 ms after suppressing those scans
Same problem here. I’m on Windows version 26.810.41047 and my whole PC gets extremely laggy
Same! It’s laggy and unable to function properly unless you close the app.
Hope it’ll get fixed