Problem: initialization fails when Windows username contains non‑ASCII/diacritic characters (é, è, etc.)

[D-Seonay]

Hi everyone,

I'm trying to use Oh My Posh on Windows with a PowerShell profile, but I'm running into an issue when my Windows username contains a non-ASCII character (like "é" in "MathéoDELAUNAY").

What happens

When I run my usual initialization command in my profile:

oh-my-posh init pwsh --config "C:\Users\Public\oh-my-posh\themes<theme>.omp.json" | Invoke-Expression

PowerShell tries to execute a temporary init script in my user folder, but the path gets garbled (for example: "Math├®oDELAUNAY") and the prompt fails to load with a “command not found” error.

Steps I've tried

• Using $HOME instead of $env:USERPROFILE
• Using the short 8.3 path
• Copying the theme to a path without accents

None of these fully solve the problem because the generated init script still goes under my user folder with the accented character.

Environment

• Windows 11
• PowerShell Core (pwsh)
• Oh My Posh latest
• Username contains "é"

My question

Has anyone found a way to make Oh My Posh work correctly when the Windows username contains non-ASCII characters?
Is there a way to force it to generate the init script somewhere safe, or to properly handle Unicode in the init path?

Thank you for any advice or workaround!

[JanDeDobbeleer]

This should be what you're looking for.

[D-Seonay]

Yes, thank you, that solves my problem.
Sorry for the trouble on such a well-crafted project.
I’ll make sure to read the documentation more carefully next time.