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

wt.exe startingDirectory argument fails with path containing spaces and a trailing backslash #23628

New Issue
Closed
opened 2026-01-31 08:47:40 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 08:47:40 +00:00
Owner
Copy Link

Originally created by @stuerp on GitHub (Sep 20, 2025).

Windows Terminal version

Preview_1.24.2372.0_x64

Windows build number

10.0.26100.4946

Other Software

PowerShell 7.5.3 as default profile

Steps to reproduce

Fails to set the starting directory (note the trailing backslash):

wt.exe --startingDirectory "c:\A\B B\"

Successfully sets the starting directory:

wt.exe --startingDirectory "c:\A\B B"

Expected Behavior

The starting directory should be set in both cases.

Actual Behavior

[error 2147942402 (0x80070002) when launching `B\']
The system cannot find the file specified.
Originally created by @stuerp on GitHub (Sep 20, 2025). ### Windows Terminal version Preview_1.24.2372.0_x64 ### Windows build number 10.0.26100.4946 ### Other Software PowerShell 7.5.3 as default profile ### Steps to reproduce Fails to set the starting directory (note the trailing backslash): `wt.exe --startingDirectory "c:\A\B B\"` Successfully sets the starting directory: `wt.exe --startingDirectory "c:\A\B B"` ### Expected Behavior The starting directory should be set in both cases. ### Actual Behavior ``` [error 2147942402 (0x80070002) when launching `B\'] The system cannot find the file specified. ```
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:47:40 +00:00
claunia commented 2026-01-31 08:47:41 +00:00
Author
Owner
Copy Link

@marcotaranta commented on GitHub (Oct 8, 2025):

Hello, I'm tackling that issue.

@marcotaranta commented on GitHub (Oct 8, 2025): Hello, I'm tackling that issue.
claunia commented 2026-01-31 08:47:41 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 15, 2025):

Right now the situation here isn't great, but the workaround we've generally recommended for anybody autogenerating paths for -d is to append a . instead. It's going to work on all versions of Terminal, whereas a fix we start rolling out tomorrow is only going to work on that version ;P

@DHowett commented on GitHub (Oct 15, 2025): Right now the situation here isn't great, but the workaround we've generally recommended for anybody autogenerating paths for `-d` is to append a `.` instead. It's going to work on _all versions of Terminal_, whereas a fix we start rolling out tomorrow is only going to work on that version ;P
claunia commented 2026-01-31 08:47:41 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 15, 2025):

FWIW, it looks like this is a duplicate of #4571.

@DHowett commented on GitHub (Oct 15, 2025): FWIW, it looks like this is a duplicate of #4571.
claunia commented 2026-01-31 08:47:42 +00:00
Author
Owner
Copy Link

@stuerp commented on GitHub (Oct 16, 2025):

Right now the situation here isn't great, but the workaround we've generally recommended for anybody autogenerating paths for -d is to append a . instead. It's going to work on all versions of Terminal, whereas a fix we start rolling out tomorrow is only going to work on that version ;P

How is that a workaround? It only is when you know beforehand that the caller generates paths with a trailing backslash. Appending a '.' to "C:\A\B B" results in an invalid path.

@stuerp commented on GitHub (Oct 16, 2025): > Right now the situation here isn't great, but the workaround we've generally recommended for anybody autogenerating paths for `-d` is to append a `.` instead. It's going to work on _all versions of Terminal_, whereas a fix we start rolling out tomorrow is only going to work on that version ;P How is that a workaround? It only is when you know beforehand that the caller generates paths with a trailing backslash. Appending a '.' to "C:\A\B B" results in an invalid path.
claunia commented 2026-01-31 08:47:42 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 17, 2025):

Sorry, I misremembered. Append \.. If the path ends with \, it becomes foo\\. (which is valid.) If it does not end with \, it becomes foo\..

@DHowett commented on GitHub (Oct 17, 2025): Sorry, I misremembered. Append `\.`. If the path ends with `\`, it becomes `foo\\.` (which is valid.) If it does not end with `\`, it becomes `foo\.`.
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-Triage
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#23628
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?