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

'Run profile as admin' ignored when running bat or cmd directly (double-clicking) #22215

New Issue
Closed
opened 2026-01-31 08:06:43 +00:00 by claunia · 12 comments
claunia commented 2026-01-31 08:06:43 +00:00
Owner
Copy Link

Originally created by @Bostonjunk on GitHub (Sep 4, 2024).

Windows Terminal version

1.21.2361.0

Windows build number

10.0.22631.0

Other Software

No response

Steps to reproduce

Change default profile setting to enable 'Run profile as administrator' then try and open a batch file or cmd file by double-clicking on it.

Caveat - I am logged into Windows as a standard user but need to run scripts under a separate admin account. Terminal is installed for both the standard and admin user.

Extra context - I upgraded from a Windows 10 to a Windows 11 laptop - everything else works fine, this is the only thing I can't get functioning as it did before.

Expected Behavior

To double-click on the bat or cmd file and be prompted for elevation and the bat or cmd to launch in an elevated Terminal window.
This is how it functioned on my old laptop.

Actual Behavior

I am not prompted for elevation and the bat or cmd file opens in a standard session.

If Terminal is run directly, or the + is pressed for a new tab, only then am I prompted for elevation.

Originally created by @Bostonjunk on GitHub (Sep 4, 2024). ### Windows Terminal version 1.21.2361.0 ### Windows build number 10.0.22631.0 ### Other Software _No response_ ### Steps to reproduce Change default profile setting to enable 'Run profile as administrator' then try and open a batch file or cmd file by double-clicking on it. Caveat - I am logged into Windows as a standard user but need to run scripts under a separate admin account. Terminal is installed for both the standard and admin user. Extra context - I upgraded from a Windows 10 to a Windows 11 laptop - everything else works fine, this is the only thing I can't get functioning as it did before. ### Expected Behavior To double-click on the bat or cmd file and be prompted for elevation and the bat or cmd to launch in an elevated Terminal window. This is how it functioned on my old laptop. ### Actual Behavior I am not prompted for elevation and the bat or cmd file opens in a standard session. If Terminal is run directly, or the + is pressed for a new tab, only then am I prompted for elevation.
claunia commented 2026-01-31 08:06:46 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 4, 2024):

That's totally by design. When you double-click on a batch script, the OS launches an instance of CMD.exe to process that script, then launches a terminal application to handle that script. By the time the Terminal is launched, the script is already running unelevated. The terminal settings can't affect the elevation of that process anymore. That hasn't changed between Windows 10 & 11

To double-click on the bat or cmd file and be prompted for elevation and the bat or cmd to launch in an elevated Terminal window.
This is how it functioned on my old laptop.

Are you actually clicking on a shortcut to a batch file, one that's got this box checked?
image

because otherwise I don't know how a batch script could request to be run as admin... Maybe it's something specific to that script/?

@zadjii-msft commented on GitHub (Sep 4, 2024): That's totally by design. When you double-click on a batch script, the OS launches an instance of CMD.exe to process that script, _then_ launches a terminal application to handle that script. By the time the Terminal is launched, the script is already running unelevated. The terminal settings can't affect the elevation of that process anymore. That hasn't changed between Windows 10 & 11 > To double-click on the bat or cmd file and be prompted for elevation and the bat or cmd to launch in an elevated Terminal window. This is how it functioned on my old laptop. Are you actually clicking on a shortcut to a batch file, one that's got this box checked? ![image](https://github.com/user-attachments/assets/df47f70c-77d9-4ba2-a7c5-92380d53cb57) because otherwise I don't know how a batch script could request to be run as admin... Maybe it's something specific to that script/?
claunia commented 2026-01-31 08:06:46 +00:00
Author
Owner
Copy Link

@Bostonjunk commented on GitHub (Sep 4, 2024):

Nope, if I use a shortcut as shown in your image, it will open in a conhost window.

On my previous Windows 10 laptop I was using 2 days ago, if I double-clicked directly on a bat or cmd file, it would ask me for elevation and run in an elevated Terminal window - I was just wanting the same behaviour on my new laptop.

The only setting I changed on my old laptop to make this happen was 'Run profile as administrator' - then it functioned as described - I've been using it that way for over 2 years.

EDIT: On my new laptop, if I right-click and run as admin, it will run in a conhost window. If I double-click, it will run in a standard Terminal session.
The only way to currently have it running in Terminal AND as admin, is to run Terminal as admin, then navigate to the folder via the command line and launch it that way, which is much less convenient than just double-clicking on the file.

The bat files themselves serve only as launchers for PowerShell scripts, so the files themselves are literally just:
@ECHO OFF
CLS
powershell -Executionpolicy bypass -file [path to script]
PAUSE

@Bostonjunk commented on GitHub (Sep 4, 2024): Nope, if I use a shortcut as shown in your image, it will open in a conhost window. On my previous Windows 10 laptop I was using 2 days ago, if I double-clicked directly on a bat or cmd file, it would ask me for elevation and run in an elevated Terminal window - I was just wanting the same behaviour on my new laptop. The only setting I changed on my old laptop to make this happen was 'Run profile as administrator' - then it functioned as described - I've been using it that way for over 2 years. EDIT: On my new laptop, if I right-click and run as admin, it will run in a conhost window. If I double-click, it will run in a standard Terminal session. The only way to currently have it running in Terminal AND as admin, is to run Terminal as admin, then navigate to the folder via the command line and launch it that way, which is much less convenient than just double-clicking on the file. The bat files themselves serve only as launchers for PowerShell scripts, so the files themselves are literally just: `@ECHO OFF` `CLS` `powershell -Executionpolicy bypass -file [path to script]` `PAUSE`
claunia commented 2026-01-31 08:06:46 +00:00
Author
Owner
Copy Link

@Bostonjunk commented on GitHub (Sep 4, 2024):

https://github.com/user-attachments/assets/ec567ffe-e4eb-4b7b-99ce-e2c8a6bf6579

@Bostonjunk commented on GitHub (Sep 4, 2024): https://github.com/user-attachments/assets/ec567ffe-e4eb-4b7b-99ce-e2c8a6bf6579
claunia commented 2026-01-31 08:06:46 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 4, 2024):

That's... definitely not supposed to happen 😨

When you get the UAC prompt for the Terminal, what's the commandline it shows? (under "Show more details")

@zadjii-msft commented on GitHub (Sep 4, 2024): That's... definitely not supposed to happen 😨 When you get the UAC prompt for the Terminal, what's the commandline it shows? (under "Show more details")
claunia commented 2026-01-31 08:06:47 +00:00
Author
Owner
Copy Link

@Bostonjunk commented on GitHub (Sep 4, 2024):

20240904_145833

@Bostonjunk commented on GitHub (Sep 4, 2024): ![20240904_145833](https://github.com/user-attachments/assets/5ca1ed60-1eca-41a2-95f7-6f164b7b7f53)
claunia commented 2026-01-31 08:06:47 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 4, 2024):

huh. That's wacky. It

  • boots the unelevated terminal
  • decides that ....\Enable AD Account.bat matches one of your profiles (with a guid of {3ad42e7b-...)
  • evaluates that the profile it matched should be elevated
  • then hands off the commandline instead to an elevated window

So what ends up running is a second copy of that batch script, with the original one presumably terminating early when the original terminal process exits.

That's super weird.

That is on 1.20, but I don't think we changed that in 1.21.
7b50f12a78/src/cascadia/TerminalApp/TerminalPage.cpp (L305-L314)

Most recent changes there are:

Unless we're just not matching this commandline anymore, but I'd doubt that.

Could you manually install a 1.20 Terminal on your win11 machine, and see if that works the same as before? Or inversely, a 1.21 Terminal on win10? I cannot imagine that the handoff logic that's in the OS is different between those two OS versions.

@zadjii-msft commented on GitHub (Sep 4, 2024): huh. That's wacky. It * boots the unelevated terminal * decides that `....\Enable AD Account.bat` matches one of your profiles (with a guid of `{3ad42e7b-...`) * evaluates that the profile it matched should be elevated * then hands off the commandline instead to an elevated window So what ends up running is a _second_ copy of that batch script, with the original one presumably terminating early when the original terminal process exits. That's super weird. That is on 1.20, but I don't think we changed that in 1.21. https://github.com/microsoft/terminal/blame/7b50f12a780ec0f8a55e7f04ad12d65b451f7667/src/cascadia/TerminalApp/TerminalPage.cpp#L305-L314 Most recent changes there are: * #12272 (`1.13`) * #14946 (`1.18`) * #16914 (`1.21`, but I don't _really_ think this is relevant) Unless we're just not matching this commandline anymore, but I'd doubt that. Could you manually install a 1.20 Terminal on your win11 machine, and see if that works the same as before? Or inversely, a 1.21 Terminal on win10? I _cannot_ imagine that the handoff logic that's in the OS is different between those two OS versions.
claunia commented 2026-01-31 08:06:47 +00:00
Author
Owner
Copy Link

@Bostonjunk commented on GitHub (Sep 4, 2024):

I've had this behaviour going back quite a long way - it survived many updates.
I don't know when I first installed Terminal, but I'm pretty sure in the early days it wasn't a Store app, but installed via an old-skool MSI package, maybe? I can't remember my exact update path over the years, but that's the only 'non-standard' aspect to things here. Possibly something to do with my upgrade path from very early versions? (Clutching at straws here a bit)

@Bostonjunk commented on GitHub (Sep 4, 2024): I've had this behaviour going back quite a long way - it survived many updates. I don't know when I first installed Terminal, but I'm pretty sure in the early days it wasn't a Store app, but installed via an old-skool MSI package, maybe? I can't remember my exact update path over the years, but that's the only 'non-standard' aspect to things here. Possibly something to do with my upgrade path from very early versions? (Clutching at straws here a bit)
claunia commented 2026-01-31 08:06:48 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 4, 2024):

Terminal's been an MSIX "store package" since our earliest release - 0.2, so I doubt it's that. I just want to try and narrow down where the delta happened that regressed this scenario for you.

What's the profile in your settings.json with the 3ad42e7b... guid? The commandline for that might be enlightening

@zadjii-msft commented on GitHub (Sep 4, 2024): Terminal's been an MSIX "store package" since our earliest release - 0.2, so I doubt it's that. I just want to try and narrow down where the delta happened that regressed this scenario for you. What's the profile in your settings.json with the `3ad42e7b...` `guid`? The commandline for that might be enlightening
claunia commented 2026-01-31 08:06:48 +00:00
Author
Owner
Copy Link

@Bostonjunk commented on GitHub (Sep 5, 2024):

Apologies - did you want the settings.json file itself or something else as well?

@Bostonjunk commented on GitHub (Sep 5, 2024): Apologies - did you want the settings.json file itself or something else as well?
claunia commented 2026-01-31 08:06:48 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 5, 2024):

Yea the settings.json file would be good enough ☺️

@zadjii-msft commented on GitHub (Sep 5, 2024): Yea the settings.json file would be good enough ☺️
claunia commented 2026-01-31 08:06:48 +00:00
Author
Owner
Copy Link

@1EDExg0ffyXfTEqdIUAYNZGnCeajIxMWd2vaQeP commented on GitHub (Sep 23, 2024):

still relevant AFAIK

@1EDExg0ffyXfTEqdIUAYNZGnCeajIxMWd2vaQeP commented on GitHub (Sep 23, 2024): still relevant AFAIK
claunia commented 2026-01-31 08:06:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 23, 2024):

@1EDExg0ffyXfTEqdIUAYNZGnCeajIxMWd2vaQeP if you're hitting this too, then the same question applies to you ☺️ That's the next thing I'd investigate, and can't do much else without it.

@zadjii-msft commented on GitHub (Sep 23, 2024): @1EDExg0ffyXfTEqdIUAYNZGnCeajIxMWd2vaQeP if you're hitting this too, then the [same question](https://github.com/microsoft/terminal/issues/17859#issuecomment-2331220582) applies to you ☺️ That's the next thing I'd investigate, and can't do much else without it.
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 Area-DefApp Issue-Bug Needs-Author-Feedback Needs-Triage Product-Terminal
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#22215
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?