That’s a lot of language telling the user to do work, when it seems pretty clear that the programming didn’t anticipate profile file paths with characters such as world users might input when it makes the local directory for the new obfuscated chat history storage.
symptom: el�s
could be: Elís (accented, local code page or UTF-16 code point character)
Pointing that you should act on bug reports: understand, replicate, escalate.
Potential Workaround:
- Set
CODEX_HOMEenvironment variable to point to a user-writeable directory outside your user profile, see if the Windows app reads and respects that setting. - Log in with a different local account with English alphabet characters to use this program.
- Investigate alternatives.
I was able to immediately replicate this fault by creating a new local user “elís” and attempting to install the quarter-of-a-gigabyte application from the Microsoft Store.
