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

Process exists with code 1 if RDP session closes #22467

New Issue
Open
opened 2026-01-31 08:14:18 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 08:14:18 +00:00
Owner
Copy Link

Originally created by @NeilMacMullen on GitHub (Oct 30, 2024).

Windows Terminal version

1.21.2911.0

Windows build number

Win32NT 10.0.26100.0 Microsoft Windows NT 10.0.26100.0

Other Software

I was RDP'd into my work PC from home and switched focus to an existing Windows Terminal session running on the remote PC. The session had open tabs, all running powershell and I used a couple of them to issue commands, leaving them all at the prompt.

I put the home machine to sleep without explicitly closing the RDP session.

When I logged into the work PC at work, I discovered that all windows terminal tabs including one I had not used were showing the error

[process exited with code 1 (0x00000001)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

The screenshot below shows 2 distinct terminal sessions on the same machine. Every tab within these sessions shows the "process exited" method.

Image

The terminal tab will restart the powershell session if RETURN is pressed....

Image

Steps to reproduce

Still investigating.... possibly abnormal disconnect from RDP

Expected Behavior

Terminals should not exit processes simply because a remote session is lost.

Actual Behavior

Processes were exited

Originally created by @NeilMacMullen on GitHub (Oct 30, 2024). ### Windows Terminal version 1.21.2911.0 ### Windows build number Win32NT 10.0.26100.0 Microsoft Windows NT 10.0.26100.0 ### Other Software I was RDP'd into my work PC from home and switched focus to an existing Windows Terminal session running on the remote PC. The session had open tabs, all running powershell and I used a couple of them to issue commands, leaving them all at the prompt. I put the home machine to sleep without explicitly closing the RDP session. When I logged into the work PC at work, I discovered that _all_ windows terminal tabs including one I had not used were showing the error ``` [process exited with code 1 (0x00000001)] You can now close this terminal with Ctrl+D, or press Enter to restart. ``` The screenshot below shows 2 distinct terminal sessions on the same machine. Every tab within these sessions shows the "process exited" method. ![Image](https://github.com/user-attachments/assets/bf87ba79-5ce9-4468-b796-e76300a08668) The terminal tab will restart the powershell session if RETURN is pressed.... ![Image](https://github.com/user-attachments/assets/b351789f-73a9-4e56-90f7-82551faac502) ### Steps to reproduce Still investigating.... possibly abnormal disconnect from RDP ### Expected Behavior Terminals should not exit processes simply because a remote session is lost. ### Actual Behavior Processes were exited
claunia added the Needs-TriageIssue-BugNeeds-Author-FeedbackNo-Recent-Activity labels 2026-01-31 08:14:19 +00:00
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-Author-Feedback Needs-Triage No-Recent-Activity
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#22467
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?