Windows PowerShell works, pwsh 7.4.5 doesn't

[underlines]

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

What happened?

First of all: OMP is awesome and I use it for years. Love your work. I use it without problems in Windows Terminal + Windows PowerShell (the legacy one). But recently I had to move to MS pwsh (the open source one) and noticed it doesn't work (it never did on my machine, even on older versions).

System

• Windows 11 Pro
• Windows Terminal (set Nerd Font, use pwsh to invoke PowerSHell 7.4.5)
• Nerd Font: 'Hack' (I tried with 'MesloLGM Nerd Font')
• Microsoft PowerShell 7.4.5 hereby referred to as pwsh doesn't work (tried MS Store and winget Version)
• Windows PowerShell (legacy, works)

Windows PowerShell

$PROFILE content:

oh-my-posh init pwsh --config ~/jandedobbeleer.omp.json | Invoke-Expression

Write-Host $error empty

debug

oh-my-posh debug pwsh

visual:

MS pwsh 7.4.5:

$PROFILE content:

oh-my-posh init pwsh --config ~/jandedobbeleer.omp.json | Invoke-Expression

Write-Host $error empty

debug

oh-my-posh debug pwsh

visual:

Theme

default: jandedobbeleer.omp.json

What OS are you seeing the problem on?

Windows

Which shell are you using?

powershell

Log output

[pwsh debug.txt](https://github.com/user-attachments/files/17118429/pwsh.debug.txt)
[Windows PowerShell debug.txt](https://github.com/user-attachments/files/17118426/Windows.PowerShell.debug.txt)

[underlines]

Found your issue in PowerShell/PowerShell

[Console]::OutputEncoding = [Text.Encoding]::UTF8 fixed it, when added to $PROFILE before the OMP invokation.

So my init script now looks like this:

[Console]::OutputEncoding = [Text.Encoding]::UTF8
oh-my-posh init pwsh --config ~/jandedobbeleer.omp.json | Invoke-Expression
Import-Module -Name Terminal-Icons

If you compare both outputs exactly in my log output it really seems to be an encoding problem as you noted:

•  jb   ~    Windows PowerShell legacy
• ¯é jb ¯é░¯é░ ¯¬â ~ ¯é░¯é░ ´Çî ¯é Microsoft PowerShell 7
•  jb   ~    Microsoft PowerShell 7 after changing text encoding to UTF8

[JanDeDobbeleer]

@underlines this is a PowerShell UTF8 issue they currently still refuse to fix. We can't solve that. You'll need to force the shell to UTF8 before initializing oh-my-posh.