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

PowerShell tabs often stop with "process exited with code 5" #13653

New Issue
Closed
opened 2026-01-31 03:48:30 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 03:48:30 +00:00
Owner
Copy Link

Originally created by @SpitFire-666 on GitHub (Apr 28, 2021).

Windows Terminal version (or Windows build number)

1.7.1033.0

Other Software

OneDrive

Steps to reproduce

(I think this is what's happening)

  1. Have OneDrive installed/signed in
  2. Open a bunch of PowerShell tabs and CD to your OneDrive ( cd $env:\Onedrive )
  3. Open a PowerShell tab and CD to C:\ drive
  4. Put computer to sleep/hibernate
  5. Wake the computer

Expected Behavior

PowerShell tabs should remain available for use

Actual Behavior

The PowerShell tabs in the OneDrive path display
[process exited with code 5]

image

The busted tab will no longer receive any input.

Note that a normal PowerShell window seems unaffected.

Originally created by @SpitFire-666 on GitHub (Apr 28, 2021). ### Windows Terminal version (or Windows build number) 1.7.1033.0 ### Other Software OneDrive ### Steps to reproduce (I **think** this is what's happening) 1. Have OneDrive installed/signed in 2. Open a bunch of PowerShell tabs and CD to your OneDrive ( `cd $env:\Onedrive` ) 3. Open a PowerShell tab and CD to C:\ drive 3. Put computer to sleep/hibernate 4. Wake the computer ### Expected Behavior PowerShell tabs should remain available for use ### Actual Behavior The PowerShell tabs in the OneDrive path display `[process exited with code 5]` ![image](https://user-images.githubusercontent.com/38451588/116356068-1b09d500-a83e-11eb-9489-c753f718ddc4.png) The busted tab will no longer receive any input. Note that a normal PowerShell window seems unaffected.
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 03:48:30 +00:00
claunia commented 2026-01-31 03:48:31 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Apr 28, 2021):

This feels like a PowerShell issue for me, since we really don't control when & how the shell exits.

@skyline75489 commented on GitHub (Apr 28, 2021): This feels like a PowerShell issue for me, since we really don't control when & how the shell exits.
claunia commented 2026-01-31 03:48:31 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 29, 2021):

I'm guessing that this is because the OneDrive filter driver is disconnected and as part of that, any process holding a handle to that path is killed. There's nothing we can do about this[1].

If you wouldn't mind filing feedback on OneDrive (and possibly sharing the link here,) that would be lovely.

Thanks!

1: Traditionally, console applications would just disappear when they were killed. Terminal at least warns you! 😄

@DHowett commented on GitHub (Apr 29, 2021): I'm guessing that this is because the OneDrive filter driver is disconnected and as part of that, any process holding a handle to that path is killed. There's nothing we can do about this[1]. If you wouldn't mind filing feedback on OneDrive (and possibly sharing the link here,) that would be lovely. Thanks! 1: Traditionally, console applications would just disappear when they were killed. Terminal at least warns you! :smile:
claunia commented 2026-01-31 03:48:31 +00:00
Author
Owner
Copy Link

@SpitFire-666 commented on GitHub (Apr 30, 2021):

Hi @DHowett I can definitely provide feedback to OneDrive however I still find it odd that a normal PowerShell window does not suffer from this problem and remains responsive after sleep/wake (unlike the Terminal tab). Thoughts?

@SpitFire-666 commented on GitHub (Apr 30, 2021): Hi @DHowett I can definitely provide feedback to OneDrive however I still find it odd that a normal PowerShell window does not suffer from this problem and remains responsive after sleep/wake (unlike the Terminal tab). Thoughts?
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-Question Needs-Tag-Fix 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#13653
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?