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

Crash on launch #6379

New Issue
Closed
opened 2026-01-31 00:37:06 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 00:37:06 +00:00
Owner
Copy Link

Originally created by @Bonuspunkt on GitHub (Feb 11, 2020).

Environment

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.18363.0 Microsoft Windows NT 10.0.18363.0

Steps to reproduce

  1. Install via Store
  2. Launch Window Terminal

Expected behavior

Windows Terminal stays open

Actual behavior

Crashes, Event Logs shows

Faulting application name: WindowsTerminal.exe, version: 0.8.2001.26001, time stamp: 0x5e2e5240
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.18362.449, time stamp: 0xb90db728
Exception code: 0xc000027b
Fault offset: 0x0000000000712ec0
Faulting process id: 0x64b4
Faulting application start time: 0x01d5e1283661b6f5
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.8.10261.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: bed3d691-c869-4e4c-bcab-39efe39783f6
Faulting package full name: Microsoft.WindowsTerminal_0.8.10261.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

on a sidenode:

  • Feedback Hub does not list Windows Terminal
  • works fine on all my dev machines where VS2019 is installed
Originally created by @Bonuspunkt on GitHub (Feb 11, 2020). # Environment ```none Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 ``` # Steps to reproduce 1. Install via Store 2. Launch Window Terminal # Expected behavior Windows Terminal stays open # Actual behavior Crashes, Event Logs shows ``` Faulting application name: WindowsTerminal.exe, version: 0.8.2001.26001, time stamp: 0x5e2e5240 Faulting module name: Windows.UI.Xaml.dll, version: 10.0.18362.449, time stamp: 0xb90db728 Exception code: 0xc000027b Fault offset: 0x0000000000712ec0 Faulting process id: 0x64b4 Faulting application start time: 0x01d5e1283661b6f5 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.8.10261.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll Report Id: bed3d691-c869-4e4c-bcab-39efe39783f6 Faulting package full name: Microsoft.WindowsTerminal_0.8.10261.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App ``` on a sidenode: - Feedback Hub does not list Windows Terminal - works fine on all my dev machines where VS2019 is installed
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 00:37:07 +00:00
claunia commented 2026-01-31 00:37:07 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 11, 2020):

Hmm. And you've not customized Terminal at all in this installation?

@DHowett-MSFT commented on GitHub (Feb 11, 2020): Hmm. And you've not customized Terminal at all in this installation?
claunia commented 2026-01-31 00:37:08 +00:00
Author
Owner
Copy Link

@Bonuspunkt commented on GitHub (Feb 11, 2020):

no, reinstall also didn't fix it

@Bonuspunkt commented on GitHub (Feb 11, 2020): no, reinstall also didn't fix it
claunia commented 2026-01-31 00:37:08 +00:00
Author
Owner
Copy Link

@Bonuspunkt commented on GitHub (Feb 12, 2020):

fixed after rebooting 😅

@Bonuspunkt commented on GitHub (Feb 12, 2020): fixed after rebooting 😅
claunia commented 2026-01-31 00:37:08 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 12, 2020):

I hate to hear that (since it means it's nondeterministic and based on global system state), but thanks for following up!

@DHowett-MSFT commented on GitHub (Feb 12, 2020): I hate to hear that (since it means it's nondeterministic and based on global system state), but thanks for following up!
claunia commented 2026-01-31 00:37:08 +00:00
Author
Owner
Copy Link

@wt29 commented on GitHub (Jun 21, 2020):

I had this problem after upgrading to W10 2004 - I wanted the WSL Linux container integration. My laptop is now 8 YO, still functions well but has an integrated Intel 3000 GPU and an Nvidia GT520M. Disabling the GT520 fixed the issue with terminal and other apps that use GPU acceleration. There are some comments that 2004 has problems with Nvidia drivers < 328. The Nvidia experience app wouldn't run on 2004 under the GT520 so I had to specify "run on the Intel Integrated" which allowed me to update the drivers. Terminal now runs well. Other option was disable the GT520 in the BIOS.

@wt29 commented on GitHub (Jun 21, 2020): I had this problem after upgrading to W10 2004 - I wanted the WSL Linux container integration. My laptop is now 8 YO, still functions well but has an integrated Intel 3000 GPU and an Nvidia GT520M. Disabling the GT520 fixed the issue with terminal and other apps that use GPU acceleration. There are some comments that 2004 has problems with Nvidia drivers < 328. The Nvidia experience app wouldn't run on 2004 under the GT520 so I had to specify "run on the Intel Integrated" which allowed me to update the drivers. Terminal now runs well. Other option was disable the GT520 in the BIOS.
claunia commented 2026-01-31 00:37:08 +00:00
Author
Owner
Copy Link

@maPer77 commented on GitHub (Nov 19, 2020):

I had this problem after upgrading to W10 2004 - I wanted the WSL Linux container integration. My laptop is now 8 YO, still functions well but has an integrated Intel 3000 GPU and an Nvidia GT520M. Disabling the GT520 fixed the issue with terminal and other apps that use GPU acceleration. There are some comments that 2004 has problems with Nvidia drivers < 328. The Nvidia experience app wouldn't run on 2004 under the GT520 so I had to specify "run on the Intel Integrated" which allowed me to update the drivers. Terminal now runs well. Other option was disable the GT520 in the BIOS.

I have the same configuration and the same problem.

You have 2 options:

  • On the panel nvidia force the use of integrated graphics for the windows terminal.

or

notepad_jBTWh0JQsn

@maPer77 commented on GitHub (Nov 19, 2020): > I had this problem after upgrading to W10 2004 - I wanted the WSL Linux container integration. My laptop is now 8 YO, still functions well but has an integrated Intel 3000 GPU and an Nvidia GT520M. Disabling the GT520 fixed the issue with terminal and other apps that use GPU acceleration. There are some comments that 2004 has problems with Nvidia drivers < 328. The Nvidia experience app wouldn't run on 2004 under the GT520 so I had to specify "run on the Intel Integrated" which allowed me to update the drivers. Terminal now runs well. Other option was disable the GT520 in the BIOS. I have the same configuration and the same problem. You have 2 options: - On the panel nvidia force the use of integrated graphics for the windows terminal. or - In the windows terminal settings use: "experimental.rendering.software": true https://github.com/microsoft/terminal/issues/8286#issuecomment-729204294 ![notepad_jBTWh0JQsn](https://user-images.githubusercontent.com/5252293/99722058-d90a8500-2a8e-11eb-9d27-2ebc28d567c9.png)
claunia commented 2026-01-31 00:37:08 +00:00
Author
Owner
Copy Link

@rudironsoni commented on GitHub (Jul 18, 2021):

I had this problem after upgrading to W10 2004 - I wanted the WSL Linux container integration. My laptop is now 8 YO, still functions well but has an integrated Intel 3000 GPU and an Nvidia GT520M. Disabling the GT520 fixed the issue with terminal and other apps that use GPU acceleration. There are some comments that 2004 has problems with Nvidia drivers < 328. The Nvidia experience app wouldn't run on 2004 under the GT520 so I had to specify "run on the Intel Integrated" which allowed me to update the drivers. Terminal now runs well. Other option was disable the GT520 in the BIOS.

Thank you SO MUCH! I even formatted my computer in order to use Terminal but the issue was with NVIDIA.
Just like Linus said... F*ck you NVIDIA! hahahah
Can't believe that my GPU driver is the culprit.

@rudironsoni commented on GitHub (Jul 18, 2021): > I had this problem after upgrading to W10 2004 - I wanted the WSL Linux container integration. My laptop is now 8 YO, still functions well but has an integrated Intel 3000 GPU and an Nvidia GT520M. Disabling the GT520 fixed the issue with terminal and other apps that use GPU acceleration. There are some comments that 2004 has problems with Nvidia drivers < 328. The Nvidia experience app wouldn't run on 2004 under the GT520 so I had to specify "run on the Intel Integrated" which allowed me to update the drivers. Terminal now runs well. Other option was disable the GT520 in the BIOS. --------------------------------------- Thank you SO MUCH! I even formatted my computer in order to use Terminal but the issue was with NVIDIA. Just like Linus said... F*ck you NVIDIA! hahahah Can't believe that my GPU driver is the culprit.
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 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#6379
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?