Windows Codex Desktop 26.623.13972.0 freezes when clicking Add file button

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

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

Version 26.623.101652 • Released 03.07.2026

What subscription do you have?

Plus

What platform is your computer?

OS: Windows Codex Desktop version: 26.623.13972.0 Package: OpenAI.Codex_26.623.13972.0_x64__2p2nqsd0c76g0 Install source: Microsoft Store / msstore Store package ID: 9PLM9XGG6VKS

What issue are you seeing?

Codex Desktop freezes immediately when I click the Add file / attachment button.

No file picker appears. After clicking the button once, the app becomes unresponsive. When I

What steps can reproduce the bug?

  1. Open Codex Desktop on Windows.
  2. Start a new empty chat.
  3. Click the Add file / attachment button.
  4. No file picker opens.
  5. Codex becomes unresponsive.

What is the expected behavior?

Expected behavior

The file picker or attachment menu should open.

Actual behavior

Codex freezes immediately and Windows reports "Not Responding".

Additional information

What I already tried

  • Reinstalled Codex Desktop.
  • Same issue after reinstall.
  • After reinstall, the app was still logged in and had the same state.
  • Backed up %USERPROFILE%\.codex.
  • Renamed %USERPROFILE%\.codex temporarily.
  • Renamed local package data temporarily:

C:\Users\Harry\AppData\Local\Packages\OpenAI.Codex_2p2nqsd0c76g0

  • Started Codex with fresh local state.
  • Same issue persists.
  • Other apps open the Windows file picker normally.
  • The issue is specific to Codex Desktop.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 1 month ago

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

  • #31256

Powered by Codex Action

lutzeman · 10 days ago

I can reproduce the same issue in the current ChatGPT desktop app on Windows.

Environment:

  • Windows 11 x64, OS build 26200.9168
  • Still reproducible on 2026-08-16

Observed behavior:

  1. Open the desktop app and start a chat.
  2. Click the paperclip / Add file button.
  3. The app freezes before the native Windows file picker appears and Windows reports “Not responding”.

Useful comparison / workaround:

  • Dragging and dropping the same files into the composer works.
  • Selecting/uploading files through chatgpt.com in Firefox works.
  • This appears specific to the Windows desktop app's file-picker path, not the files or the network upload itself.

Troubleshooting already attempted without effect:

  • Restarted the app and Windows
  • Windows Settings > Apps > ChatGPT > Repair
  • Reset the app
  • Uninstalled and reinstalled the app

A report was also submitted from the app using /feedback.
Feedback/session ID: no-active-thread-01a00b8d-405b-7502-8b7b-9d486ad4fdda

waynesung83 · 5 days ago

I can reproduce the same issue on the current Windows Codex Desktop build.

Environment

  • OS: Windows 11 x64
  • Codex package: OpenAI.Codex_26.818.5229.0_x64__2p2nqsd0c76g0
  • Package status: OK
  • Timezone: Asia/Taipei (UTC+8)

Reproduction steps

  1. Open Codex Desktop.
  2. Open or start a chat.
  3. Click the + button beside the message composer to add a file.
  4. Codex becomes unresponsive before the file picker appears.

Expected behavior

The attachment/file picker should open without affecting the chat.

Actual behavior

The app hangs and must be restarted. Windows Error Reporting logged this as MoAppHang for the Codex package on 2026-08-23 at approximately 14:24 (UTC+8). No native crash dump was generated.

Additional notes

  • The issue is reproducible specifically from the + attachment button.
  • The installed package is healthy according to Windows package status checks.
  • As a workaround, copying a file in File Explorer and pasting it into the Codex composer with Ctrl+V avoids using the + button.
  • I have not cleared or deleted local Codex data because existing reports indicate that reinstalling or resetting local state does not reliably resolve this issue.