starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Opening a .lnk file from a .bat causes Terminal to become unresponsive #23574

New Issue
Closed
opened 2026-01-31 08:46:15 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 08:46:15 +00:00
Owner
Copy Link

Originally created by @Jlw111 on GitHub (Aug 30, 2025).

Windows Terminal version

1.23.12371.0

Windows build number

10.0.26100.5074

Other Software

No response

Steps to reproduce

Create a test folder. Inside this folder, create a batch file test_batch.bat with the following contents.

@ECHO OFF
start "" "test_shortcut.lnk"
timeout 5

Create a new shortcut inside this folder called test_shortcut.lnk. In the "start in" box, fill in the following:

%localappdata%\Microsoft\WindowsApps

In the "target" box, fill in the following:

%localappdata%\Microsoft\WindowsApps\wt.exe -w test_window --title "test_tab" cmd /c pause

Then, run the test_batch.bat file.

Expected Behavior

Batch file should start, open a new Terminal window with the "pause" command, and then close the originating window, leaving the "pause" command window running and able to be interacted with.

Actual Behavior

After the originating Terminal window closes itself (after the 5 second countdown), the window that it left behind becomes almost entirely unresponsive. It does not react to any mouse clicks, and resizing the window results does not work properly. Clicking the close button does work, but no updates are drawn to the window at any point. It does not show any further results of the process that would have been on screen.

https://github.com/user-attachments/assets/54b98f45-6d53-4e06-afa6-9d8aea295247

Originally created by @Jlw111 on GitHub (Aug 30, 2025). ### Windows Terminal version 1.23.12371.0 ### Windows build number 10.0.26100.5074 ### Other Software _No response_ ### Steps to reproduce Create a test folder. Inside this folder, create a batch file `test_batch.bat` with the following contents. ``` @ECHO OFF start "" "test_shortcut.lnk" timeout 5 ``` Create a new shortcut inside this folder called `test_shortcut.lnk`. In the "start in" box, fill in the following: ``` %localappdata%\Microsoft\WindowsApps ``` In the "target" box, fill in the following: ``` %localappdata%\Microsoft\WindowsApps\wt.exe -w test_window --title "test_tab" cmd /c pause ``` Then, run the `test_batch.bat` file. ### Expected Behavior Batch file should start, open a new Terminal window with the "pause" command, and then close the originating window, leaving the "pause" command window running and able to be interacted with. ### Actual Behavior After the originating Terminal window closes itself (after the 5 second countdown), the window that it left behind becomes almost entirely unresponsive. It does not react to any mouse clicks, and resizing the window results does not work properly. Clicking the close button does work, but no updates are drawn to the window at any point. It does not show any further results of the process that would have been on screen. https://github.com/user-attachments/assets/54b98f45-6d53-4e06-afa6-9d8aea295247
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 08:46:15 +00:00
claunia commented 2026-01-31 08:46:16 +00:00
Author
Owner
Copy Link

@denali999 commented on GitHub (Aug 31, 2025):

Seems like a regression from 1.22.11141.0. Works as expected on that version, and after updating to 1.23.12371.0 was able to reproduce

@denali999 commented on GitHub (Aug 31, 2025): Seems like a regression from `1.22.11141.0`. Works as expected on that version, and after updating to `1.23.12371.0` was able to reproduce
claunia commented 2026-01-31 08:46:16 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 3, 2025):

Whoa, great catch! We accidentally fixed this in #19298, which will be backported and released to 1.23 🔜

/dup #19298

@DHowett commented on GitHub (Sep 3, 2025): Whoa, great catch! We accidentally fixed this in #19298, which will be backported and released to 1.23 :soon: /dup #19298
claunia commented 2026-01-31 08:46:16 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Sep 3, 2025):

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!

@microsoft-github-policy-service[bot] commented on GitHub (Sep 3, 2025): 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! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#23574
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?