Standalone Windows app triggers WMI Provider Host (90–100% CPU) when opening one project, while the same project works normally in the VS Code extension

What version of the Codex App are you using (From “About Codex” dialog)?

26.715.12143

What subscription do you have?

ChatGPT Plus

What platform is your computer?

_No response_

What issue are you seeing?

Summary

The standalone Codex Windows app causes WMI Provider Host (WmiPrvSE.exe) to consume approximately 90–100% CPU whenever I open a specific project.

The problem is reproducible even when I create a completely new chat in that project and do not send any message or run any task.

The same project works normally with the Codex extension in VS Code, without high WMI CPU usage.

---

Environment

• Codex standalone Windows app version: 26.715.12143
• Operating system: Windows 11
• Affected component: Standalone Codex Windows app
• Unaffected component: Codex extension in VS Code

Windows version/build:

Please insert the output of `winver` here.

### What steps can reproduce the bug?

### Environment

- Codex App: 26.715.12143
- Windows 11 x64
- ChatGPT Plus

### Steps to reproduce

1. Launch the standalone Codex Windows app.
2. Open the affected local project.
3. Wait until the project finishes loading.
4. Open any existing conversation **or create a brand-new empty conversation**.
5. Do **not** send any prompt and do **not** run any task.
6. Open Windows Task Manager.

### Actual behavior

Immediately after entering the project:

- `WMI Provider Host (WmiPrvSE.exe)` jumps to 90–100% CPU.
- The application becomes sluggish.
- Windows Event Viewer continuously logs WMI Activity Event ID 5858.
- The issue occurs before any prompt is sent.

The problem is reproducible every time.

### Expected behavior

Opening a project or an empty conversation should not trigger continuous WMI activity or high CPU usage.

### Additional observations

- The exact same project works normally in the Codex VS Code extension.
- The issue only occurs in the standalone Windows app.
- Other projects appear to work normally.

This issue appears to be associated with the standalone application's project/workspace initialization rather than conversation content, because creating a brand-new empty conversation in the same project reproduces the issue immediately.

### What is the expected behavior?

_No response_

### Additional information

_No response_