starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

startupActions not run when in elevated window #18385

New Issue
Open
opened 2026-01-31 06:12:20 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 06:12:20 +00:00
Owner
Copy Link

Originally created by @svict4 on GitHub (Sep 6, 2022).

Windows Terminal version

4.14.2282.0

Windows build number

10.0.22000.0

Other Software

No response

Steps to reproduce

  1. Add a startupAction in the settings.json at the top level
{
  "$help": "https://aka.ms/terminal-documentation",
  "startupActions": "new-tab; new-tab",
  ...
}
  1. Add the elevate property to a profile, such as the defaults profile
...
  "profiles": {
    "defaults": {
      "colorScheme": "Tango Dark",
      "elevate": true,
      ...
    },
    "list": [ ... ]
  }
...
  1. See that the startupActions are not respected.
  2. See that by commenting/removing the elevate property, that it runs the startupActions

Expected Behavior

That the arguments in startupActions are run, even in elevated window

Actual Behavior

startupActions are ignored/not run

Originally created by @svict4 on GitHub (Sep 6, 2022). ### Windows Terminal version 4.14.2282.0 ### Windows build number 10.0.22000.0 ### Other Software _No response_ ### Steps to reproduce 1. Add a `startupAction` in the `settings.json` at the top level ``` { "$help": "https://aka.ms/terminal-documentation", "startupActions": "new-tab; new-tab", ... } ``` 2. Add the [`elevate` property](https://docs.microsoft.com/en-us/windows/terminal/customize-settings/profile-general#automatically-run-as-administrator) to a profile, such as the `defaults` profile ``` ... "profiles": { "defaults": { "colorScheme": "Tango Dark", "elevate": true, ... }, "list": [ ... ] } ... ``` 3. See that the `startupActions` are not respected. 4. See that by commenting/removing the `elevate` property, that it runs the `startupActions` ### Expected Behavior That the arguments in `startupActions` are run, even in `elevated` window ### Actual Behavior `startupActions` are ignored/not run
claunia added the Issue-FeatureArea-SettingsProduct-Terminal labels 2026-01-31 06:12:21 +00:00
claunia commented 2026-01-31 06:12:21 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 7, 2022):

We'll need to come up with a proper design for this.

Opening an elevated "Foo" profile triggering the creation of a elevated window isn't going to hit startupActions ever. In that case, the "startup actions" has been effectively replaced by a single action - "open a tab with Foo".

  • Maybe we need an "open elevated window" action, that just opens wt without any actions. That would default to just startupActions.
  • Maybe we need a separate elevatedStartup for actions to run on startup of an elevated window. These would then be different from startupActions.
  • There's also #12191 - that could be combined with the command palette's commandline mode for a --elevate nt ; sp command to run specific actions in an elevated window.
@zadjii-msft commented on GitHub (Nov 7, 2022): We'll need to come up with a proper design for this. Opening an elevated "Foo" profile triggering the creation of a elevated window isn't going to hit `startupActions` ever. In that case, the "startup actions" has been effectively replaced by a single action - "open a tab with Foo". * Maybe we need an "open elevated window" action, that just opens wt without any actions. That would default to just `startupActions`. * Maybe we need a separate `elevatedStartup` for actions to run on startup of an elevated window. These would then be different from `startupActions`. * There's also #12191 - that could be combined with the command palette's commandline mode for a `--elevate nt ; sp` command to run specific actions in an elevated window.
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-Settings Issue-Feature 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#18385
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?