Windows Store App crashes on launch when Windows user profile contains Korean characters

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

26.609.4994.0

What subscription do you have?

pro

What platform is your computer?

_No response_

What issue are you seeing?

<!-- Failed to upload "b6ce72f2-3f87-409f-963c-24de31bc2aa8.dmp" -->

What steps can reproduce the bug?

What issue are you seeing?

The Codex Windows Store app stopped launching after updating to version 26.609.4994.0.

The app starts several Codex.exe processes for a few seconds and then exits without showing any window.

Environment
Platform: Windows 11
Codex version: 26.609.4994.0
Installation: Microsoft Store
Steps to reproduce
Install Codex from Microsoft Store.
Use a Windows account whose profile path contains Korean characters.
Launch Codex.

Example profile path:

C:\Users\서비스지원310

Observed behavior
Multiple Codex.exe processes appear briefly.
No UI window is shown.
Application exits silently.
Crash dump (.dmp) files are generated.
Codex logs only contain:

Launching app
Appshot hotkey inactive

Additional findings

Creating a new Windows account with an English-only profile path fixes the issue completely.

Example working profile:

C:\Users\codexuser

This suggests the issue may be related to Unicode / non-ASCII Windows profile paths.

What is the expected behavior?

_No response_

Additional information

_No response_

+++++ The issue still occurs on version 26.611.8604.0.

The crash is reproducible when running Codex under a Windows user profile path containing Korean characters. The application launches multiple Codex.exe processes and then exits without displaying any UI.

The problem does not occur when using a Windows account with an English-only profile path, which strongly suggests that the issue is related to handling non-ASCII / Unicode characters in the Windows user profile path. This appears to be a critical issue, as users with Korean Windows profile paths are currently unable to use Codex.

A fix for this issue would be greatly appreciated, as it prevents affected users from launching Codex at all.