Can't start with powershell and scoop

[alex289]

Code of Conduct

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

What happened?

I am using scoop to install oh my posh and just update to the latest version. When I now open the terminal I get following:

The term 's not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
195
134
241m¯éÂThe term '241m¯éÂs not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
195
134
241mThe term '241ms not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
255
255m: The term '255m' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
195
134
241mThe term '241ms not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
255
255mAlexander.Konietzko@BO-NB8104The term '255mAlexander.Konietzko@BO-NB8104s not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
195
134
241mThe term '241ms not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
255
255m: The term '255m' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
195
134
241m¯é░The term '241m¯é░s not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
71
156
49m¯é░The term '49m¯é░s not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
71
156mThe term '156ms not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
255
255m: The term '255m' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
71
156mThe term '156ms not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
255
255mdevThe term '255mdevs not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
71
156mThe term '156ms not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
255
255m: The term '255m' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
64
196
255mThe term '255ms not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
71
156m¯é░The term '156m¯é░s not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
64
196
255mThe term '255ms not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
25
53
73m: The term '73m' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
64
196
255mThe term '255ms not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
25
53
73m93The term '73m93s not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
64
196
255mThe term '255ms not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
25
53
73m´èò: The term '73m´èò' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
0
119
194mThe term '194ms not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
64
196
255m¯é░The term '255m¯é░s not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
0
119
194mThe term '194ms not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
255
255m: The term '255m' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
0
119
194mThe term '194ms not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
255
255mpwshThe term '255mpwshs not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
0
119
194mThe term '194ms not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
255
255m: The term '255m' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
255
255mThe term '255ms not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
0
119
194m¯é░The term '194m¯é░s not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
255
255mThe term '255ms not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
17
17
17m: The term '17m' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
255
255mThe term '255ms not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
17
17
17mNO: The term '17mNO' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
255
255mThe term '255ms not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
17
17
17m: The term '17m' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
255
255m¯é░The term '255m¯é░s not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
46
149
153
49m¯é░The term '49m¯é░s not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
46
149
153mThe term '153ms not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
255
255m: The term '255m' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
46
149
153mThe term '153ms not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
255
255
255m: The term '255m' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
2
46
149
153m¯é┤The term '153m¯é┤
dev: The term 'dev' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

I tried it without the theme and executing directly in an active window with same result

Theme

{
  "$schema": "https://raw.githubusercontent.com/JanDeDobbeleer/oh-my-posh/main/themes/schema.json",
  "blocks": [
    {
      "alignment": "left",
      "segments": [
        {
          "background": "#29315A",
          "foreground": "#E64747",
          "leading_diamond": "\ue0b6",
          "style": "diamond",
          "template": "{{ .UserName }}",
          "trailing_diamond": "\ue0b4 ",
          "type": "session"
        },
        {
          "background": "#29315A",
          "foreground": "#3EC669",
          "leading_diamond": "\ue0b6",
          "properties": {
            "style": "folder"
          },
          "style": "diamond",
          "template": "\ue5ff {{ .Path }}",
          "trailing_diamond": "\ue0b4",
          "type": "path"
        },
        {
          "background": "#29315A",
          "foreground": "#43CCEA",
          "leading_diamond": " \ue0b6",
          "properties": {
            "branch_icon": ""
          },
          "style": "diamond",
          "template": "{{ .HEAD }}",
          "trailing_diamond": "\ue0b4",
          "type": "git"
        },
        {
          "background": "#29315A",
          "foreground": "#42E66C",
          "leading_diamond": " \ue0b6",
          "style": "diamond",
          "template": "\ue718 {{ if .PackageManagerIcon }}{{ .PackageManagerIcon }} {{ end }}{{ .Full }}",
          "trailing_diamond": "\ue0b4",
          "type": "node"
        },
        {
          "background": "#29315A",
          "foreground": "#9B6BDF",
          "leading_diamond": " \ue0b6",
          "style": "diamond",
          "template": " \ue77f {{ if .Unsupported }}\uf071{{ else }}{{ .Full }}{{ end }} ",
          "trailing_diamond": "\ue0b4",
          "type": "dotnet"
        },
        {
          "background": "#29315A",
          "foreground": "#AEA4BF",
          "leading_diamond": " \ue0b6",
          "properties": {
            "style": "austin",
            "threshold": 150
          },
          "style": "diamond",
          "template": "{{ .FormattedMs }}",
          "trailing_diamond": "\ue0b4",
          "type": "executiontime"
        }
      ],
      "type": "prompt"
    },
    {
      "alignment": "left",
      "newline": true,
      "segments": [
        {
          "foreground": "#7FD5EA",
          "leading_diamond": "\ue0b6",
          "style": "plain",
          "template": "\u276f",
          "trailing_diamond": "\ue0b4",
          "type": "text"
        }
      ],
      "type": "prompt"
    }
  ],
  "final_space": true,
  "version": 2
}

What OS are you seeing the problem on?

Windows

Which shell are you using?

powershell

Log output

(Image above because I couldn't add it here)

[JanDeDobbeleer]

I am using scoop to install oh my posh

@alex289 did you see this discussion? We changed the way "our" scoop installs oh-my-posh so you also have signed executables. However, the behaviour described here implies that your terminal (or shell) can't evaluate ANSI anymore as well which is a change in PowerShell 7.2.

[alex289]

Mmh, any idea what I can do now?

[JanDeDobbeleer]

@alex289 the thread contains some information on how to set your PowerShell environment up right.

[JuergenGutsch]

I tried it setting $PSStyle.OutputRendering to 'Ansi' in Powershell without success.

Putting the following in the profile, print out the prompt once, no matter what output rendering is set:
"oh-my-posh init pwsh" | Invoke-Expression

Without the quotes, I get that list of errors. Even no matter what the OutputRendering is set to

[JanDeDobbeleer]

@JuergenGutsch it needs to be without quotes, otherwise it's just a string, not a command. Can you have a look at what $env:TERM says? That one's responsible as well to potentially disable ANSI. See here as well.

[JuergenGutsch]

ANSI needs to be enabled right? If I get the docs right, $env:TERM should be empty, and $PSStyle.OutputRendering should be set to 'Ansi'
Initially on my machine, $env:TERM was empty, and $PSStyle.OutputRendering was set to 'Host' by default.

I played around with the settings and just got one effect:
Setting it to 'xtermm' should set $PSStyle.OutputRendering to 'PlainText', which results in the long list of errors, but without colors :-D

Those setting don't really help

[JuergenGutsch]

I have the exact same problem but installed oh-my-posh using winget

I get this error in PowerShell 7.x and Windows Powershell on Win11

[JanDeDobbeleer]

@alex289 @JuergenGutsch so, we figured it out. There's an old executable of oh-my-posh on your systems that's causing this behavior. So, while you've installed the new binary, on your PATH the old one takes precedence and that one outputs an ANSI string and not a PowerShell script. You should see two entries when using Get-Command oh-my-posh and oh-my-posh version reporting something old.

[JuergenGutsch]

Hey @JanDeDobbeleer
Using Get-Command I just see one entry:

But that might be the reason anyway. I played around with oh-my-posh in past, without success, and left the old artifacts.
I gonna clean it up a bit and will see if it works.
Thanks for the hint.

[JanDeDobbeleer]

@JuergenGutsch it's definitely that, as oh-my-posh version should display the version. This one is an old one.

[JuergenGutsch]

Yes, I just had a look into the folders. That version was from 2020.

I'm just cleaning up and try to reinstall

[JuergenGutsch]

I also have a version from 2021 installed.
You see, I tried it a couple of times to get it running :-D

[JuergenGutsch]

That was it! It is all working. Thank you :-D