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

The Terminal is unable to start PS in a directory having square brackets in its name #18565

New Issue
Closed
opened 2026-01-31 06:17:48 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 06:17:48 +00:00
Owner
Copy Link

Originally created by @UnknownLITE on GitHub (Sep 29, 2022).

Windows Terminal version

1.15.2712.0

Windows build number

10.0.19044 Build 19044

Other Software

Powershell - version 5.1.19041.1682

Steps to reproduce

Ensure Powershell is the default startup profile for Terminal

  1. Create a directory having square brackets in its name. Example- Example [Dir]
  2. Go into the created directory
  3. Use the context menu to open Terminal
    image
  4. Notice the location where it starts in

Expected Behavior

PS should open in the right directory, i.e. where the context menu is used

Actual Behavior

PS didn't open in the right directory, instead opens in C:\WINDOWS\System32\WindowsPowerShell\v1.0

Originally created by @UnknownLITE on GitHub (Sep 29, 2022). ### Windows Terminal version 1.15.2712.0 ### Windows build number 10.0.19044 Build 19044 ### Other Software Powershell - version `5.1.19041.1682` ### Steps to reproduce Ensure Powershell is the default startup profile for Terminal 1. Create a directory having square brackets in its name. **Example**- `Example [Dir]` 2. Go into the created directory 3. Use the context menu to open Terminal ![image](https://user-images.githubusercontent.com/91004913/193066480-ad980051-b204-4d47-a54f-fb2265153e7b.png) 4. Notice the location where it starts in ### Expected Behavior PS should open in the right directory, i.e. where the context menu is used ### Actual Behavior PS didn't open in the right directory, instead opens in `C:\WINDOWS\System32\WindowsPowerShell\v1.0`
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 06:17:48 +00:00
claunia commented 2026-01-31 06:17:49 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Sep 29, 2022):

I believe this is a known bug in Windows PowerShell 5.1. See https://github.com/microsoft/terminal/issues/11149#issuecomment-914397136

@j4james commented on GitHub (Sep 29, 2022): I believe this is a known bug in Windows PowerShell 5.1. See https://github.com/microsoft/terminal/issues/11149#issuecomment-914397136
claunia commented 2026-01-31 06:17:49 +00:00
Author
Owner
Copy Link

@UnknownLITE commented on GitHub (Sep 30, 2022):

I just upgraded Powershell to LTS version 7.2.6, It fixed the issue 👍

@UnknownLITE commented on GitHub (Sep 30, 2022): I just upgraded Powershell to LTS version `7.2.6`, It fixed the issue 👍
claunia commented 2026-01-31 06:17:49 +00:00
Author
Owner
Copy Link

@UnknownLITE commented on GitHub (Sep 30, 2022):

Closing it as it is resolved at my side.

@UnknownLITE commented on GitHub (Sep 30, 2022): Closing it as it is resolved at my side.
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#18565
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?