starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-09 02:26:45 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

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

New Issue
Closed
opened 2026-01-31 00:01:03 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 00:01:03 +00:00
Owner
Copy Link

Originally created by @yllekz on GitHub (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.

Originally created by @yllekz on GitHub (Nov 12, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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: 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? <!-- A description of how to trigger this bug. --> # Expected behavior App launches as the user I specify <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # 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. <!-- What's actually happening? -->
claunia added the Resolution-Duplicate label 2026-01-31 00:01:03 +00:00
claunia commented 2026-01-31 00:01:04 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 14, 2019):

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

@DHowett-MSFT commented on GitHub (Nov 14, 2019): Thanks for the report. This looks like a /dupe of #1032.
claunia commented 2026-01-31 00:01:04 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (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 commented on GitHub (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!
claunia commented 2026-01-31 00:01:05 +00:00
Author
Owner
Copy Link

@jflattery commented on GitHub (Feb 14, 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.

@jflattery commented on GitHub (Feb 14, 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.
claunia commented 2026-01-31 00:01:05 +00:00
Author
Owner
Copy Link

@dejandjuranovic commented on GitHub (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.

@dejandjuranovic commented on GitHub (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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4935
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?