[Bug] Windows 10: Constant console window popups and zombie node.exe processes #20814

Activity

1. github-actions

   added

   bugSomething isn't workingSomething isn't working

   has reproHas detailed reproduction stepsHas detailed reproduction steps

   platform:windowsIssue specifically occurs on WindowsIssue specifically occurs on Windows

   area:core

   on Jan 25, 2026
2. github-actions commented on Jan 25, 2026

   

   github-actionsbot

   on Jan 25, 2026 – with GitHub Actions

   More actions

   Found 3 possible duplicate issues:

   1. Windows: Console window flashing when executing tools #14828
   2. [BUG] windows popup issue #19391
   3. [BUG] orphaned processes from subagents crashing computer #18405

   This issue will be automatically closed as a duplicate in 3 days.

   • If your issue is a duplicate, please close it and 👍 the existing issue instead
   • To prevent auto-closure, add a comment or 👎 this comment

   🤖 Generated with Claude Code
3. mtsbh commented on Jan 26, 2026

   

   mtsbh

   on Jan 26, 2026

   More actions

   Same here. Its so annoying
4. jupe187 commented on Jan 28, 2026

   

   jupe187

   on Jan 28, 2026

   More actions

   Environment Details

   • OS: Windows 11
   • Claude Code: Using AWS Bedrock backend (eu.anthropic.claude-opus-4-5-20251101-v1:0)
   • Bash: Git Bash (user-level installation)
     • Path: C:\Users\<username>\AppData\Local\Programs\Git\bin\bash.exe
     • Note: Not a system-wide Git installation

   Symptoms

   Brief black console window flashes on every Bash tool invocation, including:

   • Simple commands (echo "test", ls)
   • Git commands (git --version, git config)
   • Any subprocess execution

   The flash occurs at process spawn time, before any command execution.

   Investigation Findings

   1. Not shell-config related: Tested with CLAUDE_BASH_NO_LOGIN=1 - popup still occurs
   2. Not Git-specific: Affects all bash commands equally
   3. Not plugin-related: No MCP servers actively spawning processes

   Likely Root Cause

   Node.js subprocess spawning is missing the windowsHide: true option in child_process.spawn() or exec() calls. On Windows, this option is required to prevent console window allocation for child
   processes.

   Example fix pattern:

   spawn('bash.exe', args, {
     windowsHide: true,  // <-- This suppresses the console flash
     // ... other options
   });
   
   Workarounds Attempted (Unsuccessful)
   ┌──────────────────────────────┬───────────────────────────────────────────────────┐
   │          Workaround          │                      Result                       │
   ├──────────────────────────────┼───────────────────────────────────────────────────┤
   │ CLAUDE_BASH_NO_LOGIN=1       │ No effect - flash occurs before shell init        │
   ├──────────────────────────────┼───────────────────────────────────────────────────┤
   │ Different terminal emulators │ No effect - issue is in Claude Code, not terminal │
   └──────────────────────────────┴───────────────────────────────────────────────────┘
   Impact
   
   - Cosmetic but disruptive during active development
   - Multiple flashes per conversation when Claude runs several commands
   - Makes screen recordings/demos look unprofessional
   
   Happy to provide debug logs or test patches if helpful!
   
   ---
5. mtsbh commented on Feb 4, 2026

   

   mtsbh

   on Feb 4, 2026

   More actions

   I think found a temporary fix. Setting up a new User Variable stops this behavior after you explicitly tell it where your shell is. Variable name: CLAUDE_CODE_GIT_BASH_PATH with value C:\Program Files\Git\bin\bash.exe managed to work for me. It just needs to be pointed to bin\bash.exe, not git-bash.exe.

   ❤️React with ❤️1Reacted by jupe187
6. github-actions

   added

   staleIssue is inactiveIssue is inactive

   on Feb 18, 2026
7. github-actions commented on Mar 5, 2026

   

   github-actionsbot

   on Mar 5, 2026 – with GitHub Actions

   More actions

   Closing for now — inactive for too long. Please open a new issue if this is still relevant.
8. github-actions

   closed this as not plannedon Mar 5, 2026
9. github-actions commented on Mar 14, 2026

   

   github-actionsbot

   on Mar 14, 2026 – with GitHub Actions

   More actions

   This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.
10. github-actions

    locked as resolved and limited conversation to collaborators on Mar 14, 2026