Steps to reproduce
Run a Windows program installed in ${env:USERPROFILE}\AppData\Local\Microsoft\WindowsApps, e.g. iTunes.exe or wt.exe (the new Windows Terminal) from the interactive command line.
Expected behavior
The process launches in a new window, a new prompt is displayed and you can run new commands in PowerShell.
Actual behavior
PowerShell waits until the Windows application exits before allowing new commands to be entered. PowerShell is behaving as though the program was a console application.
It makes perfect sense to wait when PowerShell can't determine if the process is a Windows or console application, so a proper should do a better job processing these reparse points to inspect the real executable.
Steps to reproduce
Run a Windows program installed in
${env:USERPROFILE}\AppData\Local\Microsoft\WindowsApps, e.g.iTunes.exeorwt.exe(the new Windows Terminal) from the interactive command line.Expected behavior
The process launches in a new window, a new prompt is displayed and you can run new commands in PowerShell.
Actual behavior
PowerShell waits until the Windows application exits before allowing new commands to be entered. PowerShell is behaving as though the program was a console application.
It makes perfect sense to wait when PowerShell can't determine if the process is a Windows or console application, so a proper should do a better job processing these reparse points to inspect the real executable.