Terminal crashes on `wt .`

[hello-smile6]

Windows Terminal version

1.12.10393.0

Windows build number

19043.1469

Other Software

• Command Prompt
• Windows Explorer
  

Steps to reproduce

1. Open Windows Terminal.
2. Open Command Prompt using a non-Windows Terminal context.
3. Execute wt . in Command Prompt.
   (May also happen with Git Bash)

Expected Behavior

I was expecting to have Windows Terminal open in the current directory.

Actual Behavior

Windows Terminal crashed and I lost about 30 minutes of work.

[hello-smile6]

Just got another error.

[error 2147942402 (0x80070002) when launching `%cd%']

[237dmitry]

I was expecting to have Windows Terminal open in the current directory.

wt --startingDirectory .

[DHowett]

Yes, the argument after wt is a command to run (as in, wt powershell.)

You need to use wt -d xxx to set the starting directory.

[hello-smile6]

Yes, the argument after wt is a command to run (as in, wt powershell.)

You need to use wt -d xxx to set the starting directory.

If that is the case, then what about programs that use Windows Terminal without making sure the target binary exists?

[DHowett]

It should always display an error (as you noted in your second comment) in a new terminal tab/window/pane. If it crashes, that is a bug we should fix.