Windows Explorer's "Open in Terminal" does not escape square brackets into PowerShell

(>_ ); We are reporting this issue on Microsoft Windows’ Feedback Hub. Upvote this report on the Feedback Hub app if you believe this issue should be fixed sooner within Windows

Square brackets are considered special characters in PowerShell, cd "D:\[Assignment 1] Working Directory" will return an ObjectNotFound error unless it is specifically escaped using -LiteralPath, e.g., cd -LiteralPath "D:\[Assignment 1] Working Directory".

Therefore, when “Open in Terminal” is selected on Windows Explorer inside a folder containing square brackets, it will open a PowerShell session with the current directory set to C:\WINDOWS\System32\WindowsPowerShell\v1.0> instead.

Note: Windows PowerShell 5.1 is used. $PSVERSIONTABLE details:

PSVersion: 5.1.26100.7920
PSEdition: Desktop
PSCompatibleVersions: {1.0, 2.0, 3.0, 4.0...}
BuildVersion: 10.0.26100.7920
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1

Windows Terminal v. 1.24.10621.0 is used.