You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
This started happening after I updated powershell a few days ago. #299
Thanks for the report, and for the path. That was the clue.
Cause: the shell saved in your settings is the PowerShell App Execution Alias (%LOCALAPPDATA%\Microsoft\WindowsApps\pwsh.exe). That is the path where pwsh.exe returns, and so what wmux's own shell detector stores, when PowerShell 7 is installed from the Store. Windows refuses to open an alias the way a normal file is opened, so wmux's "does this exe exist?" check answered no. Its fallback was to look inside C:\Program Files\WindowsApps, which a normal user is not allowed to list. So every pane fell back to Windows PowerShell 5.1. Your PowerShell update most likely changed which pwsh.exe comes first on PATH, which is why it started then.
Fix (2.28.1): wmux now reads the alias to find the real pwsh.exe behind it and starts that. Your setting keeps the alias, so future Store updates of PowerShell keep working without touching anything.
Released in v2.28.1. Feel free to reopen if a new pane still shows that yellow line.
Activity
amirlehmam commentedon Oct 18, 2026
Thanks for the report, and for the path. That was the clue.
Cause: the shell saved in your settings is the PowerShell App Execution Alias (
%LOCALAPPDATA%\Microsoft\WindowsApps\pwsh.exe). That is the pathwhere pwsh.exereturns, and so what wmux's own shell detector stores, when PowerShell 7 is installed from the Store. Windows refuses to open an alias the way a normal file is opened, so wmux's "does this exe exist?" check answered no. Its fallback was to look insideC:\Program Files\WindowsApps, which a normal user is not allowed to list. So every pane fell back to Windows PowerShell 5.1. Your PowerShell update most likely changed whichpwsh.execomes first on PATH, which is why it started then.Fix (2.28.1): wmux now reads the alias to find the real
pwsh.exebehind it and starts that. Your setting keeps the alias, so future Store updates of PowerShell keep working without touching anything.Released in v2.28.1. Feel free to reopen if a new pane still shows that yellow line.
fix: resolve App Execution Alias shells (amirlehmam#299), never wait …