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

Trying elevated WT does not open #15532

Closed
mwpowellhtx opened this issue Jun 9, 2023 · 4 comments
Closed

Trying elevated WT does not open #15532

mwpowellhtx opened this issue Jun 9, 2023 · 4 comments
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

@mwpowellhtx
Copy link

Windows Terminal version

1.17.11461.0

Windows build number

10.0.19041.685

Other Software

I've been opening WT elevated for quite some time and it has been working fine up until today. It was working just yesterday. Now it seems it will not open. Prompts me for the elevated, but no window is opening. Actually, it has also been prompting me unknown program when I do, not sure why that is either, may or may not be related. Having scanned some of the tech forums as well, some suggest that, this is the point of WT, that you need Administrator access to run it, so do not need to elevate it, but this is inaccurate. Some processes you still need an elevated CL in order to do anything with them sometimes, especially if you are doing anything process level, which I sometimes do. So force of habit, I just generally open it that way.

Steps to reproduce

Simply this, CTRL+SHIFT click the taskbar, or CTRL+SHIFT+WIN+(pos) depending on the position.

Expected Behavior

I expect the WT to open elevated with the first configured CL.

Actual Behavior

Apparently, nothing. Ghosted. No window whatsoever is being opened elevated.

@mwpowellhtx mwpowellhtx 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 Jun 9, 2023
@thomas-berg
Copy link

I experience the same thing, I added my crash report to this issue: #15526

@carlos-zamora
Copy link
Member

Hi @mwpowellhtx. Thanks for filing! We're going to mark this as a /dup of #15526. We'll revisit that one in a bit. Thanks again!

@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 14, 2023
@mwpowellhtx
Copy link
Author

Cautiously optimistic, sounds promising. Thanks!

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