Windows 10: Codex background process causes intermittent system-wide mouse stutter

Open 💬 8 comments Opened Jul 19, 2026 by IZTACIYU
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary

After a recent Windows 10 update, launching Codex causes intermittent mouse-input stutter across the whole system.

The stutter continues even after closing the Codex window. It stops immediately only after fully terminating the Codex process tree. Launching Codex again makes the issue return.

This appears to be related to Codex remaining active in the background and periodically attempting to collect process snapshots through WMI.

Environment

  • OS: Windows 10 Pro, version 10.0.19045.6466
  • Codex Desktop version: 26.715.4045.0
  • Codex executable: C:\Program Files\WindowsApps\OpenAI.Codex_26.715.4045.0_x64__2p2nqsd0c76g0\app\resources\codex.exe

Steps to reproduce

  1. Restart Windows.
  2. Launch Codex Desktop.
  3. Use the PC normally for a while.
  4. Intermittent system-wide mouse stutters begin occurring.
  5. Close the Codex window.
  6. The stutters continue.
  7. Run:
taskkill /F /IM codex.exe /T
  1. The stutters stop immediately.
  2. Launch Codex again.
  3. The stutters return.

Expected behavior

Closing Codex should fully stop any background activity that can affect system responsiveness. Codex should not cause periodic system-wide mouse-input stutter.

Actual behavior

  • Closing the Codex window does not terminate codex.exe and its child processes.
  • The system intermittently stutters until the full Codex process tree is terminated.
  • The issue is reproducible: killing the process resolves it, while relaunching Codex brings it back.

Relevant logs

The Codex log repeatedly contains this warning at roughly 16 minute 30 second intervals:

[electron-sampler] Failed to collect child process snapshot

The sampler invokes PowerShell/WMI queries including:

Get-CimInstance Win32_PerfFormattedData_PerfProc_Process
Get-CimInstance Win32_Process

At the same time, Windows Event Viewer contains repeated WMI Activity errors involving:

Win32_PerfFormattedData_PerfProc_Process
ResultCode: 0x800706BA
Could not send status to client

The ResizeObserver loop completed with undelivered notifications messages also appear in the log, but they seem unrelated to the system-wide input stutter.

Notes

  • There are no obvious Codex crash reports, GPU reset events, or sustained high CPU usage when checking after the stutter.
  • The direct WMI query succeeds but takes roughly 700 ms on this machine.
  • This may be related to the Electron process sampler and its repeated WMI process enumeration after recent Windows updates.

View original on GitHub ↗

8 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #33940
  • #33875
  • #34025
  • #34050

Powered by Codex Action

Pyshenkam · 1 month ago

METOO

mrg1988 · 1 month ago

i have this for several days now too. on Windows 11.

andreipet · 1 month ago

Yeap. Thought on changing my laptop but now i see that is Codex related.
I guess it helps to see I am not the only one having these strange issues: https://www.reddit.com/r/codex/comments/1uxpr1x/severe_codex_windows_app_lag_and_systemwide_mouse/
All system metrics are green. It will be hard to investigate an issue that is not affecting everybody.

jimmonster · 29 days ago

Even today, using the latest versions of Codex CLI and ChatGPT, this issue still occurs.

chess-oai contributor · 23 days ago

thanks for the detailed reports and investigation here: they were really helpful 💖

  • we’ve shipped fixes in 26.730.7989.0 that address some major sources of powershell/wmi storms
  • taskkill.exe can still be started by other process-cleanup paths, and we’re continuing to work on reducing that separately

if you’re still seeing sustained wmi cpu usage or system-wide lag after 26.730.7989.0, please share an updated /feedback id

JellyNash · 13 days ago

Still reproducible on Windows app 26.810.4967.0

I am experiencing intermittent severe mouse-pointer/input lag affecting Windows globally, not only the Codex window.

Environment:

  • Codex/ChatGPT desktop package: 26.810.4967.0 x64
  • Windows 11 Pro x64, build 26200
  • Ryzen 9 3950X, 64 GB RAM
  • NVIDIA RTX 4080

Isolation performed:

  • The lag remained after the active Codex task finished and became idle.
  • It remained when switching to a brand-new blank task with no agent running.
  • Fully quitting the Codex/ChatGPT application immediately restored smooth mouse movement, without restarting Windows.
  • Reopening the application remained smooth initially.

This suggests an intermittent state retained by the desktop application's process tree, rather than one particular project, conversation, or actively running agent.

A clean baseline showed low CPU/GPU use, ample available memory, minimal interrupt/DPC pressure, and no display or WHEA errors. I have not captured evidence proving WMI is the cause, so this may be WMI/process sampling, helper-process cleanup, renderer state, or another application-wide mechanism.

No /feedback ID is available yet. Please advise whether a feedback capture taken during the next affected period would be useful and what should be included.

LiweiDong · 13 days ago

I can reproduce the same system-wide input lag on a newer Codex version.

Codex version: 26.810.4967.0
GPU: AMD Radeon RX 6700 XT
Feedback ID: 01a000b5-c5fa-7801-bc1f-70f9a69abcaa

After restarting Windows, mouse and keyboard input are completely normal until I launch Codex Desktop. Once Codex is running, both mouse movement and keyboard input become choppy across the entire system.

Minimizing the app does not help. The lag stops only after Codex is fully terminated, and returns after launching it again.

CPU, memory, disk, and GPU usage are not saturated. Windows App Repair, closing background utilities, changing USB ports, and testing different mouse connection methods did not resolve the issue.

thanks for the detailed reports and investigation here: they were really helpful 💖感谢您提供的详细报告和调查:它们真的很有帮助💖 we’ve shipped fixes in 26.730.7989.0 that address some major sources of powershell/wmi storms我们在 26.730.7989.0 中发布了修复程序,解决了 PowerShell/WMI 风暴的一些主要根源问题。 taskkill.exe can still be started by other process-cleanup paths, and we’re continuing to work on reducing that separatelytaskkill.exe 仍然可能由其他进程清理路径启动,我们正在继续努力减少这种情况的发生。 if you’re still seeing sustained wmi cpu usage or system-wide lag after 26.730.7989.0, please share an updated /feedback id如果在升级到 26.730.7989.0 版本后,您仍然遇到 WMI CPU 使用率持续过高或系统整体延迟的问题,请提供更新后的 /feedback ID。