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

CMD Exit fails after running diskraid #17294

New Issue
Closed
opened 2026-01-31 05:38:06 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 05:38:06 +00:00
Owner
Copy Link

Originally created by @JustinWebDev on GitHub (Apr 20, 2022).

Windows Terminal version

1.12.10733.0

Windows build number

10.0.22000.613

Other Software

No response

Steps to reproduce

run Terminal as admin
issue cmd "diskraid"
issue cmd "exit"

Expected Behavior

the terminal to exit and close

Actual Behavior

C:\Users\hammack>exit
[process exited with code 4 (0x00000004)]

-> and it does not close

image

Originally created by @JustinWebDev on GitHub (Apr 20, 2022). ### Windows Terminal version 1.12.10733.0 ### Windows build number 10.0.22000.613 ### Other Software _No response_ ### Steps to reproduce run Terminal as admin issue cmd "diskraid" issue cmd "exit" ### Expected Behavior the terminal to exit and close ### Actual Behavior C:\Users\hammack>exit [process exited with code 4 (0x00000004)] -> and it does not close ![image](https://user-images.githubusercontent.com/40804543/164247685-29c32481-32db-475d-a3b4-0c6027cf99b1.png)
claunia commented 2026-01-31 05:38:08 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 20, 2022):

Please read the FAQs.

@zadjii-msft commented on GitHub (Apr 20, 2022): [Please read the FAQs.](https://github.com/microsoft/terminal/wiki/Frequently-Asked-Questions-(FAQ)#why-am-i-seeing-process-exited-with-code-)
claunia commented 2026-01-31 05:38:08 +00:00
Author
Owner
Copy Link

@JustinWebDev commented on GitHub (Apr 20, 2022):

This was incorrectly close. Windows Termainal didn't crash. The cmd failed, but WT is operational. This doesn't make sense. I could have 100 successful cmds after the failed one and you still block exit. Hmm.

@JustinWebDev commented on GitHub (Apr 20, 2022): This was incorrectly close. Windows Termainal didn't crash. The cmd failed, but WT is operational. This doesn't make sense. I could have 100 successful cmds after the failed one and you still block exit. Hmm.
claunia commented 2026-01-31 05:38:08 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 20, 2022):

No where in the "Why am I seeing [process exited with code ...]?" section does it talk about crashing...

The diskraid command returned a non-zero exit code. When you typed exit into cmd.exe, cmd.exe returned that exit code as it's own exit code. Because you've got the closeOnExit setting set to the default value of "graceful", the Terminal will only close the pane when the client app returns with a exit code of 0. So what you're seeing here is the Terminal informing you that the client application you launched (cmd.exe) returned a non-zero value (the 4 that was returned by diskraid).

Does that make sense?

@zadjii-msft commented on GitHub (Apr 20, 2022): No where in the "Why am I seeing `[process exited with code ...]`?" section does it talk about crashing... The diskraid command returned a non-zero exit code. When you typed `exit` into `cmd.exe`, `cmd.exe` returned that exit code as it's own exit code. Because you've got the `closeOnExit` setting set to the default value of `"graceful"`, the Terminal will only close the pane when the client app returns with a exit code of 0. So what you're seeing here is the Terminal informing you that the client application you launched (`cmd.exe`) returned a non-zero value (the `4` that was returned by `diskraid`). Does that make sense?
claunia commented 2026-01-31 05:38:09 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 21, 2022):

Sure okay - that's referring to the client commandline application crashing, not the terminal, and super not the point here 😉

@zadjii-msft commented on GitHub (Apr 21, 2022): Sure okay - that's referring to the client commandline application crashing, not the terminal, and super not the point here 😉
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 Issue-Question Needs-Tag-Fix Needs-Triage Resolution-Answered
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#17294
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?