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

Ctrl or shift click the new tab button does not use the parent directory as working directory #22468

New Issue
Open
opened 2026-01-31 08:14:19 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 08:14:19 +00:00
Owner
Copy Link

Originally created by @fireattack on GitHub (Oct 30, 2024).

Windows Terminal version

1.21.2911.0

Windows build number

10.0.19045.5011

Other Software

No response

Steps to reproduce

  1. Set default profile CMD (or PS; but steps below are for CMD).
  2. Set your CMD profile's "Starting directory" to "Use parent process directory".
  3. Open a new window of WT at a non-default directory, say, C:\files\.
  4. In this window, click the drop down button (V) next to new tab button (+), and shift or ctrl click the CMD option to create a new window or an administrator window.
  5. Observe the new window is correctly using C:\files\ as current working dir, as expected.
  6. Back to the original window. Shift or ctrl click the new tab button (+) directly.

Expected Behavior

It should create a new window or a new administrator window with default profile, which should be CMD, so it should create a window using C:\files\ as starting dir just like step 4-5.

Actual Behavior

It creates a window using C:\WINDOWS\system32 as working dir, not parent process dir.

Originally created by @fireattack on GitHub (Oct 30, 2024). ### Windows Terminal version 1.21.2911.0 ### Windows build number 10.0.19045.5011 ### Other Software _No response_ ### Steps to reproduce 0. Set default profile CMD (or PS; but steps below are for CMD). 1. Set your CMD profile's "Starting directory" to "Use parent process directory". 3. Open a new window of WT at a non-default directory, say, `C:\files\`. 4. In this window, click the drop down button (V) next to new tab button (+), and shift or ctrl click the CMD option to create a new window or an administrator window. 5. Observe the new window is correctly using `C:\files\` as current working dir, as expected. 6. Back to the original window. Shift or ctrl click the new tab button (+) directly. ### Expected Behavior It should create a new window or a new administrator window with default profile, which should be CMD, so it should create a window using `C:\files\` as starting dir just like step 4-5. ### Actual Behavior It creates a window using `C:\WINDOWS\system32` as working dir, not parent process dir.
claunia added the Issue-BugNeeds-Tag-FixProduct-Terminal labels 2026-01-31 08:14:19 +00:00
claunia commented 2026-01-31 08:14:20 +00:00
Author
Owner
Copy Link

@similar-issues-ai[bot] commented on GitHub (Oct 30, 2024):

We've found some similar issues:

  • #14817 , similarity score: 85%
  • #14601 , similarity score: 83%
  • #14761 , similarity score: 81%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@similar-issues-ai[bot] commented on GitHub (Oct 30, 2024): We've found some similar issues: - #14817 , similarity score: 85% - #14601 , similarity score: 83% - #14761 , similarity score: 81% If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue. > Note: You can give me feedback by 👍 or 👎 this comment.
claunia commented 2026-01-31 08:14:21 +00:00
Author
Owner
Copy Link

@fireattack commented on GitHub (Feb 20, 2025):

This bug still exists, but the behavior changed slightly.

Now, doing so (the steps above) will not open new admin window in unexpected, but understandable C:\WINDOWS\system32, but in a random path:

Image

(To be fair, this path is in my %path% environment variables:

Image

But still)
I have no idea why since that path has nothing to do with where the wt.exe or cmd.exe is located.

@fireattack commented on GitHub (Feb 20, 2025): This bug still exists, but the behavior changed slightly. Now, doing so (the steps above) will not open new admin window in unexpected, but understandable `C:\WINDOWS\system32`, but in a random path: ![Image](https://github.com/user-attachments/assets/aaa111b2-de4c-43cd-ae2d-f4759cee2434) (To be fair, this path is in my %path% environment variables: ![Image](https://github.com/user-attachments/assets/870b4344-f856-43fc-82d0-3b814fed030c) But still) I have no idea why since that path has nothing to do with where the wt.exe or cmd.exe is located.
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-Tag-Fix 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#22468
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?