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

Is it possible to have elevated consoles follow default terminal setting? #15922

Closed
zamadatix opened this issue Sep 1, 2023 · 2 comments
Closed
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@zamadatix
Copy link

zamadatix commented Sep 1, 2023

This is more a question as I assume the problem comes down to my ignorance about voodoo done for launching elevated sessions.... but, given there is nowadays a way to set the default terminal application, why must elevated console sessions (e.g. running a .bat file as admin or launching diskpart from a non-elevated Terminal session) still default to the legacy Windows Console Host instead of follow the preference like non-elevated sessions do? I thought the reasoning may have to do with the setting being per user but even running Windows Terminal as admin the preference still shows as Windows Terminal.

@zamadatix zamadatix added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Sep 1, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Sep 1, 2023
@zadjii-msft
Copy link
Member

Basically, we've been tracking this in #10276. The way the default terminal setting works is based off Packaged COM. Unfortunately, Packaged COM still doesn't work for our needs in an elevated context.

Till then, follow /dup #10276

@zadjii-msft zadjii-msft closed this as not planned Won't fix, can't repro, duplicate, stale Sep 5, 2023
@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 Needs-Tag-Fix Doesn't match tag requirements labels Sep 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. 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

2 participants