starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 16:05:21 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Windows terminal crashes suddenly without any visual output #17671

New Issue
Closed
opened 2026-01-31 05:49:41 +00:00 by claunia · 12 comments
claunia commented 2026-01-31 05:49:41 +00:00
Owner
Copy Link

Originally created by @ThakurKarthik on GitHub (Jun 10, 2022).

Windows Terminal version

1.13.11431.0

Windows build number

10.0.19043.0

Other Software

No response

Steps to reproduce

Ok I can help better if you can guide me on how to give you any error logs. But right now the issue is that windows terminal just closes/crashes without any error feedback. My use case is simple I open the terminal and navigate to some path and open vscode and I keep the terminal open to run some npm commands. I am not sure when but the terminal crashes if I have one or two or multiple tabs open at once.

Expected Behavior

Windows terminal should not crash as I change to multiple directories and if it crashes then I have to open the terminal again and navigate to those paths again.

Actual Behavior

As I mentioned the terminal window crashes

Originally created by @ThakurKarthik on GitHub (Jun 10, 2022). ### Windows Terminal version 1.13.11431.0 ### Windows build number 10.0.19043.0 ### Other Software _No response_ ### Steps to reproduce Ok I can help better if you can guide me on how to give you any error logs. But right now the issue is that windows terminal just closes/crashes without any error feedback. My use case is simple I open the terminal and navigate to some path and open vscode and I keep the terminal open to run some npm commands. I am not sure when but the terminal crashes if I have one or two or multiple tabs open at once. ### Expected Behavior Windows terminal should not crash as I change to multiple directories and if it crashes then I have to open the terminal again and navigate to those paths again. ### Actual Behavior As I mentioned the terminal window crashes
claunia commented 2026-01-31 05:49:43 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 10, 2022):

If you've got a consistent repro, then the Feedback Hub should be able to capture the crash dump. /feedback

@zadjii-msft commented on GitHub (Jun 10, 2022): If you've got a consistent repro, then the Feedback Hub should be able to capture the crash dump. /feedback
claunia commented 2026-01-31 05:49:43 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 10, 2022):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?

Thanks!

image

image

image

@ghost commented on GitHub (Jun 10, 2022): Hi there!<br><br>Can you please send us feedback with the [Feedback Hub](https://support.microsoft.com/en-us/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332) with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18356694/140811502-a068f78b-89d2-4587-925a-73e19652b830.png)<br><br>![image](https://user-images.githubusercontent.com/18356694/140811557-cdc22a0f-fa6a-4f6a-953e-73b51f5548a3.png)<br><br>![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-31 05:49:44 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 14, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jun 14, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 05:49:44 +00:00
Author
Owner
Copy Link

@ThakurKarthik commented on GitHub (Jun 15, 2022):

The issue is intermittent, feel free to close it for now. I will reopen it back when I can reproduce the issue.

@ThakurKarthik commented on GitHub (Jun 15, 2022): The issue is intermittent, feel free to close it for now. I will reopen it back when I can reproduce the issue.
claunia commented 2026-01-31 05:49:44 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 15, 2022):

Thanks!

@zadjii-msft commented on GitHub (Jun 15, 2022): Thanks!
claunia commented 2026-01-31 05:49:44 +00:00
Author
Owner
Copy Link

@ThakurKarthik commented on GitHub (Jun 22, 2022):

@zadjii-msft I was able to run the feedback hub recording and (un)fortunately the terminal crashed too, here is the link https://aka.ms/AAh9yy4 Let me know if you need any thing

@ThakurKarthik commented on GitHub (Jun 22, 2022): @zadjii-msft I was able to run the feedback hub recording and (un)fortunately the terminal crashed too, here is the link https://aka.ms/AAh9yy4 Let me know if you need any thing
claunia commented 2026-01-31 05:49:45 +00:00
Author
Owner
Copy Link

@ThakurKarthik commented on GitHub (Jul 5, 2022):

@zadjii-msft any progress over here ?

@ThakurKarthik commented on GitHub (Jul 5, 2022): @zadjii-msft any progress over here ?
claunia commented 2026-01-31 05:49:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 5, 2022):

Sorry, was out on vacation. Just catching up now.

The only crash I'm seeing is for something called AW.WinPC.Updater.exe - any chance you've got something called "Air Watch" installed? I honestly have no idea what that is or why that crashing would bring down the Terminal. Unfortunately, there wasn't really anything else that the Feedback Hub captured about the Terminal, so it seems to suggest that the problem lies outside the Terminal itself...

@zadjii-msft commented on GitHub (Jul 5, 2022): Sorry, was out on vacation. Just catching up now. The only crash I'm seeing is for something called `AW.WinPC.Updater.exe` - any chance you've got something called "Air Watch" installed? I honestly have no idea what that is or why that crashing would bring down the Terminal. Unfortunately, there wasn't really anything else that the Feedback Hub captured about the Terminal, so it seems to suggest that the problem lies outside the Terminal itself...
claunia commented 2026-01-31 05:49:45 +00:00
Author
Owner
Copy Link

@simeyla commented on GitHub (Sep 23, 2023):

I've given up on using Terminal since it just crashes and disappears leaving processes still running.
I'm sure it's happening when memory is low, but that's no excuse. I just look for it and it's gone.

I never seem to see anything in EventLog but that doesn't necessarily mean anything since I don't immediately always notice or look.

@simeyla commented on GitHub (Sep 23, 2023): I've given up on using Terminal since it just crashes and disappears leaving processes still running. I'm sure it's happening when memory is low, but that's no excuse. I just look for it and it's gone. I never seem to see anything in EventLog but that doesn't necessarily mean anything since I don't immediately always notice or look.
claunia commented 2026-01-31 05:49:45 +00:00
Author
Owner
Copy Link

@kentcb commented on GitHub (Nov 24, 2023):

I'm about to give up too, found this issue when searching for answers. It's happened to me twice today: two separate terminal windows open, each with several tabs. They just disappear without any feedback at all (except I notice things in my dev process stop working, since processes in those terminals are critical).

It's kind of silly that one must be recording to capture the problem, since the problem appears completely random in nature. There should be some kind of ability to turn on a log so one can check retrospectively what caused the crash.

@kentcb commented on GitHub (Nov 24, 2023): I'm about to give up too, found this issue when searching for answers. It's happened to me twice today: two separate terminal windows open, each with several tabs. They just disappear without any feedback at all (except I notice things in my dev process stop working, since processes in those terminals are critical). It's kind of silly that one must be recording to capture the problem, since the problem appears completely random in nature. There should be some kind of ability to turn on a log so one can check retrospectively what caused the crash.
claunia commented 2026-01-31 05:49:46 +00:00
Author
Owner
Copy Link

@omair2084 commented on GitHub (Mar 5, 2024):

I experienced the same and landed here.
So, for me the issue is actually automatic updates to the Terminal which causes this problem.
image

I don't click on any update button as in #6726 . As seen from the screenshot, this happened around 2am.

@omair2084 commented on GitHub (Mar 5, 2024): I experienced the same and landed here. So, for me the issue is actually automatic updates to the Terminal which causes this problem. ![image](https://github.com/microsoft/terminal/assets/18167139/6b809201-cdc3-4b4d-ab8d-539ccfd1e131) I don't click on any update button as in #6726 . As seen from the screenshot, this happened around 2am.
claunia commented 2026-01-31 05:49:46 +00:00
Author
Owner
Copy Link

@CrazySqueak commented on GitHub (Mar 11, 2025):

I have this issue as well.

Found this in Event Viewer > Windows Logs > System:
Image

I did not click any "update now" button or anything like that. I had processes running that I'd prefer weren't interrupted abruptly by the system.
Luckily I was only idling for 20 minutes or so before realising it had stopped, and luckily it was able to be resumed once I manually re-opened the terminal and re-ran the command.

Windows version:
Windows 10 Home (x64)
Version 10.0.19045 Build 19045

Terminal version:
Before update: not sure.
After update: 1.21.10351.0

@CrazySqueak commented on GitHub (Mar 11, 2025): I have this issue as well. Found this in Event Viewer > Windows Logs > System: ![Image](https://github.com/user-attachments/assets/4cc9dd8a-b3e1-4e36-b8d4-504f848ce92a) I did not click any "update now" button or anything like that. I had processes running that I'd prefer weren't interrupted abruptly by the system. Luckily I was only idling for 20 minutes or so before realising it had stopped, and luckily it was able to be resumed once I manually re-opened the terminal and re-ran the command. Windows version: Windows 10 Home (x64) Version 10.0.19045 Build 19045 Terminal version: Before update: not sure. After update: 1.21.10351.0
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-Repro Needs-Tag-Fix Needs-Triage Resolution-No-Repro
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#17671
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?