microsoft / microsoft/terminal
Calling wt from cmd for working directory "C:\" causes an error
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
Hi,
I was testing the new command line options to open a Windows Terminal for a specified working directory. When calling wt new-tab -d "C:\" from PowerShell this seems to work. Calling the same command from cmd however will print the error message [error 0x8007010b when launching powershell.exe']` in the newly opened Windows Terminal instance. Using the "-p" option to launch a different shell will provoke the same error message for the executable associated with the specified profile name.
Environment
Windows build number: Microsoft Windows [Version 10.0.18363.657]
Windows Terminal version: 0.9.433.0
Steps to reproduce
Call wt new-tab -d "C:\" from cmd.
Expected behavior
Open a new Windows Terminal tab with path C:\ set as the current working directory.
Actual behavior
Opens a Windows Terminal instance with the message:
[error 0x8007010b when launching `powershell.exe']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce wt new-tab -d "C:\" from cmd and compare it with the PowerShell invocation described in the issue. Trace the working-directory handling for the launched shell, then verify that a new tab starts in C:\ without the 0x8007010b error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100