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

Terminal app is opening and closing rapidly when "Run as administrator" is enabled #14879

Closed
StragaSevera opened this issue Feb 19, 2023 · 5 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

@StragaSevera
Copy link

Windows Terminal version

1.16.10261.0

Windows build number

10.0.19045.2604

Other Software

No response

Steps to reproduce

  1. Open terminal application.
  2. Go to Settings -> Defaults (or to a default profile).
  3. Enable "Run this profile as Administrator".
  4. Close application.
  5. Open it again.

Expected Behavior

Application is opening normally.

Actual Behavior

The button on taskbar blinking, opening and closing the app, while the process is spawning and de-spawning in Process Manager.

@StragaSevera StragaSevera 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 Feb 19, 2023
@jamespack
Copy link
Contributor

This happens to me at work where my user account is different from my administrator account. To fix it I have to login with my Admin account and run terminal. Then I can log back in to my standard user account and run as administrator. I used to be able to fix it by reregistering the appx as admin but that stopped working a while back

@cloud-66
Copy link

I have the same bug. Also all shells run as administrator despite that "Run this profile as Administrator" is disabled. And i don't know how to run shell as non administrator

@zadjii-msft
Copy link
Member

Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #13928 for more discussion.

/dup #13928

@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 Feb 20, 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!

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

4 participants