Why does the non-elevated (noadmin) one correctly launches in Windows Terminal,while the elevated (admin) instance launch in the legacy console?
I found that using CLI DOSPROMPT=noadmin open Windows Terminal, while CLI DOSPROMPT=admin runs the Command Prompt. (after grant administrator privileges)
I've noticed a similar behavior with PowerShell. Using CLI DOSPROMPT=noadmin,powershell opens Windows Terminal, while CLI DOSPROMPT=admin,powershellopens the default Windows PowerShell console.
Can all of them be configured to use Windows Terminal?
I know how to run a profile as Administrator in Windows Terminal, just directly using Windows Terminal parameters, such as "C:\XXX\WindowsTerminal.exe" new-tab -p "CMD_Admin", which can open Windows Terminal and run CMD with administrator privileges.
I just don’t quite understand why the elevated and non-elevated states of CLI DOSPROMPT launch different terminal applications. Is there a way to modify this behavior? Since the CLI DOSPROMPT=admin command obviously requires administrator privileges, and I would grant them anyway, there shouldn't be any permission-related issue, right?
The Start Menu does exactly the same thing.
We never run Windows Terminal directly, and it seems Windows 11 only diverts cmd.exe to it when not-elevated. I suspect it's because they couldn't work out a good way for admin and non-admin tabs to be joined in a single window.
Thanks, Leo. I just found a link on GitHub that addresses this issue. I'll post it here in case anyone comes across this thread later and is looking for a solution.