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

Grey screen on launch, terminal doesn't respond #15238

New Issue
Closed
opened 2026-01-31 04:32:25 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 04:32:25 +00:00
Owner
Copy Link

Originally created by @Sankgreall on GitHub (Sep 16, 2021).

Windows Terminal version (or Windows build number)

1.10.2383.0

Other Software

No response

Steps to reproduce

  • Install Windows Terminal (either through Store or through .msixbundle

  • Try to launch Windows Terminal

Note: Execution environment is a AVD host pool using a Windows 10 build 2004 base image

Expected Behavior

Windows Terminal launches

Actual Behavior

Windows Terminal does not load. Instead, it is completely grey and eventually stops responding and must be forcibly stopped.

wsl
Originally created by @Sankgreall on GitHub (Sep 16, 2021). ### Windows Terminal version (or Windows build number) 1.10.2383.0 ### Other Software _No response_ ### Steps to reproduce - Install Windows Terminal (either through Store or through .msixbundle - Try to launch Windows Terminal Note: Execution environment is a AVD host pool using a Windows 10 build 2004 base image ### Expected Behavior Windows Terminal launches ### Actual Behavior Windows Terminal does not load. Instead, it is completely grey and eventually stops responding and must be forcibly stopped. <img width="902" alt="wsl" src="https://user-images.githubusercontent.com/53608489/133659903-9f03d844-1f08-4db4-b89d-13393c67afb9.png">
claunia added the Resolution-Duplicate label 2026-01-31 04:32:25 +00:00
claunia commented 2026-01-31 04:32:26 +00:00
Author
Owner
Copy Link

@Sankgreall commented on GitHub (Sep 16, 2021):

Following on from this, if I execute the Windows Terminal twice, then the first window will open grey and unresponsive as above. However, once this is forcibly quit then the second execution will open as intended.

I.e., two or more executions in a row work fine, once the first windows has been destroyed.

@Sankgreall commented on GitHub (Sep 16, 2021): Following on from this, if I execute the Windows Terminal **twice**, then the first window will open grey and unresponsive as above. However, once this is forcibly quit then the second execution will open **as intended**. I.e., two or more executions in a row work fine, once the first windows has been destroyed.
claunia commented 2026-01-31 04:32:26 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 18, 2021):

Hmm interesting. I've got a question that might help sort out the root cause here. If you install PowerToys, and try and open the PowerToys settings, do you get the same behavior?

@zadjii-msft commented on GitHub (Sep 18, 2021): Hmm interesting. I've got a question that might help sort out the root cause here. If you install PowerToys, and try and open the PowerToys settings, do you get the same behavior?
claunia commented 2026-01-31 04:32:26 +00:00
Author
Owner
Copy Link

@Sankgreall commented on GitHub (Sep 18, 2021):

Thanks for your reply. PowerToys was not on the original run environment, but have installed it now to test.

Does appear to work. No grey screen on the settings page, and PowerToys Run works as expected.

powertoys
@Sankgreall commented on GitHub (Sep 18, 2021): Thanks for your reply. PowerToys was not on the original run environment, but have installed it now to test. Does appear to work. No grey screen on the settings page, and PowerToys Run works as expected. <img width="1658" alt="powertoys" src="https://user-images.githubusercontent.com/53608489/133894697-b179a54b-c362-40ae-8752-52471ee951b6.png">
claunia commented 2026-01-31 04:32:27 +00:00
Author
Owner
Copy Link

@Sankgreall commented on GitHub (Sep 18, 2021):

Weirdly, after closing PowerToys Settings and the failing Windows Terminal, my next attempt at opening Windows Terminal succeeded. Subsequent attempts failed and went back to grey screen.

I uninstalled and reinstalled PowerToys, but wasn't able to replicate - so it could have been a coincidence. However, on the first time I tried this I did notice a PowerToys error message (which I'm sorry I didn't take a screenshot of), which didn't happen upon reinstallation.

@Sankgreall commented on GitHub (Sep 18, 2021): Weirdly, after closing PowerToys Settings and the failing Windows Terminal, my next attempt at opening Windows Terminal succeeded. Subsequent attempts failed and went back to grey screen. I uninstalled and reinstalled PowerToys, but wasn't able to replicate - so it could have been a coincidence. However, on the first time I tried this I did notice a PowerToys error message (which I'm sorry I didn't take a screenshot of), which didn't happen upon reinstallation.
claunia commented 2026-01-31 04:32:27 +00:00
Author
Owner
Copy Link

@Falco20019 commented on GitHub (Sep 21, 2021):

I have the same problem. I just cleanly reinstalled the latest release but it's not working. I have Windows 10 v1909 (Build 18363.1734) and can't update since it's a company machine maintained by our IT. PowerToys settings in 0.4.3 are working as expected.

@Falco20019 commented on GitHub (Sep 21, 2021): I have the same problem. I just cleanly reinstalled the latest release but it's not working. I have Windows 10 v1909 (Build 18363.1734) and can't update since it's a company machine maintained by our IT. PowerToys settings in 0.4.3 are working as expected.
claunia commented 2026-01-31 04:32:27 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 21, 2021):

Sorry, didn't realize this was Windows Server. Yep, that sounds just like /dup #11135

@zadjii-msft commented on GitHub (Sep 21, 2021): Sorry, didn't realize this was Windows Server. Yep, that sounds just like /dup #11135
claunia commented 2026-01-31 04:32:28 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 21, 2021):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Sep 21, 2021): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
claunia commented 2026-01-31 04:32:28 +00:00
Author
Owner
Copy Link

@Sankgreall commented on GitHub (Sep 21, 2021):

Sorry, didn't realize this was Windows Server. Yep, that sounds just like /dup #11135

@zadjii-msft Sorry, I am confused. I am using Windows 10 build 2004, not Windows Server. Do you still suspect this is a duplicate?

@Sankgreall commented on GitHub (Sep 21, 2021): > Sorry, didn't realize this was Windows Server. Yep, that sounds just like /dup #11135 @zadjii-msft Sorry, I am confused. I am using Windows 10 build 2004, not Windows Server. Do you still suspect this is a duplicate?
claunia commented 2026-01-31 04:32:28 +00:00
Author
Owner
Copy Link

@Falco20019 commented on GitHub (Sep 21, 2021):

@Sankgreall I also have the same issue on 1909 (non server), but I assume the cause is the same or at least related.

@Falco20019 commented on GitHub (Sep 21, 2021): @Sankgreall I also have the same issue on 1909 (non server), but I assume the cause is the same or at least related.
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 Resolution-Duplicate
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#15238
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?