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

Process exits prematurely #23637

New Issue
Closed
opened 2026-01-31 08:47:52 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 08:47:52 +00:00
Owner
Copy Link

Originally created by @mikaele90 on GitHub (Sep 22, 2025).

Windows Terminal version

1.22.12111.0

Windows build number

10.0.26100.0

Other Software

7z, 64-bit x64, 25.01

Steps to reproduce

When running for example "Get-ChildItem -Recurse -Filter *.rar | ForEach-Object { 7z x $_.FullName -o"$($_.DirectoryName)" -y }" on an HDD that's under load, the process seems to be interpreted as "exited" way before the loop is complete.

The archives were in the 5-7GB range.

With default settings I got only one successful extraction done out of 20.

After setting profile termination behavior to "Never close automatically" and allowed it to run in the background in installed apps as "Always", I got two successful extractions before it exited.

Expected Behavior

Turned all the knobs to what I'd imagine should work;

  • Enabled "Run this profile as Administrator"
  • Disabled "Automatically mark prompts on pressing Enter"
  • Disabled "Launch this application with a new environment block"

And... It worked. All extractions finished as they should have.

Either way, it seems like there might be a bug here. Perhaps induced by the slower response time of the HDD under existing load.

Actual Behavior

Process terminates prematurely.

Originally created by @mikaele90 on GitHub (Sep 22, 2025). ### Windows Terminal version 1.22.12111.0 ### Windows build number 10.0.26100.0 ### Other Software 7z, 64-bit x64, 25.01 ### Steps to reproduce When running for example "`Get-ChildItem -Recurse -Filter *.rar | ForEach-Object { 7z x $_.FullName -o"$($_.DirectoryName)" -y }`" on an HDD that's under load, the process seems to be interpreted as "exited" way before the loop is complete. The archives were in the 5-7GB range. With default settings I got only one successful extraction done out of 20. After setting profile termination behavior to "Never close automatically" and allowed it to run in the background in installed apps as "Always", I got two successful extractions before it exited. ### Expected Behavior Turned all the knobs to what I'd imagine should work; - Enabled "Run this profile as Administrator" - Disabled "Automatically mark prompts on pressing Enter" - Disabled "Launch this application with a new environment block" And... It worked. All extractions finished as they should have. Either way, it seems like there might be a bug here. Perhaps induced by the slower response time of the HDD under existing load. ### Actual Behavior Process terminates prematurely.
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 08:47:52 +00:00
claunia commented 2026-01-31 08:47:54 +00:00
Author
Owner
Copy Link

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

Is it Terminal which is exiting, PowerShell or 7-zip? Or, perhaps, OpenConsole (our console hosting process)? Do you have any event viewer logs about the four of these?

FWIW, the "never close ..." setting should always leave you with an open window with an error code in it. If it leaves you with no window, that's Terminal exiting or crashing. It should do neither in this case.

All of the "close on exit" settings only take effect when the process hosted within Terminal has exited on its own. We never ourselves time out a process or manage its lifetime in any way other than starting it.

@DHowett commented on GitHub (Sep 22, 2025): Is it _Terminal_ which is exiting, PowerShell or 7-zip? Or, perhaps, OpenConsole (our console hosting process)? Do you have any event viewer logs about the four of these? FWIW, the "never close ..." setting should always leave you with an open window with an error code in it. If it leaves you with no window, that's Terminal exiting or crashing. It should do neither in this case. All of the "close on exit" settings only take effect when the process hosted within Terminal has exited on its own. We never _ourselves_ time out a process or manage its lifetime in any way other than starting it.
claunia commented 2026-01-31 08:47:54 +00:00
Author
Owner
Copy Link

@mikaele90 commented on GitHub (Sep 23, 2025):

Turns out that the terminal had to be launched as an administrator to have the entire process complete successfully. The weird part really is how sometimes it got two archives extracted instead of just one (as I was writing this I got one run to 3 archives completed). My guess is 7z is the culprit, even though I've had random terminations of terminal windows running powershell in the last few days (instances that have only just been launched less than a minute ago, with nothing running yet).

Right now the terminal just leaves this code and message for me, when a process does not finish successfully:
[process exited with code 1 (0x00000001)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

Nothing obvious in the event viewer, but I also might not be looking in the right place to find the correct logs.

Sorry, if this is wasting your time. At this point I doubt Terminal itself is the culprit, might be either 7z or powershell. Unfortunately I don't know enough about OpenConsole to diagnose problems with it, if there are any.

Edit: Right after typing this I got one of those instances, where a process terminates, without me having done anything yet. Basically just:
PS N:\launch-location>
[process exited with code 1 (0x00000001)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

@mikaele90 commented on GitHub (Sep 23, 2025): Turns out that the terminal had to be launched as an administrator to have the entire process complete successfully. The weird part really is how sometimes it got two archives extracted instead of just one (as I was writing this I got one run to 3 archives completed). My guess is 7z is the culprit, even though I've had random terminations of terminal windows running powershell in the last few days (instances that have only just been launched less than a minute ago, with nothing running yet). Right now the terminal just leaves this code and message for me, when a process does not finish successfully: _[process exited with code 1 (0x00000001)] You can now close this terminal with Ctrl+D, or press Enter to restart._ Nothing obvious in the event viewer, but I also might not be looking in the right place to find the correct logs. Sorry, if this is wasting your time. At this point I doubt Terminal itself is the culprit, might be either 7z or powershell. Unfortunately I don't know enough about OpenConsole to diagnose problems with it, if there are any. Edit: Right after typing this I got one of those instances, where a process terminates, without me having done anything yet. Basically just: _PS N:\launch-location> [process exited with code 1 (0x00000001)] You can now close this terminal with Ctrl+D, or press Enter to restart._
claunia commented 2026-01-31 08:47:54 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 15, 2025):

Thanks for following up! We're still stumped and don't think it's on our end, but I do think there's some tracing we can do to get closer to a root cause...

Would you be able to follow the steps at https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capturing-a-debug-etl-trace and get it to happen again?

If you were to run PowerShell without Terminal (by running conhost powershell (or conhost pwsh if that is your persuasion) or by changing your default terminal app back to "Windows Console Host"), does it happen? Over there it would manifest as the window closing with little additional ceremony.

@DHowett commented on GitHub (Oct 15, 2025): Thanks for following up! We're still stumped and don't think it's on our end, but I do think there's some tracing we can do to get closer to a root cause... Would you be able to follow the steps at https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capturing-a-debug-etl-trace and get it to happen again? If you were to run PowerShell _without_ Terminal (by running `conhost powershell` (or `conhost pwsh` if that is your persuasion) or by changing your default terminal app back to "Windows Console Host"), does it happen? Over there it would manifest as the window closing with little additional ceremony.
claunia commented 2026-01-31 08:47:55 +00:00
Author
Owner
Copy Link

@mikaele90 commented on GitHub (Oct 15, 2025):

Unfortunately, I already did a fresh install of Windows (not because of this), which unsurprisingly solved the issue. I think this issue can be closed, but I'll be sure to follow the steps in the guide and report back if the issue ever returns.

@mikaele90 commented on GitHub (Oct 15, 2025): Unfortunately, I already did a fresh install of Windows (not because of this), which unsurprisingly solved the issue. I think this issue can be closed, but I'll be sure to follow the steps in the guide and report back if the issue ever returns.
claunia commented 2026-01-31 08:47:55 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 16, 2025):

I'll be closing this issue for now then.

@lhecker commented on GitHub (Oct 16, 2025): I'll be closing this issue for now then.
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 Needs-Attention Needs-Triage
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#23637
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?