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

Open in Windows terminal does not work with Powershell and special characters #15890

New Issue
Closed
opened 2026-01-31 04:51:27 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 04:51:27 +00:00
Owner
Copy Link

Originally created by @codec-abc on GitHub (Nov 15, 2021).

Windows Terminal version (or Windows build number)

1.11.2921.0

Other Software

No response

Steps to reproduce

  1. Make Powershell as the default terminal
  2. Create a directory named [test]. Open it with Windows Explorer. Right click in the empty space and choose Open in Windows terminal .
  3. Powershell current directory should be in the directory. Instead it is in C:\Windows\System32\WindowsPowerShell\v1.0

if the [test] directory is renamed test it will work. So I guess the path given to the powershell prompt through the Windows Terminal are not escaped properly (or something similar).

Expected Behavior

The current directory of Powershell after using Open in Windows terminal should be the one from which the action was triggered in the explorer (at least for local path).

Actual Behavior

Powershell current directory reverted to C:\Windows\System32\WindowsPowerShell\v1.0

Originally created by @codec-abc on GitHub (Nov 15, 2021). ### Windows Terminal version (or Windows build number) 1.11.2921.0 ### Other Software _No response_ ### Steps to reproduce 1. Make Powershell as the default terminal 2. Create a directory named ``[test]``. Open it with Windows Explorer. Right click in the empty space and choose ``Open in Windows terminal ``. 3. Powershell current directory should be in the ``directory``. Instead it is in ``C:\Windows\System32\WindowsPowerShell\v1.0`` if the ``[test]`` directory is renamed ``test`` it will work. So I guess the path given to the powershell prompt through the Windows Terminal are not escaped properly (or something similar). ### Expected Behavior The current directory of Powershell after using ``Open in Windows terminal `` should be the one from which the action was triggered in the explorer (at least for local path). ### Actual Behavior Powershell current directory reverted to ``C:\Windows\System32\WindowsPowerShell\v1.0``
claunia added the Resolution-Duplicate label 2026-01-31 04:51:27 +00:00
claunia commented 2026-01-31 04:51:28 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 15, 2021):

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #11652 for more discussion.

/dup #11652

Unfortunately, this is a PowerShell issue. The version of PowerShell that comes with Windows cannot handle being started in a folder that has [] in it. PowerShell 6+ does properly handle it, however.

@zadjii-msft commented on GitHub (Nov 15, 2021): Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #11652 for more discussion. /dup #11652 > Unfortunately, this is a PowerShell issue. The version of PowerShell that comes with Windows cannot handle being started in a folder that has `[]` in it. PowerShell 6+ _does_ properly handle it, however.
claunia commented 2026-01-31 04:51:28 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 15, 2021):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Nov 15, 2021): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-31 04:51:28 +00:00
Author
Owner
Copy Link

@codec-abc commented on GitHub (Nov 15, 2021):

Yes, sorry for not finding the duplicate :(

And yeah, installing Powershell 7 solves this. I guess Powershell 5 is a bit weird.

@codec-abc commented on GitHub (Nov 15, 2021): Yes, sorry for not finding the duplicate :( And yeah, installing Powershell 7 solves this. I guess Powershell 5 is a bit weird.
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 Resolution-Duplicate
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#15890
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?