Open terminal here fail to open in the right directory if it contains specific characters #15093

Closed
opened 2026-01-31 04:28:23 +00:00 by claunia · 4 comments
Owner

Originally created by @ghost on GitHub (Sep 5, 2021).

Windows Terminal version (or Windows build number)

1.9.1942.0

Other Software

No response

Steps to reproduce

Try to right click - open in terminal - in a directory that contains as example "[" in their name.

Expected Behavior

No response

Actual Behavior

It opens to C:> instead of the current directory.

Originally created by @ghost on GitHub (Sep 5, 2021). ### Windows Terminal version (or Windows build number) 1.9.1942.0 ### Other Software _No response_ ### Steps to reproduce Try to right click - open in terminal - in a directory that contains as example "[" in their name. ### Expected Behavior _No response_ ### Actual Behavior It opens to C:\> instead of the current directory.
claunia added the Needs-Author-FeedbackArea-ShellExtension labels 2026-01-31 04:28:23 +00:00
Author
Owner

@ghost commented on GitHub (Sep 7, 2021):

I manually updated to 1.10.2383.0 but the issue is still there.

@ghost commented on GitHub (Sep 7, 2021): I manually updated to 1.10.2383.0 but the issue is still there.
Author
Owner

@zadjii-msft commented on GitHub (Sep 7, 2021):

gh-11149
weird.

What OS version are you on? What shell are you using? What's the exact path you're trying to open in? Could you share your settings.json?

@zadjii-msft commented on GitHub (Sep 7, 2021): ![gh-11149](https://user-images.githubusercontent.com/18356694/132345562-490c038d-3e4b-446c-88ae-557ded1515e8.gif) weird. What OS version are you on? What shell are you using? What's the exact path you're trying to open in? Could you share your `settings.json`?
Author
Owner

@DHowett commented on GitHub (Sep 7, 2021):

This is a bug in Windows PowerShell (5.1) -- sorry! There's nothing that can be done about that. It does not handle directories with special characters in them properly.

@DHowett commented on GitHub (Sep 7, 2021): This is a bug in Windows PowerShell (5.1) -- sorry! There's nothing that can be done about that. It does not handle directories with special characters in them properly.
Author
Owner

@regs01 commented on GitHub (May 28, 2025):

This is a bug in Windows PowerShell (5.1) -- sorry! There's nothing that can be done about that. It does not handle directories with special characters in them properly.

Something should be done about it. [] are not illegal path characters in Windows.

@regs01 commented on GitHub (May 28, 2025): > This is a bug in Windows PowerShell (5.1) -- sorry! There's nothing that can be done about that. It does not handle directories with special characters in them properly. Something should be done about it. [] are not illegal path characters in Windows.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#15093