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

Serious freeze when opening first Terminal window #23024

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

Originally created by @PaszaVonPomiot on GitHub (Mar 14, 2025).

Windows Terminal version

1.21.10351.0

Windows build number

10.0.22631.0

Other Software

No response

Steps to reproduce

  1. Install terminal from Windows Store
  2. Open terminal from start menu

Expected Behavior

No freezes, no blackouts

Actual Behavior

After starting first Terminal window for about 10 seconds there is a serious freeze including:

  • terminal window freeze
  • mouse cursor freeze
  • total screen blackout
    Image

After freeze ends I can open new tabs or new Terminal window without another freeze. But when I close all Terminals then again the first will be affected by that freeze.

Changing default profile to Command Prompt doesn't stop those freezes.

This might be fresh bug as there is similar report on the superuser:
https://superuser.com/questions/1884604/launching-windows-terminal-freezes-the-os-for-several-seconds?newreg=46c574e06a0747edb57eb0fe7ccfe391

Originally created by @PaszaVonPomiot on GitHub (Mar 14, 2025). ### Windows Terminal version 1.21.10351.0 ### Windows build number 10.0.22631.0 ### Other Software _No response_ ### Steps to reproduce 1. Install terminal from Windows Store 2. Open terminal from start menu ### Expected Behavior No freezes, no blackouts ### Actual Behavior After starting first Terminal window for about 10 seconds there is a serious freeze including: - terminal window freeze - mouse cursor freeze - total screen blackout ![Image](https://github.com/user-attachments/assets/5c65c49f-b64d-4166-ac7e-d9c0195d940b) After freeze ends I can open new tabs or new Terminal window without another freeze. But when I close all Terminals then again the first will be affected by that freeze. Changing default profile to Command Prompt doesn't stop those freezes. This might be fresh bug as there is similar report on the superuser: https://superuser.com/questions/1884604/launching-windows-terminal-freezes-the-os-for-several-seconds?newreg=46c574e06a0747edb57eb0fe7ccfe391
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:30:12 +00:00
claunia commented 2026-01-31 08:30:13 +00:00
Author
Owner
Copy Link

@rdoursenaud commented on GitHub (Mar 15, 2025):

I have the same problem and tracked it down to a video acceleration bug with Optimus (Intel + nVidia graphics).

Setting the GPU preference to Intel solves the issue for me.

The clue was my screen flickering and a bunch of errors about "nvlddmkm missing" in the event monitor.

Let me know if I can help further narrow down the culprit.

@rdoursenaud commented on GitHub (Mar 15, 2025): I have the same problem and tracked it down to a video acceleration bug with Optimus (Intel + nVidia graphics). Setting the GPU preference to Intel solves the issue for me. The clue was my screen flickering and a bunch of errors about "nvlddmkm missing" in the event monitor. Let me know if I can help further narrow down the culprit.
claunia commented 2026-01-31 08:30:13 +00:00
Author
Owner
Copy Link

@rdoursenaud commented on GitHub (Mar 15, 2025):

Update: after removing both drivers with DDU and letting Windows Update pick up the drivers, I can’t reproduce the behavior anymore regardless of the GPU preference setting. Might be a graphics driver issue.

@rdoursenaud commented on GitHub (Mar 15, 2025): Update: after removing both drivers with DDU and letting Windows Update pick up the drivers, I can’t reproduce the behavior anymore regardless of the GPU preference setting. Might be a graphics driver issue.
claunia commented 2026-01-31 08:30:14 +00:00
Author
Owner
Copy Link

@PaszaVonPomiot commented on GitHub (Mar 16, 2025):

Thanks! I set following in Graphic Settings for Terminal and the problem went away:

Image

Changing to high performance makes the crash. Ticking the "Dont use optimistations..." box makes hard reset to my Windows.
Should I report it to NVIDIA?

@PaszaVonPomiot commented on GitHub (Mar 16, 2025): Thanks! I set following in Graphic Settings for Terminal and the problem went away: ![Image](https://github.com/user-attachments/assets/082661ce-c27e-41ba-a45d-ed314973810e) Changing to high performance makes the crash. Ticking the "Dont use optimistations..." box makes hard reset to my Windows. Should I report it to NVIDIA?
claunia commented 2026-01-31 08:30:14 +00:00
Author
Owner
Copy Link

@Nenormalniy commented on GitHub (Mar 18, 2025):

I have same issue, but I have no integrated graphics, just one gpu.

@Nenormalniy commented on GitHub (Mar 18, 2025): I have same issue, but I have no integrated graphics, just one gpu.
claunia commented 2026-01-31 08:30:14 +00:00
Author
Owner
Copy Link

@ryan08100715 commented on GitHub (Mar 19, 2025):

I have the same problem, but when I updated the Nvidia driver (version: 572.83) released on March 18th, the problem was solved.

@ryan08100715 commented on GitHub (Mar 19, 2025): I have the same problem, but when I updated the Nvidia driver (version: 572.83) released on March 18th, the problem was solved.
claunia commented 2026-01-31 08:30:14 +00:00
Author
Owner
Copy Link

@PaszaVonPomiot commented on GitHub (Mar 19, 2025):

I confirm - Nvidia driver (version: 572.83) solves it.

@PaszaVonPomiot commented on GitHub (Mar 19, 2025): I confirm - Nvidia driver (version: 572.83) solves it.
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-Triage
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#23024
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?