CMD mishandles app execution aliases when they're spawned from scripts #6603

Open
opened 2026-01-31 00:42:50 +00:00 by claunia · 0 comments
Owner

Originally created by @ablujay on GitHub (Feb 23, 2020).

Environment

Windows build number: 10.0.18363.657
Windows Terminal version (if applicable): 0.9.433.0

Steps to reproduce

  1. Create a cmd script that is meant to open windows terminal.
    (e.g. wt ; split-pane -p "Ubuntu" ; split-pane -p "Ubuntu" -H)

  2. Run the script by double-clicking on the file

Expected behavior

The script should run, open the configured windows terminal with 3-panes, and then the script should complete.

Actual behavior

The wt command does not seem to complete -- so both the cmd prompt and the newly created terminal are now open. The cmd prompt will close once the terminal window that was created is closed out.

Originally created by @ablujay on GitHub (Feb 23, 2020). Environment ```none Windows build number: 10.0.18363.657 Windows Terminal version (if applicable): 0.9.433.0 ``` # Steps to reproduce 1. Create a `cmd` script that is meant to open windows terminal. (e.g. `wt ; split-pane -p "Ubuntu" ; split-pane -p "Ubuntu" -H`) 2. Run the script by double-clicking on the file # Expected behavior The script should run, open the configured windows terminal with 3-panes, and then the script should complete. # Actual behavior The `wt` command does not seem to complete -- so both the cmd prompt and the newly created terminal are now open. The cmd prompt will close once the terminal window that was created is closed out.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6603