Codex Windows app fails to access workspace/tools when Windows username contains Non-ascii characters

Open 💬 1 comment Opened Jun 11, 2026 by BigBeautifulM

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

0.139.0

What subscription do you have?

Plus

What platform is your computer?

Windows 11

What issue are you seeing?

After a recent Windows/Codex update, Codex installed through the Microsoft Store failed to correctly access workspace files and tools under a Windows account whose username contains Korean characters. The same workflow worked after creating and using a new Windows account with an English/ASCII-only username.
This suggests that the issue is not a general permission problem, but likely a Unicode/non-ASCII path handling problem in the Codex Windows app, its bundled tool execution layer, or the Microsoft Store/AppX sandbox environment.

What steps can reproduce the bug?

The Codex Windows app appears to have a Unicode path handling issue when the Windows user profile path contains Korean characters or other non-ASCII characters.

What is the expected behavior?

The process terminates instantly when started gui desktop version and leaves no error message. And since installation path is not accessible for the user by authorization issue, log files cannot be accessed directly. Only indirect process termination code is able to track down the reason of crash.

Additional information

If this happens, try making a new Windows account fully on English, and install Codex on that account. Worked for me.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗