Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run this Profile as Admin starts Windows Powershell instead of Powershell7 #15391

Closed
leoniDEV opened this issue May 20, 2023 · 4 comments
Closed
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@leoniDEV
Copy link

leoniDEV commented May 20, 2023

Windows Terminal version

1.17.1023

Windows build number

10.0.25352.0

Other Software

No response

Steps to reproduce

Create and account of type administrator;
Create a Windows Terminal's profile for Powershell7
In Windows Terminal set a profile for Windows Powershell as default profile;

Create an account of type standard;
login with this standard account;
Create a Windows Terminal's profile for Powershel7 an set Run this profile as Administrator to on
Try to open this Pwsh7 profile;
enter credential of the account of type administrator

Expected Behavior

Open a new elevated instance of Windows Terminal running Powershell 7

Actual Behavior

A new elevated instance of Windows Terminal is opened with the default profile loaded

@leoniDEV leoniDEV added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels May 20, 2023
@leoniDEV
Copy link
Author

I think I understand what happen, when open a new tab, wt use the command new-tab --profile {GUID}, this GUID is the one of the profile in the settings of the standard account, but when try to open a profile as admin (when the admin is another account) it load the settings from the admin account which doesn't contains the GUID that wt try to load and then the default profile is loaded.

As a workaround I copied the GUID of the Powershell profile from the standard account to the Powershell profile in the setting file of the admin account.

@zadjii-msft
Copy link
Member

Ho boy this is a good edge case here. I don't think any of us considered that "Run as Admin" (where the admin account != your current user account) uses the settings from the admin account, not your own.

@zadjii-msft zadjii-msft added the Needs-Discussion Something that requires a team discussion before we can proceed label May 22, 2023
@carlos-zamora
Copy link
Member

Hey @leoniDEV! Thanks for filing, we're going to mark this as a dup of #11111.

/dup #11111

@microsoft-github-policy-service
Copy link
Contributor

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 5, 2023
@carlos-zamora carlos-zamora removed the Needs-Discussion Something that requires a team discussion before we can proceed label Jun 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants