Launching terminal using --startingDirectory does not work for "." in v1.23

[rkodey]

Windows Terminal version

1.23.10353.0

Windows build number

10.0.19045.5371

Other Software

• Windows Terminal in portable mode using ".portable"
• This bug affects VSCode, when it launches the external terminal.
• But, VSCode is not required, as shown below

Steps to reproduce

See basic configuration settings.json in comment below
Open a command prompt

cd \Users

Expected Behavior

Version 1.22.10352.0 works as expected.

cd \Users

command-line	Opens Terminal In
wt.exe	C:\Users
wt.exe -d .	C:\Users
wt.exe -d "."	C:\Users
wt.exe -d "C:\Users"	C:\Users
wt.exe --startingDirectory .	C:\Users
wt.exe --startingDirectory "."	C:\Users
wt.exe --startingDirectory "C:\Users"	C:\Users

Actual Behavior

Version 1.23.10353.0 shows the bug.

cd \Users

command-line	Opens Terminal In
wt.exe	C:\WINDOWS\system32
wt.exe -d .	C:\WINDOWS\system32
wt.exe -d "."	C:\WINDOWS\system32
wt.exe -d "C:\Users"	C:\Users
wt.exe --startingDirectory .	C:\WINDOWS\system32
wt.exe --startingDirectory "."	C:\WINDOWS\system32
wt.exe --startingDirectory "C:\Users"	C:\Users

[rkodey]

Here's the minimal settings.json to show the issue.
I started with a blank configuration

• Set default profile to Coommand Prompt
• Ser Command Prompt starting directory to null

{
    "$help": "https://aka.ms/terminal-documentation",
    "$schema": "https://aka.ms/terminal-profiles-schema-preview",
    "defaultProfile": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
    "profiles": 
    {
        "defaults": {},
        "list": 
        [
            {
                "commandline": "%SystemRoot%\\System32\\cmd.exe",
                "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
                "hidden": false,
                "name": "Command Prompt",
                "startingDirectory": null
            }
        ]
    }
}