starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-15 13:46:07 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Windows Terminal does not respond after VGA driver crash #14101

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

Originally created by @MPeti1 on GitHub (Jun 3, 2021).

Windows Terminal version (or Windows build number)

1.8.1444

Other Software

No response

Steps to reproduce

  1. Get a VGA that's nearing it's life's end
  2. Use the terminal as you would.
  3. When the VGA driver restarts, see that Windows terminal first becomes slower to respond, and then get greyed out.

Expected Behavior

Windows Terminal should try to recover from this error.

Actual Behavior

Windows Terminal keeps running, for example I can still see in the greyed out window as the command output (over SSH) is scrolling, but since Windows perceives that WT is not responding, I can not send any input to either the open terminals, nor to the WT window controls themselves.

An interesting detail is that after the VGA driver recovers, the WT windows (I usually have 2) are

  • not freezing immediately, and can be controlled for a few seconds, but at this time they become laggy
  • not freezing at the exact same time

Additional notes:
I agree that this is not an ideal situation that the user's VGA is crashing, but

  • I sadly can't replace it currently
  • other graphics software has added features so they can recover (I think I read it in OBS's changelog, and one another software I don't remember now)

So I understand it if this is not a priority for now, but I think it would be nice if WT could recover (especially because it still keeps working in the background, just half of the front of it crashed, and this makes the user lose several tabs of terminal sessions)

Originally created by @MPeti1 on GitHub (Jun 3, 2021). ### Windows Terminal version (or Windows build number) 1.8.1444 ### Other Software _No response_ ### Steps to reproduce 1. Get a VGA that's nearing it's life's end 2. Use the terminal as you would. 3. When the VGA driver restarts, see that Windows terminal first becomes slower to respond, and then get greyed out. ### Expected Behavior Windows Terminal should try to recover from this error. ### Actual Behavior Windows Terminal keeps running, for example I can still see in the greyed out window as the command output (over SSH) is scrolling, but since Windows perceives that WT is not responding, I can not send any input to either the open terminals, nor to the WT window controls themselves. An interesting detail is that after the VGA driver recovers, the WT windows (I usually have 2) are - not freezing immediately, and can be controlled for a few seconds, but at this time they become laggy - not freezing at the exact same time Additional notes: I agree that this is not an ideal situation that the user's VGA is crashing, but - I sadly can't replace it currently - other graphics software has added features so they can recover (I think I read it in OBS's changelog, and one another software I don't remember now) So I understand it if this is not a priority for now, but I think it would be nice if WT could recover (especially because it still keeps working in the background, just half of the front of it crashed, and this makes the user lose several tabs of terminal sessions)
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 Area-Rendering Needs-Attention Needs-Tag-Fix Needs-Triage Product-Terminal Severity-Crash
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#14101
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?