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.

Sign up for GitHub

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

Jump to bottom

Window restore issue when running terminal elevated #13711

Closed
lupinitylabs opened this issue Aug 9, 2022 · 3 comments
Closed

Window restore issue when running terminal elevated #13711

lupinitylabs opened this issue Aug 9, 2022 · 3 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

@lupinitylabs
Copy link

Windows Terminal version

1.14.1962.0

Windows build number

10.0.19044.1826

Other Software

No response

Steps to reproduce

Open terminal in elevated mode (run as administrator). Minimize it by clicking the app on the taskbar, then try to restore the window by clicking on it again:

Unminimize.Issue.mp4

Expected Behavior

I would expect the app window to restore after clicking, regardless whether it was run elevated or not.

Actual Behavior

Restoring the window works if not run as administrator, but it does not work when run as administrator.
@lupinitylabs lupinitylabs added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Aug 9, 2022
@ghost ghost added 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 Aug 9, 2022
@DHowett
Copy link
Member

DHowett commented Aug 9, 2022

Thanks for the report! This looks like a /duplicate of #13589, which is fixed pending release.

@ghost
Copy link

ghost commented Aug 9, 2022

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!

@ghost ghost closed this as completed Aug 9, 2022
@ghost ghost 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 Aug 9, 2022
@lupinitylabs
Copy link
Author

Actually it looks like an exact duplicate of #13592. Sorry, and thanks!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
No milestone
Development

No branches or pull requests
2 participants
@DHowett @lupinitylabs