starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 16:05:21 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Run profile as Administrator is not allowed #17755

New Issue
Closed
opened 2026-01-31 05:52:25 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 05:52:25 +00:00
Owner
Copy Link

Originally created by @wolf99 on GitHub (Jun 20, 2022).

Windows Terminal version

1.13.11431.0

Windows build number

21H2 (19044.1706

Other Software

No response

Steps to reproduce

Windows is managed by my organisation.
Usually UAC will allow me to run things locally as an administrator as my org has not blocked this.

  • Create a cmd prompt profile with Run this profile ad Administrator switched On
  • Try to open a new tavb using this profile

Expected Behavior

  • Security policy requests confirmation of execution
  • User confirms execution
  • Tab opens in administrator mode

Actual Behavior

  • Security policy requests confirmation of execution (for unknown app)
  • User confirms execution
  • Windows warns that the app has been blocked

image

Spitballing; perhaps policy is not specifically blocking WT, but is blocking "unknown" apps, which would mean that this is related to https://github.com/microsoft/terminal/issues/12357

Note that using gsudo to achieve admin access instead of the WT-native feature, does not suffer from this same issue. There the execution is on gsudo though...

https://www.howtogeek.com/789658/how-to-open-powershell-as-admin-in-windows-terminal/

Originally created by @wolf99 on GitHub (Jun 20, 2022). ### Windows Terminal version 1.13.11431.0 ### Windows build number 21H2 (19044.1706 ### Other Software _No response_ ### Steps to reproduce Windows is managed by my organisation. Usually UAC will allow me to run things locally as an administrator as my org has not blocked this. - Create a cmd prompt profile with `Run this profile ad Administrator` switched `On` - Try to open a new tavb using this profile ### Expected Behavior - Security policy requests confirmation of execution - User confirms execution - Tab opens in administrator mode ### Actual Behavior - Security policy requests confirmation of execution _(for `unknown` app)_ - User confirms execution - Windows warns that the app has been blocked ![image](https://user-images.githubusercontent.com/281700/174566129-b38091a6-9eed-4212-af31-4797fa926f75.png) Spitballing; perhaps policy is not specifically blocking WT, but _is_ blocking "unknown" apps, which would mean that this is related to https://github.com/microsoft/terminal/issues/12357 Note that using gsudo to achieve admin access instead of the WT-native feature, does not suffer from this same issue. There the execution is on `gsudo` though... https://www.howtogeek.com/789658/how-to-open-powershell-as-admin-in-windows-terminal/
claunia commented 2026-01-31 05:52:27 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 20, 2022):

Can you run the terminal successfully as admin via the right click on taskbar, right click on app, run as administrator shortcut?

image

I suspect this is because the app isn't installed for the admin profile, but I can't be sure. Can you contact your sysadmin for clarification on what policy specifically blocked this/? That might help us get to the root cause on our end.

FWIW I believe the "unknown program" thing is a known bug in Windows 10 that should be getting serviced.

@zadjii-msft commented on GitHub (Jun 20, 2022): Can you run the terminal successfully as admin via the right click on taskbar, right click on app, run as administrator shortcut? ![image](https://user-images.githubusercontent.com/18356694/174586342-fb5a9085-81e4-4621-adaa-696923f5f9fc.png) I suspect this is because the app isn't installed for the admin profile, but I can't be sure. Can you contact your sysadmin for clarification on what policy specifically blocked this/? That might help us get to the root cause on our end. FWIW I believe the "unknown program" thing is a known bug in Windows 10 that _should_ be getting serviced.
claunia commented 2026-01-31 05:52:27 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 24, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jun 24, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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 Issue-Bug Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
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#17755
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?