Can't start Terminal with admin privileges #10858

Closed
opened 2026-01-31 02:32:07 +00:00 by claunia · 5 comments
Owner

Originally created by @TheChilliPL on GitHub (Oct 2, 2020).

Environment

Windows build number: Windows 10 v 2004 build 19041.508
Windows Terminal version (if applicable): preview 1.4.2652.0

Steps to reproduce

Right click on any Windows Terminal icon and select Run as Administrator.

Expected behavior

Windows Terminal should open normally, with administrator privileges.

Actual behavior

After asking for admin password 2 times, it doesn't start and throws an error instead:
image

Originally created by @TheChilliPL on GitHub (Oct 2, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Windows 10 v 2004 build 19041.508 Windows Terminal version (if applicable): preview 1.4.2652.0 ``` # Steps to reproduce Right click on any Windows Terminal icon and select `Run as Administrator`. # Expected behavior Windows Terminal should open normally, with administrator privileges. # Actual behavior After asking for admin password 2 times, it doesn't start and throws an error instead: ![image](https://user-images.githubusercontent.com/18823939/94899985-8a7c3980-0494-11eb-8a4c-3144a8ca3bbf.png)
claunia added the Resolution-Duplicate label 2026-01-31 02:32:07 +00:00
Author
Owner

@conioh commented on GitHub (Oct 3, 2020):

Are you trying to elevate the same user or are you trying to "Run as Administrator" as another user?

@conioh commented on GitHub (Oct 3, 2020): Are you trying to elevate the same user or are you trying to "Run as Administrator" as another user?
Author
Owner

@TheChilliPL commented on GitHub (Oct 3, 2020):

I'm clicking Run as Administrator in the context menu of the exe, but I'm not logged in as one, so I'm prompted to type in the password of another administrative user.

@TheChilliPL commented on GitHub (Oct 3, 2020): I'm clicking `Run as Administrator` in the context menu of the exe, but I'm not logged in as one, so I'm prompted to type in the password of another administrative user.
Author
Owner

@zadjii-msft commented on GitHub (Oct 5, 2020):

Unfortunately, this scenario doesn't work quite right today. IIRC you need to have the Terminal installed for the admin user as well. There are more details in #4217, which is tracking this issue with the platform team as well. Thanks!

/dup #4217

@zadjii-msft commented on GitHub (Oct 5, 2020): Unfortunately, this scenario doesn't work quite right today. IIRC you need to have the Terminal installed for the admin user as well. There are more details in #4217, which is tracking this issue with the platform team as well. Thanks! /dup #4217
Author
Owner

@ghost commented on GitHub (Oct 5, 2020):

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 commented on GitHub (Oct 5, 2020): 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!
Author
Owner

@conioh commented on GitHub (Oct 5, 2020):

I'm clicking Run as Administrator in the context menu of the exe, but I'm not logged in as one, so I'm prompted to type in the password of another administrative user.

As @zadjii-msft said you need to have WT installed for the other user too, but from what I recall you also need to have WT in both users at the same version. If you've updates it through the store in your non-admin user but haven't updated it in your admin user, you'd get this error.

@conioh commented on GitHub (Oct 5, 2020): > I'm clicking `Run as Administrator` in the context menu of the exe, but I'm not logged in as one, so I'm prompted to type in the password of another administrative user. As @zadjii-msft said you need to have WT installed for the other user too, but from what I recall you also need to have WT in both users _at the same version_. If you've updates it through the store in your non-admin user but haven't updated it in your admin user, you'd get this error.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#10858