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

Batch file issues #17324

New Issue
Closed
opened 2026-01-31 05:39:12 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 05:39:12 +00:00
Owner
Copy Link

Originally created by @RichardD2 on GitHub (Apr 22, 2022).

Windows Terminal version

1.12.10983.0

Windows build number

10.0.22000.0

Other Software

Windows 11 File Explorer

Steps to reproduce

Set the default shell terminal to Windows Terminal.

Create a batch file which executes multiple robocopy commands.

Find the folder in Windows Explorer, and double-click the batch file.

Expected Behavior

The batch file should run to completion, and the terminal should either close or display the "process exited with code ..." message.

The robocopy output should fill the visible screen before scrolling off the top.

Actual Behavior

If there are changes for the first robocopy to replicate, the batch file seems to be terminated part-way through a subsequent robocopy command.

The output often only occupies the first couple of lines of the visible window. It never fills the screen.

Originally created by @RichardD2 on GitHub (Apr 22, 2022). ### Windows Terminal version 1.12.10983.0 ### Windows build number 10.0.22000.0 ### Other Software Windows 11 File Explorer ### Steps to reproduce Set the default shell terminal to Windows Terminal. Create a batch file which executes multiple `robocopy` commands. Find the folder in Windows Explorer, and double-click the batch file. ### Expected Behavior The batch file should run to completion, and the terminal should either close or display the "process exited with code ..." message. The `robocopy` output should fill the visible screen before scrolling off the top. ### Actual Behavior If there are changes for the first `robocopy` to replicate, the batch file seems to be terminated part-way through a subsequent `robocopy` command. The output often only occupies the first couple of lines of the visible window. It never fills the screen.
claunia commented 2026-01-31 05:39:14 +00:00
Author
Owner
Copy Link

@AlanJWoodward commented on GitHub (Apr 22, 2022):

Also suffering from this exact issue.

Windows Terminal version: 10.12.10983.0 (updated on 21st April 2022)
Widows OS build no: 22000.613

The issue didn't exist before upgrading to 10.12.10983.0

When running the batch file with robocopy, the batch file will stop at a random point and display:

[process exited with code 1 (0x00000001)]

Will run satisfactorily for one run, then fail.

@AlanJWoodward commented on GitHub (Apr 22, 2022): Also suffering from this exact issue. Windows Terminal version: 10.12.10983.0 (updated on 21st April 2022) Widows OS build no: 22000.613 The issue didn't exist before upgrading to 10.12.10983.0 When running the batch file with robocopy, the batch file will stop at a random point and display: [process exited with code 1 (0x00000001)] Will run satisfactorily for one run, then fail.
claunia commented 2026-01-31 05:39:14 +00:00
Author
Owner
Copy Link

@arthurcaccavo commented on GitHub (Jul 4, 2022):

same problem when running ant commands

@arthurcaccavo commented on GitHub (Jul 4, 2022): same problem when running ant commands
claunia commented 2026-01-31 05:39:14 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 1, 2022):

This is bizarre - there's something similar in #13185 but I honestly can't repro this. Maybe it's just my build (both of the OS and the Terminal)?

That thread has a more minimal repro in it (rather than some specific robocopy commands). Anyone in this thread who was seeing this - does the minimal repro also cause the same thing for you (on a 1.14/1.15 Terminal)/?

@zadjii-msft commented on GitHub (Aug 1, 2022): This is bizarre - there's something similar in #13185 but I honestly can't repro this. Maybe it's just my build (both of the OS and the Terminal)? That thread has a more minimal repro in it (rather than some specific robocopy commands). Anyone in this thread who was seeing this - does the minimal repro also cause the same thing for you (on a 1.14/1.15 Terminal)/?
claunia commented 2026-01-31 05:39:15 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 5, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Aug 5, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 05:39:15 +00:00
Author
Owner
Copy Link

@AlanJWoodward commented on GitHub (Aug 5, 2022):

I'll check that out and get back to you soon.

@AlanJWoodward commented on GitHub (Aug 5, 2022): I'll check that out and get back to you soon.
claunia commented 2026-01-31 05:39:15 +00:00
Author
Owner
Copy Link

@AlanJWoodward commented on GitHub (Aug 5, 2022):

OK, so it does look as if the issue has now been fixed (unable to now reproduce with the ren files batch files, or my robocopy batch files).

I hadn't tried my robocopy commands in Terminal since it stopped working for me, but it looks like 1.14.11963.0 now works as it used to do before 1.12.10983.0 broke it.

The part screen loading also looks fixed too.

@AlanJWoodward commented on GitHub (Aug 5, 2022): OK, so it does look as if the issue has now been fixed (unable to now reproduce with the ren files batch files, or my robocopy batch files). I hadn't tried my robocopy commands in Terminal since it stopped working for me, but it looks like 1.14.11963.0 now works as it used to do before 1.12.10983.0 broke it. The part screen loading also looks fixed too.
claunia commented 2026-01-31 05:39:15 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 5, 2022):

That's great, thanks for confirming! Who knows what part of the last few months fixed it, but I'm glad it's sorted out!

@zadjii-msft commented on GitHub (Aug 5, 2022): That's great, thanks for confirming! Who knows what part of the last few months fixed it, but I'm glad it's sorted out!
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 Area-DefApp Issue-Bug Needs-Author-Feedback Needs-Tag-Fix Needs-Triage Resolution-No-Repro
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#17324
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?