Setting Defaults to Run this profile as Administrator in SUI won't launch un-elevated profiles

[elsaco]

Windows Terminal version

main fbe0416

Windows build number

10.0.19044.0

Other Software

No response

Steps to reproduce

• build and deploy latest CascadiaPackage
• toggle Run this profile as Administrator for Defaults to On . It will set it for all the other profiles, also.
• select one profile and toggle the setting to Off
• launch the un-elevated profile

Sample SUI screenshot:

Expected Behavior

• new un-elevated terminal window

Actual Behavior

• any profile is launched in same window and elevated, even the ones with "elevate": false set.

Sample screenshot with CMD profile set to un-elevated:

settings.json with CMD not elevated:

    "profiles": 
    {
        "defaults": 
        {
            "elevate": true,
            "startingDirectory": "C:\\"
        },
        "list": 
        [
            {
                "commandline": "%SystemRoot%\\System32\\WindowsPowerShell\\v1.0\\powershell.exe",
                "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
                "hidden": false,
                "name": "Windows PowerShell"
            },
            {
                "commandline": "%SystemRoot%\\System32\\cmd.exe",
                "elevate": false,
                "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
                "hidden": false,
                "name": "Command Prompt"
            },

It works the other way around. If some profile is set to be elevated a new terminal window pops-up with admin rights.

[zadjii-msft]

That's on me, I still need to write the docs for elevate. Unfortunately, you can't go backwards. You can't de-elevate a package apparently, so elevate only works to spawn a new elevated window. Once you're in the elevated window, you can theoretically open anything.

I'm gonna make that very clear in the docs.

[zadjii-msft]

Closed in MicrosoftDocs/terminal#490