mise activation fails for powershell 5.1

[danf-s1]

I haven't been able to get mise to activate in my PowerShell 5.1 session, so I've had to fall back to the shim method.
Tested with the latest v2025.1.8, installed manually by extracting .\mise to c:\Program Files\ and adding c:\Program Files\mise\bin to the PATH variable.

The documentation for PowerShell seems like it has repeated commands (mise activate twice) and doesn't work for PowerShell 5.1: https://mise.jdx.dev/installing-mise.html#powershell
echo '~/.local/bin/mise activate mise activate pwsh | Out-String | Invoke-Expression' >> $HOME\Documents\PowerShell\Microsoft.PowerShell_profile.ps1

When I update the command to run in my environment and for PowerShell 5.1 as such:
echo 'mise activate pwsh | Out-String | Invoke-Expression' >> $HOME\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1

The results are several errors when opening a new PowerShell 5.1 session:

Unable to find type [System.Management.Automation.LocationChangedEventArgs].
At line:54 char:30
+ ... pwd_hook = [EventHandler[System.Management.Automation.LocationChanged ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Manageme...hangedEventArgs:TypeName) [], RuntimeException
    + FullyQualifiedErrorId : TypeNotFound

The property 'LocationChangedAction' cannot be found on this object. Verify that the property exists and can be set.
At line:66 char:13
+             $ExecutionContext.SessionState.InvokeCommand.LocationChan ...
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : PropertyAssignmentException

& : The term 'C:\Program' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:47 char:11
+         & C:\Program Files\mise\bin\mise.exe hook-env $args -s pwsh | ...
+           ~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (C:\Program:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

The third error seems to be due to a space in the mise path. If I move the mise binary path location to a path without spaces, I only get the first two errors. This path issue is impacting both PowerShell 5.1 and PowerShell 7.4. The activation issue only impacts PowerShell 5.1.

[NavyD]

You should use pwsh 7.4 lts instead of powershell 5.1 as the current implementation #3506 uses C# api's such as System.Management.Automation.LocationChangedEventArgs that require powershell at least 7.2

You can also check out the installing mise powershell

[robertwt7]

I tried doing this but it doesn't seem to be working as well for me:

mise activate pwsh | Out-String | Invoke-Expression

I'm on powershell 7.2.24

[jdx]

we should figure out what the oldest version of powershell that actually works with mise is. That activation instruction certainly looks wrong too.

I'd accept a PR for including support for older powershell versions too.

[danf-s1]

I tried doing this but it doesn't seem to be working as well for me:

mise activate pwsh | Out-String | Invoke-Expression

I'm on powershell 7.2.24

I've had luck with these commands for adding mise activation to the powershell profile (although Powershell 5.1 generates the errors mentioned in my initial post):

# Powershell 5.1:  
echo 'mise activate pwsh | Out-String | Invoke-Expression' >> $HOME\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1

# PowerShell 7.4:  
echo 'mise activate pwsh | Out-String | Invoke-Expression' >> $HOME\Documents\PowerShell\Microsoft.PowerShell_profile.ps1

[robertwt7]

one of the issue that i'm facing right now is that apps like android studio refuse to use powershell 7 by default. so running android studio won't recognise the binaries that is installed from mise because its not activated. i have to reinstall node again with the .exe file to bypass this

there is a setting to bypass the terminal in android studio, however it doesn't change the default shell that it's using when running the app. I guess that's windows for you :/

[jdx]

you should be using shims with that sort of setup