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

Fresh install shows blank window then exits #7818

New Issue
Closed
opened 2026-01-31 01:13:22 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 01:13:22 +00:00
Owner
Copy Link

Originally created by @swpalmer on GitHub (Apr 29, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.815]
Windows Terminal version (if applicable): 0.11.1191.0

Any other software?  Just setting up a new Windows re-install, so nothing I can think would be relevant. The new chromium-based edge, but Terminal was failing before and after installed that.  Windows update says there are no updates.

settings.json is new and untouched from this initial install.

Steps to reproduce

Try to launch Windows Terminal by opening or "Run as Administrator" from the start menu

Expected behavior

Windows Terminal would launch and be usable.

Actual behavior

A blank "gel" window appears for a second or two and goes away. Nothing for Windows Terminal is shown on the start bar. An Application event is logged.

Faulting application name: WindowsTerminal.exe, version: 0.11.2004.28001, time stamp: 0x5ea883f8
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.18362.815, time stamp: 0x9fa806f2
Exception code: 0xc000027b
Fault offset: 0x0000000000713530
Faulting process id: 0x1560
Faulting application start time: 0x01d61e5dc395feaa
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.11.1191.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: 47537453-c99e-4fe4-834e-f02b48c6bcdd
Faulting package full name: Microsoft.WindowsTerminal_0.11.1191.0_x64__8wekyb3d8bbwe

Originally created by @swpalmer on GitHub (Apr 29, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ``` Windows build number: Microsoft Windows [Version 10.0.18363.815] Windows Terminal version (if applicable): 0.11.1191.0 Any other software? Just setting up a new Windows re-install, so nothing I can think would be relevant. The new chromium-based edge, but Terminal was failing before and after installed that. Windows update says there are no updates. settings.json is new and untouched from this initial install. ``` # Steps to reproduce Try to launch Windows Terminal by opening or "Run as Administrator" from the start menu # Expected behavior Windows Terminal would launch and be usable. # Actual behavior A blank "gel" window appears for a second or two and goes away. Nothing for Windows Terminal is shown on the start bar. An Application event is logged. Faulting application name: WindowsTerminal.exe, version: 0.11.2004.28001, time stamp: 0x5ea883f8 Faulting module name: Windows.UI.Xaml.dll, version: 10.0.18362.815, time stamp: 0x9fa806f2 Exception code: 0xc000027b Fault offset: 0x0000000000713530 Faulting process id: 0x1560 Faulting application start time: 0x01d61e5dc395feaa Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.11.1191.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll Report Id: 47537453-c99e-4fe4-834e-f02b48c6bcdd Faulting package full name: Microsoft.WindowsTerminal_0.11.1191.0_x64__8wekyb3d8bbwe
claunia added the Needs-Tag-FixNeeds-Attention labels 2026-01-31 01:13:22 +00:00
claunia commented 2026-01-31 01:13:23 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 29, 2020):

/feedback

@DHowett-MSFT commented on GitHub (Apr 29, 2020): /feedback
claunia commented 2026-01-31 01:13:23 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 29, 2020):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

image image

@ghost commented on GitHub (Apr 29, 2020): Hi there!<br><br>Can you please send us feedback with the Feedback Hub with this issue and 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/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-31 01:13:24 +00:00
Author
Owner
Copy Link

@swpalmer commented on GitHub (Apr 30, 2020):

https://aka.ms/AA8aekz

@swpalmer commented on GitHub (Apr 30, 2020): https://aka.ms/AA8aekz
claunia commented 2026-01-31 01:13:24 +00:00
Author
Owner
Copy Link

@swpalmer commented on GitHub (Apr 30, 2020):

Finally solved this. it appears to be an issue with nVidia Quadro 2000m. Changing the setting in the nVidia control panel that had the "Preferred graphics processor" set to the "high-performance NVIDIA processor", instead to be "Auto-select" (presumably defaulting to the integrated graphics for non-3D), made this problem go away.

@swpalmer commented on GitHub (Apr 30, 2020): Finally solved this. it appears to be an issue with nVidia Quadro 2000m. Changing the setting in the nVidia control panel that had the "Preferred graphics processor" set to the "high-performance NVIDIA processor", instead to be "Auto-select" (presumably defaulting to the integrated graphics for non-3D), made this problem go away.
claunia commented 2026-01-31 01:13:24 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 30, 2020):

Wow, that's quite strange. I didn't stand a chance of figuring that one out. Thanks for following up!

@DHowett-MSFT commented on GitHub (Apr 30, 2020): Wow, that's quite strange. I didn't stand a chance of figuring that one out. Thanks for following up!
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 Needs-Attention Needs-Tag-Fix
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#7818
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?