starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

New tabs don't launch in the directory of the first tab when launching WT via cmd.exe shorthand #19289

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

Originally created by @Pieter-Dewachter on GitHub (Jan 30, 2023).

Windows Terminal version

1.15.3466.0

Windows build number

10.0.22621.1105

Other Software

No response

Steps to reproduce

Reproduce actual (broken) behaviour:

  1. When in a particular folder with Explorer, open Terminal by typing "cmd" in the address bar
  2. Create a new tab in the opened Terminal window

Reproduce expected behaviour:

  1. When in a particular folder with Explorer, open Terminal by typing "wt" in the address bar
  2. Create a new tab in the opened Terminal window

Expected Behavior

The new tab should have the same working director as the first tab, if settings.json is correctly setup.
This is already the case when launching Terminal through the "wt" shorthand, but not via "cmd".

Actual Behavior

The new tab always starts in "C:\Windows\System32" regardless of the starting directory of the first tab.
When launching Terminal through the "wt" shorthand, the new tab will start in the correct directory.

Originally created by @Pieter-Dewachter on GitHub (Jan 30, 2023). ### Windows Terminal version 1.15.3466.0 ### Windows build number 10.0.22621.1105 ### Other Software _No response_ ### Steps to reproduce Reproduce actual (broken) behaviour: 1. When in a particular folder with Explorer, open Terminal by typing "cmd" in the address bar 2. Create a new tab in the opened Terminal window Reproduce expected behaviour: 1. When in a particular folder with Explorer, open Terminal by typing "wt" in the address bar 2. Create a new tab in the opened Terminal window ### Expected Behavior The new tab should have the same working director as the first tab, if settings.json is correctly setup. This is already the case when launching Terminal through the "wt" shorthand, but not via "cmd". ### Actual Behavior The new tab always starts in "C:\Windows\System32" regardless of the starting directory of the first tab. When launching Terminal through the "wt" shorthand, the new tab will start in the correct directory.
claunia added the Issue-BugIssue-TaskProduct-TerminalPriority-2Area-DefApp labels 2026-01-31 06:39:07 +00:00
claunia commented 2026-01-31 06:39:08 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 1, 2023):

Notes:

  • This is different from #5506.
  • We'd need to somehow crack CMD's CWD when it launches and then package that up with the defterm connection for Terminal to read
  • Terminal would then use that as it's "initial" CWD, ala #5506

Or, you could set up your CMD prompt to emit the CWD and then duplicateTab would just do the right thing.

@zadjii-msft commented on GitHub (Feb 1, 2023): Notes: * This is different from #5506. * We'd need to somehow crack CMD's CWD when it launches and then package that up with the defterm connection for Terminal to read * Terminal would then use that as it's "initial" CWD, ala #5506 Or, you could set up your CMD prompt to [emit the CWD](https://learn.microsoft.com/en-us/windows/terminal/tutorials/new-tab-same-directory) and then `duplicateTab` would just do the right thing.
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 Issue-Task Priority-2 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#19289
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?