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

"cmd.exe" does not exit the terminal properly if the last command didn't exit with 0 #18261

New Issue
Closed
opened 2026-01-31 06:08:26 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 06:08:26 +00:00
Owner
Copy Link

Originally created by @dovholuknf on GitHub (Aug 22, 2022).

Windows Terminal version

1.14.1963.0

Windows build number

No response

Other Software

cme.exe - whatever comes with windows 11 latest

Steps to reproduce

  • set windows terminal preview as the default terminal application and save that setting
  • hit the start key
  • type: cmd.exe [enter] (to open "Command Prompt - App")
  • type: type bob
  • i expect you'll see: "The system cannot find the file specified."
  • type: exit

Expected Behavior

the terminal should exit

Actual Behavior

the terminal stays alive indicating:

C:\Users\user_name>exit

[process exited with code 1 (0x00000001)]
Originally created by @dovholuknf on GitHub (Aug 22, 2022). ### Windows Terminal version 1.14.1963.0 ### Windows build number _No response_ ### Other Software cme.exe - whatever comes with windows 11 latest ### Steps to reproduce * set windows terminal preview as the default terminal application and save that setting * hit the start key * type: cmd.exe [enter] (to open "Command Prompt - App") * type: type bob * i expect you'll see: "The system cannot find the file specified." * type: exit ### Expected Behavior the terminal should exit ### Actual Behavior the terminal stays alive indicating: ``` C:\Users\user_name>exit [process exited with code 1 (0x00000001)] ```
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:08:27 +00:00
claunia commented 2026-01-31 06:08:28 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 22, 2022):

Thanks for the report! This has been fixed as of 1.15 builds 200x+. /dup #13325.

@DHowett commented on GitHub (Aug 22, 2022): Thanks for the report! This has been fixed as of 1.15 builds 200x+. /dup #13325.
claunia commented 2026-01-31 06:08:28 +00:00
Author
Owner
Copy Link

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

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!

@ghost commented on GitHub (Aug 22, 2022): 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!
claunia commented 2026-01-31 06:08:28 +00:00
Author
Owner
Copy Link

@dovholuknf commented on GitHub (Aug 23, 2022):

image

the steps to report a bug are incorrect if you're using the terminal preview. turns out i am running 1.15.2003.0 and the bug is most definitely still present

@dovholuknf commented on GitHub (Aug 23, 2022): ![image](https://user-images.githubusercontent.com/46322585/186146746-f3ee394a-fd2e-4c42-96d1-f65e4093a14c.png) the steps to report a bug are incorrect if you're using the terminal preview. turns out i am running 1.15.2003.0 and the bug is most definitely still present
claunia commented 2026-01-31 06:08:29 +00:00
Author
Owner
Copy Link

@dovholuknf commented on GitHub (Aug 23, 2022):

@DHowett - would you mind reopening/retriaging this bug? or i can just file another if i have to?

@dovholuknf commented on GitHub (Aug 23, 2022): @DHowett - would you mind reopening/retriaging this bug? or i can just file another if i have to?
claunia commented 2026-01-31 06:08:29 +00:00
Author
Owner
Copy Link

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

Sorry, more correctly, this is fixed in Preview v1.15.228, which should also be appearing by default on some set of stable builds also, but those haven't been spun up quite yet.

It's enabled by a small change to the closeOnExit setting, which might have already been persisted as graceful in your settings. After #13560 is released, the new default should be automatic, which will do what you want. Till then, you can use closeOnExit: always

@zadjii-msft commented on GitHub (Aug 23, 2022): Sorry, more correctly, this is fixed in `Preview v1.15.228`, which should also be appearing by default on some set of stable builds also, but those haven't been spun up quite yet. It's enabled by a small change to the `closeOnExit` setting, which might have already been persisted as `graceful` in your settings. After #13560 is released, the new default should be `automatic`, which will do what you want. Till then, you can use `closeOnExit: always`
claunia commented 2026-01-31 06:08:30 +00:00
Author
Owner
Copy Link

@dovholuknf commented on GitHub (Aug 23, 2022):

Good grief - I had found/used closeOnExit": "always" for other profiles but didn't apply it to 'defaults"... Which i just rectified, thanks!

        "defaults": 
        {
            "closeOnExit": "always",
            ...
            ...
@dovholuknf commented on GitHub (Aug 23, 2022): Good grief - I had found/used `closeOnExit": "always"` for other profiles but didn't apply it to `'defaults"`... Which i just rectified, thanks! ``` "defaults": { "closeOnExit": "always", ... ... ```
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#18261
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?