Terminal: Debugger creates processes every second

Created on 7 Apr 2020  ·  3Comments  ·  Source: microsoft/terminal

Environment

Windows build number: W10 RB1903 18362.752
Windows Terminal version (if applicable): 0.10.781.0

Any other software?

Steps to reproduce

1. open regedit.exe
2. add new key cmd.exe in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\
3. add new Debugger string with value to windows terminal "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.10.781.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe"
4. run cmd.exe
5. enjoy how windows terminal is opened thousands of times ;)

https://framapic.org/FXcZwQgGbBPZ/bYYEfDIIPOXj.png

Expected behavior

open once only

Actual behavior

see step 5.

Issue-Question Needs-Attention Needs-Tag-Fix Needs-Triage Product-Terminal Resolution-Answered
Source
picture crazyyzarc

All 3 comments

_y tho_

Is this really a bug, or expected behavior? I bet your default profile for the Terminal is a cmd.exe profile. Whenever you launch cmd.exe, Windows is going to open a new WT instance, which is going to start cmd.exe as your default profile, which is going to cause Windows to open a new WT instance, ...

This is very much by-design. Do you have some other design or use case in mind?

zadjii-msft picture zadjii-msft on 7 Apr 2020
👍1

I think what they want is #492

DHowett-MSFT picture DHowett-MSFT on 7 Apr 2020
👍1

I think what they want is #492

Yes, when I use the command cmd.exe, I want to open a WT instance instead of system32cmd.exe

crazyyzarc picture crazyyzarc on 8 Apr 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

geeksfn picture geeksfn  ·  3Comments
TayYuanGeng picture TayYuanGeng  ·  3Comments
NickITGuy picture NickITGuy  ·  3Comments
DieselMeister picture DieselMeister  ·  3Comments
mrmlnc picture mrmlnc  ·  3Comments