Repository navigation
[Windows] Empty console window pops up when running any shim (mise-shim spawns mise.exe with visible console) #14751
Unanswered
snakejke
asked this question in
Troubleshooting and bug reports
Replies: 1 comment 2 replies
|
Thanks for the report. I couldn't reproduce this headlessly, so a few details would help narrow it down:
A console program started from a parent that has no console (mintty is the usual case) gets a new console window from Windows itself, so (1) and (4) tell us whether that's what you're seeing or whether mise is spawning something. AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5-5; version: 2.1.299. |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Environment
Description
Starting with recent releases (around 2026.10.14–2026.10.15 alongside the new shim versioning check), invoking any CLI tool installed via mise through its shim causes an empty console window titled
mise.exeto pop up momentarily or persist.Steps to Reproduce
mise use -g uvormise use -g pi).PATH....\mise.exe.Expected Behavior
Shims should execute headlessly in the background and forward I/O cleanly within the parent terminal without spawning a separate visible console window (
conhost.exe).Actual Behavior
A blank console window opens targeting
...\.local\bin\mise.exe(see screenshot attached).Suspected Cause
When
mise-shim.exeinvokesmise.exeto resolve and launch the target runtime, it appears to call WindowsCreateProcess(or Rust'sstd::process::Command) without suppressing window creation flags (e.g. missingCREATE_NO_WINDOW/0x08000000or improper console handle inheritance when running under non-conhost terminals like mintty/PTY).All reactions