-no-console can not work

[Astro-Aionia]

Windows Terminal version

1.17.11461.0

Windows build number

10.0.19045.3086

Other Software

I find this bug when using Syncthing, but I'm sure this bug can reproduce with any CLI programs

Steps to reproduce

run a CLI program with a parameter -no-console

e.g., I write this bat file to run Syncthing without console window:

start "Syncthing" syncthing.exe -no-console -no-browser

Expected Behavior

Launch the program and close the tab immediately.

Actual Behavior

It will open a new tab and keep the screen output. But in cmd it wil close the cmd window

[zadjii-msft]

This is definitely a dupe, but it's hard to say where to exactly. Here are some notes:

• downstream: -no-console option does not work when Windows Terminal is set as Default Terminal application syncthing/syncthing#8046
• PowerShell argument WindowStyle -Hidden is not respected when the default terminal application is Windows Terminal #12464
  • This is the thread I think is probably the most relevant.
  • There's another note in Epic: Default-by-default fall-out, long-term plans, and community feedback #13392 too.
• Allow console allocation policies that are finer-grained than the PE image subsystem #7335
  • notable mention here.
  • I'm guessing that syncthing is a CONSOLE subsystem exe. I'm guessing that folks are running it from like, a shortcut, or the run dialog - basically, from something that can't just call CreateProcess with specific flags.
  • There's gotta be some commandline that'll launch a console app hidden. Idly, I wonder if cmd.exe /c start /min "Syncthing" syncthing.exe -no-console -no-browser would work.
    • That should cause defterm to not handoff for the "minimized" syncthing.exe launch. Once syncthing is launched in conhost, it should be able to SW_HIDE its console window. A Terminal window might still flash on screen (for the cmd.exe), but it should disappear quick.

[PankajBhojwani]

Thank you for submitting the issue! We've determined this is a /dup #12464

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!