VS Code started from terminal holding console open

[AnrDaemon]

Type: Bug

I've reported this issue earlier and got a response to use wrapper scripts from ./bin/ directory.
Unfortunately, they only cure half the problem. The diagnostic messages cease to appear in console, but the console remains to be held by the VS Code process until I completely exit the IDE, even if application I've opened the workspace from is long gone.

Simple reproduction:

1. Win+X, open command prompt.
2. Call "%ProgramFiles%/Microsoft VS Code/bin/code.cmd" "%path%/to/your/workspace"
3. In command prompt terminal, type exit.
4. Even though the command interpreter is gone, the console window remains open.
5. Close VS Code. The console will close following shutdown of the IDE.

VS Code version: Code 1.72.2 (d045a5e, 2022-10-12T22:15:18.074Z)
OS version: Windows/any
Modes:
Sandboxed: No

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (8 x 3408)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: disabled_off
Load (avg)	undefined
Memory (System)	15.92GB (10.33GB free)
Process Argv	--folder-uri file:///c%3A/Users/Admin/Documents/hk/invapi-php
Screen Reader	no
VM	0%

[AnrDaemon]

The previous issue was #98164

[bersbersbers]

This goes back as far as #6608 :) Are you aware of #10162?

[AnrDaemon]

That's actually how I start VS Code "in production" - through cygstart utility or a batch file wrapper. But that's a problem in itself, I have to remember to use a wrapper at every time.
I can't simply use file associations, like with any normal program.

[deepak1556]

Merging to #66750