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

Cannot run WindowsTerminal.exe as other user from the Windows Store version #3534

Closed
yllekz opened this issue Nov 12, 2019 · 4 comments
Closed
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@yllekz
Copy link

yllekz commented Nov 12, 2019

Environment

Windows build number: 10.0.18362.387
Windows Terminal version (if applicable): 0.6.2951.0

Any other software?

Steps to reproduce

When I try to either engage "runas" on C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe or shift right click and "run as another user" on WindowsTerminal.exe, it gives me an error.

Can this be fixed? Or alternately, can a feature be built into Windows Terminal where you can relaunch as a different user?

Expected behavior

App launches as the user I specify

Actual behavior

The application will either a) reject my perfectly valid credentials (which work in other prompts), or b) give me an access denied error.

Runas:
Attempting to start C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe as user "domainname\otherusername" ...
RUNAS ERROR: Unable to run - C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
5: Access is denied.

"Run as other user" GUI:
"Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item."

Unsure if this same issue happens on the non-Store version.

@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 Nov 12, 2019
@DHowett-MSFT
Copy link
Contributor

Thanks for the report. This looks like a /dupe of #1032.

@ghost
Copy link

ghost commented Nov 14, 2019

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 Nov 14, 2019
@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 Nov 14, 2019
@jflattery
Copy link

Thanks for the report. This looks like a /dupe of #1032.

I would argue this is not a dupe of #1032 as #1032 does not imply that the user account requesting the elevated window/tab is different than the admin user account. In my case, I have two accounts on my system. One account is my daily driver which is a standard user, the other is my admin account. With the current setup I am unable to elevate a tab or window in the terminal app, and need to revert to using powershell or cmd directly, which defeats the purpose of terminal.

@dejandjuranovic
Copy link

dejandjuranovic commented May 8, 2020

Thanks for the report. This looks like a /dupe of #1032.

I would argue this is not a dupe of #1032 as #1032 does not imply that the user account requesting the elevated window/tab is different than the admin user account. In my case, I have two accounts on my system. One account is my daily driver which is a standard user, the other is my admin account. With the current setup I am unable to elevate a tab or window in the terminal app, and need to revert to using powershell or cmd directly, which defeats the purpose of terminal.


I use the same scenario, two accounts on the same machine, one of them admin. Elevation works as long as both profiles have the same version of Windows Terminal.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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