microsoft / microsoft/terminal

Windows Terminal will not open

Open
#17,255 22 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Settings Issue-Bug Priority-1 Product-Terminal Severity-Crash
Dominant language
C++
Stars
105k
Forks
9.6k
Avg merge
3d 17h
Merged PRs (30d)
29

Description

Windows Terminal version

1.19.11213.0 & 1.21.1272.0

Windows build number

Win10 22H2 build 19045.4355

Other Software

N/A

Steps to reproduce

Windows Terminal will not open now, as of a couple weeks ago.

It will not run by opening wt.exe, or WIndowsTerminal.exe. Regularly, or as administrator. In it's default folder, or by typing wt.exe in "run:"

I've tried rebooting, I've ensured the system is fully updated, I've tried Settings>Apps>Windows Terminal>Advanced Options> Terminate/Repair/Reset.

It started with v 1.19.11213.0 which I've had installed from Windows Store for a while now. It was working fine up until a couple weeks ago. I don't know what's changed other than maybe a system update? I've also tried uninstalling it then reinstalling it - same issue. Then, I uninstalled it and installed v 1.21.1272.0 - same exact issue. It runs at first launch after install, then won't open after.

It will only open from Windows Store > Windows Terminal > "Open" -- but without any of my settings.

I've looked online (and yes, I've looked in Github Open & Closed issues) and I've tried just about everything except the generic MS Agent response to:

1) del /f /s /q /a "%LocalAppData%\Packages\Microsoft.WindowsTerminal_*\LocalState\settings.json"

2) Download windows installer > Upgrade PC Now > Keep Files

I am not going to reinstall windows and have to backup 1tb of data or risk it being lost over this.

There needs to be a different way?

I'm at the point of deleting anything "WindowsTerminal" in Windows Registry but I have not done so unless you tell me to, or another option.

C:\WINDOWS\system32>DISM /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Image Version: 10.0.19045.4355

No component store corruption detected.
The operation completed successfully.
C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

Edit:

Per the github-actions bot, before posting this I also did find #14133 which refers to #14104 - which recommends to simply install "Windows Media Feature Pack" -- however, that is for Windows N versions. So I did not do it.

They also reference #14110 & #14124 - which appears to be a different error, but it did prompt me to look at Event Viewer:

Regular opening attempt of wt.exe as non-administrator:

Faulting application name: WindowsTerminal.exe, version: 1.19.2404.30003, time stamp: 0x663158bd
Faulting module name: ucrtbase.dll, version: 10.0.19041.3636, time stamp: 0x81cf5d89
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x1f90
Faulting application start time: 0x01daa5103b89c37d
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.19.11213.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: cfe9c59a-12b4-4ea2-97d3-b83a0c38df62
Faulting package full name: 
Faulting package-relative application ID: 

Attempt at opening wt.exe with "Run ad Administrator:

Faulting application name: WindowsTerminal.exe, version: 1.19.2404.30003, time stamp: 0x663158bd
Faulting module name: ucrtbase.dll, version: 10.0.19041.3636, time stamp: 0x81cf5d89
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x2ec0
Faulting application start time: 0x01daa51054d81854
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.19.11213.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 6ef3592e-3575-4d14-b563-713b917d42d4
Faulting package full name: 
Faulting package-relative application ID: 

Appears to be a different faulting DLL than those issues referenced.

Per the feedback in all of those issues - I will also send feedback via the Feedback Hub, however I really would appreciate some insight or a fix here asap because Windows Terminal is meta, and I need to use it!!!

Thanks!

Expected Behavior

The program to run regularly.

Actual Behavior

The program will not open other than via Windows Store > Open, with stock settings.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the launch failure on Windows 10 22H2 with the listed Terminal versions, then review the Event Viewer reports showing ucrtbase.dll and exception 0xc0000409. Compare the referenced issues #14133, #14104, #14110, and #14124 for related failures. Done means identifying a reproducible cause and restoring normal wt.exe launching with the user's settings.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.