›_ Codex Issues
Codex Issues / #27367

Codex desktop app immediately exits on Windows 10 Pro 22H2 after update, while CLI works

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

Environment

  • OS: Windows 10 Pro
  • Windows version: 22H2
  • OS build: 19045.7417
  • Region/UI language: Korean
  • Codex desktop app version: OpenAI.Codex_26.608.1337.0_x64__2p2nqsd0c76g0
  • Codex CLI version: 0.139.0
  • Authentication: ChatGPT login
  • CLI status: works
  • Desktop app status: does not launch

Problem

After updating Codex, the desktop app no longer opens.

When launching from the Start Menu or using codex app, the process briefly appears in Task Manager and then exits. No visible error dialog is shown.

What I tried

  • Rebooted Windows
  • Reinstalled Codex from Microsoft Store
  • Reinstalled Codex using winget install Codex -s msstore
  • Removed the AppX package with Remove-AppxPackage
  • Cleared/renamed:
  • %APPDATA%\Codex
  • %LOCALAPPDATA%\Codex
  • %LOCALAPPDATA%\Packages\OpenAI.Codex_2p2nqsd0c76g0
  • Reinstalled after cleanup
  • Installed and logged into Codex CLI
  • Verified codex login status
  • Ran Codex CLI successfully
  • Tried launching the desktop app again; same behavior

Observed behavior

The desktop app starts and exits immediately.

The latest desktop log only contains:

2026-06-10T09:11:11.319Z info Launching app agentRunId=null allowDebugMenu=false allowDevtools=false allowInspectElement=false buildFlavor=prod enableSparkle=false enableUpdater=true nodeEnv=undefined packaged=true platform=win32
2026-06-10T09:11:12.041Z info Appshot hotkey inactive configured=true enabled=true platform=win32

Then the app exits.

Windows AppX / TWinUI logs show that activation of OpenAI.Codex_2p2nqsd0c76g0!App was attempted and completed with status 0. AppX deployment/register logs also show successful registration with 0x0.

Additional issue

When using the Codex CLI, the CLI works, but elevated/admin sandbox setup fails. I can continue with the non-admin sandbox. The desktop app issue remains unchanged.

When selecting the elevated/admin sandbox setup option, Windows shows an error dialog saying:

'codex-windows-sandbox-setup.exe' cannot be found.
Please check if the name was entered correctly and try again.

Expected behavior

The Codex desktop app should open normally after launch.

Attachments

  • codex-doctor.txt
  • codex-desktop-latest.log
  • codex-sandbox.log
  • Screenshot of Windows version dialog
  • Screenshot of codex-windows-sandbox-setup.exe error dialog

<img width="757" height="639" alt="Image" src="https://github.com/user-attachments/assets/89459b8c-b595-4ff6-9906-5635804c47e6" />

<img width="831" height="197" alt="Image" src="https://github.com/user-attachments/assets/c5fa9302-d6e9-4ab9-a9a4-9021e04eab2a" />

codex-doctor.txt
codex-sandbox.log
codex-desktop-latest.log

View original on GitHub ↗

10 Comments

github-actions[bot] contributor · 1 month ago

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

  • #27320
  • #27327
  • #27125

Powered by Codex Action

MR-JUKE · 1 month ago

This looks identical to my environment as well, including version 26.608.1337.0 and the app exiting immediately after launch.

I can reproduce the same issue on Codex Windows Desktop App 26.608.1337.0.

Additional details from my environment:

  • OS: Windows 11
  • Windows version: 25H2
  • OS build: 26200.8655
  • Codex Desktop App: OpenAI.Codex_26.608.1337.0_x64__2p2nqsd0c76g0
  • Codex CLI works normally
  • VS Code Codex extension works normally
  • WSL2 Ubuntu works normally
  • AppX activation succeeds
  • The desktop app appears briefly in Task Manager and then exits
  • The desktop log only contains:
  • Launching app ...
  • Appshot hotkey inactive ...
  • Windows WER dump is not created
  • Codex Crashpad .dmp files are created under:

%LOCALAPPDATA%\Packages\OpenAI.Codex_2p2nqsd0c76g0\LocalCache\Roaming\Codex\web\Codex\Crashpad\reports

WinDbg summary from the Crashpad dump:

  • PROCESS_NAME: Codex.exe
  • ERROR_CODE: 0xe06d7363
  • ExceptionCode: e06d7363
  • Exception type: C++ EH exception
  • Stack includes:
  • KERNELBASE!RaiseException
  • chrome!node::MultiIsolatePlatform::DisposeIsolate
  • chrome!v8...
  • chrome!node::PromiseRejectCallback

Already tried:

  • Reinstalled Codex Desktop App
  • Reset AppX user package folder
  • Reset LocalCache\Roaming\Codex
  • Reset LocalCache\Local\Codex
  • Tried --disable-gpu
  • Tried --no-sandbox
  • Tried --disable-features=RendererCodeIntegrity
  • Tried custom --user-data-dir
  • Tested single monitor mode

I can provide the Crashpad .dmp privately if needed, but I am not attaching it publicly because it may contain memory contents.

jaepil-choi · 1 month ago

The same happening on my end. What should I do?

jhtop101 · 1 month ago

Windows 10 22H2 (19045.6466)
Codex 26.608.1337.0
Worked until the update.
After updating, the app launches a process and exits after 2-3 seconds.
CLI works normally.
No Codex crash logs are generated.

baesangrae · 1 month ago

<Korean>

Windows 11 최신 업데이트 이후, Codex Windows 데스크톱 앱이 실행되지 않습니다.

테스트해보니 Windows 계정명이 한글인 경우 사용자 프로필 경로에 한글이 포함됩니다.

예:

C:\Users\한국어 계정명

이 계정에서는 Codex를 실행하면 잠깐 시작되는 것처럼 보이지만, 창이 뜨지 않고 조용히 종료됩니다.

그런데 영어-only Windows 계정을 새로 만들었더니 Codex가 정상적으로 실행되었습니다.

따라서 제 테스트 결과로는 Windows 계정명 또는 사용자 프로필 경로에 포함된 한글/non-ASCII 문자와 관련된 문제로 보입니다.

<English>

After the latest Windows 11 update, the Codex Windows desktop app no longer launches for me.

I tested it on a Windows account where the username contains Korean characters, which makes the user profile path include Korean characters, for example:

C:\Users\한국어 계정명

In that account, Codex briefly starts, no window appears, and then it exits silently.

I then created a new Windows account with an English-only username, and Codex launched successfully.

So based on my test, this seems to be related to Korean/non-ASCII characters in the Windows account name or user profile path.

baesangrae · 1 month ago

<img width="912" height="518" alt="Image" src="https://github.com/user-attachments/assets/4b64e775-cae7-4acd-9365-71bb864d8b30" />

일단, 이 옵션을 체크 후, 윈도우를 다시 시작하면 실행이 잘 됩니다.

zms0529 · 1 month ago
<img alt="Image" width="912" height="518" src="https://private-user-images.githubusercontent.com/49590002/606977042-4b64e775-cae7-4acd-9365-71bb864d8b30.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODEyNzAyNzYsIm5iZiI6MTc4MTI2OTk3NiwicGF0aCI6Ii80OTU5MDAwMi82MDY5NzcwNDItNGI2NGU3NzUtY2FlNy00YWNkLTkzNjUtNzFiYjg2NGQ4YjMwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA2MTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwNjEyVDEzMTI1NlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTZjZjI5YmU5OTQ0N2I2NTNjNjY3YjhhMjEwZWRmNDc3ZDIzOWNmMGYwN2QyZTE2ZGNjM2Y1ZTk0NzcyZjFiMWYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRnBuZyJ9.g_wAqNk7FEgrzKAkJJ4wWESm2l_aHOPrDGKEDFTjFBY"> 일단, 이 옵션을 체크 후, 윈도우를 다시 시작하면 실행이 잘 됩니다.

감사합니다.. 해결되었습니다..ㅠㅠ

jaepil-choi · 1 month ago

@baesangrae 마치 몇 년 전 stackoverflow, github issue 에서 모르는거 서로 물어보고, 구글링해서 해결책 찾던 갬성이 있네요. 해결책 제공 감사합니다.

Thanks for providing the solution. This has actually worked right away. Brings me back to the time when developers asked and answered issues on the internet, sharing knowledge without asking to the AI. Good times. Fond memories.

MR-JUKE · 1 month ago

There’s another workaround for this issue. I applied the fix suggested in Issue #27506.
If a different issue occurs after enabling Unicode UTF-8, try this as well. That said, if Codex is updated, you may need to repeat the steps below.

  1. First, open the %LOCALAPPDATA%\OpenAI\Codex\runtimes\cua_node folder. You can get to %LOCALAPPDATA% by pressing Win+R and entering %LOCALAPPDATA%.
  1. Inside that folder, there may be a directory named something like .staging-789504f8...-dkCDLV. It will probably be created when you run Codex.
  1. Copy just the 789504f8... part from that folder name, and create an empty folder with that exact name.
  1. Copy the files from C:\Program Files\WindowsApps\OpenAI.Codex_26.609.4994.0_x64...\app\resources\cua_node. There will likely be a bin folder and a manifest.json file.
  1. Paste the folders and files from step 4 into the folder you created in step 3.

After applying this method, Codex ran without any issues.
According to Issue #27506, the problem appears to occur when the execution path contains non-ASCII characters.

------------------------------------------------------------------------------------------------------------------------------------------
이 문제에 대한 다른 해결 방법이 있습니다. Issue #27506에서 제시된 해결책을 적용했습니다.
Unicode UTF-8 사용을 적용한 뒤 다른 문제가 발생한다면 이 방법도 시도해 보세요. 다만 Codex가 업데이트되면 아래 과정을 다시 진행해야 할 수도 있습니다.

  1. 먼저 %LOCALAPPDATA%\OpenAI\Codex\runtimes\cua_node 폴더를 여세요. %LOCALAPPDATA% 경로는 Win+R을 눌러 %LOCALAPPDATA%를 입력하면 열 수 있습니다.
  1. 해당 폴더 안에 .staging-789504f8...-dkCDLV 같은 이름의 폴더가 있을 수 있습니다. Codex를 실행하면 이 폴더가 생성될 가능성이 있습니다.
  1. 위 폴더 이름에서 789504f8... 부분만 복사해, 같은 이름의 빈 폴더를 새로 만드세요.
  1. C:\Program Files\WindowsApps\OpenAI.Codex_26.609.4994.0_x64...\app\resources\cua_node 경로에 있는 파일을 복사합니다. 아마 bin 폴더와 manifest.json 파일이 있을 것입니다.
  1. 4단계에서 복사한 폴더와 파일을 3단계에서 만든 폴더 안에 붙여넣으세요.

이 방법을 적용한 뒤 Codex가 문제 없이 실행되었습니다.
Issue #27506의 보고 내용에 따르면, 실행 경로에 비 ASCII 문자가 포함되어 있을 때 이 문제가 발생하는 것으로 보입니다.

etraut-openai contributor · 1 month ago

This bug appears to be affecting a lot of Codex users, so we're treating it as a high priority to get it fixed.