Windows Terminal Quits Immediately on Start #14004

Closed
opened 2026-01-31 03:58:12 +00:00 by claunia · 11 comments
Owner

Originally created by @XieJiSS on GitHub (May 28, 2021).

Windows Terminal version (or Windows build number)

10.0.19042, 1.8.1444.0

Other Software

No response

Steps to reproduce

Basically, my PC installed a windows update (KB5003173) during a restart

image

After the restart, I tried to start Windows Terminal from Startup Menu, from task bar and from my Right-click menu, but it always quits immediately.

https://i.loli.net/2021/05/28/iu1XHN9Whc8gUlQ.gif

This is the only thing showed up:

image

(its full title is DesktopWindowXamlSource) and it will disappear in a short time (~5s).

I haven't changed any settings of my WT before (despite font size), but I did modified my $profile file (though it worked perfectly before the windows update).

I did use Huorong antivirus, but I think this won't affect because the same phenomenon still happens after I manually quit Huorong antivirus


Note that this is (as far as I can tell) not related to the startingDirectory option because there's no such word in my configuration file

Expected Behavior

Windows Terminal should start properly

Actual Behavior

Windows Terminal won't start

Originally created by @XieJiSS on GitHub (May 28, 2021). ### Windows Terminal version (or Windows build number) 10.0.19042, 1.8.1444.0 ### Other Software _No response_ ### Steps to reproduce Basically, my PC installed a windows update (KB5003173) during a restart ![image](https://user-images.githubusercontent.com/24671280/119945382-f5502700-bfc7-11eb-9256-6389e3145cd7.png) After the restart, I tried to start Windows Terminal from Startup Menu, from task bar and from my Right-click menu, but it always quits immediately. https://i.loli.net/2021/05/28/iu1XHN9Whc8gUlQ.gif This is the only thing showed up: ![image](https://user-images.githubusercontent.com/24671280/119946095-d43c0600-bfc8-11eb-9702-cdc690b9dc07.png) (its full title is `DesktopWindowXamlSource`) and it will disappear in a short time (~5s). I haven't changed any settings of my WT before (despite font size), but I did modified my $profile file (though it worked perfectly before the windows update). I did use Huorong antivirus, but I think this won't affect because the same phenomenon still happens after I manually quit Huorong antivirus --- Note that this is (as far as I can tell) not related to the `startingDirectory` option because there's no such word in my configuration file ### Expected Behavior Windows Terminal should start properly ### Actual Behavior Windows Terminal won't start
claunia added the Resolution-Duplicate label 2026-01-31 03:58:12 +00:00
Author
Owner

@awolman commented on GitHub (May 28, 2021):

This is the second time this has happened to me (if I remember correctly the first time was on the 1.4 -> 1.5 upgrade). Can someone please tell me how to install windows terminal in a way where the upgrades don't happen automatically, so that I can decide when to upgrade?

@awolman commented on GitHub (May 28, 2021): This is the second time this has happened to me (if I remember correctly the first time was on the 1.4 -> 1.5 upgrade). Can someone please tell me how to install windows terminal in a way where the upgrades don't happen automatically, so that I can decide when to upgrade?
Author
Owner

@XieJiSS commented on GitHub (May 28, 2021):

I found #6304 by searching DesktopWindowX, and it appears to me that this window is a normal step during the initializing process of a Windows Terminal instance, but now the process is failing at this step.

@XieJiSS commented on GitHub (May 28, 2021): I found #6304 by searching `DesktopWindowX`, and it appears to me that this window is a normal step during the initializing process of a Windows Terminal instance, but now the process is failing at this step.
Author
Owner

@mkaes commented on GitHub (May 28, 2021):

I could fix this issue by using the repair options in the settings of the app

@mkaes commented on GitHub (May 28, 2021): I could fix this issue by using the repair options in the settings of the app
Author
Owner

@XieJiSS commented on GitHub (May 28, 2021):

@mkaes Thanks, I fixed it with the repair options too.

Still don't know root cause though, so I think I'll leave this issue open.

To be more specific:

  1. I found the "Settings" option here:
    image

  2. Open "Settings", click "Repair" (NOT Reset)

@XieJiSS commented on GitHub (May 28, 2021): @mkaes Thanks, I fixed it with the repair options too. Still don't know root cause though, so I think I'll leave this issue open. To be more specific: 1. I found the "Settings" option here: ![image](https://user-images.githubusercontent.com/24671280/119966362-d066ae80-bfdd-11eb-9156-3450bcb4f42f.png) 2. Open "Settings", click "Repair" (**NOT** Reset)
Author
Owner

@zadjii-msft commented on GitHub (May 28, 2021):

I'm thinking that this is probably #10211, but there's only one way to know for sure. If you could repro this with the Feedback Hub, we could get a stack trace that we can make sure is the same thing.

/feedback

@zadjii-msft commented on GitHub (May 28, 2021): I'm thinking that this is probably #10211, but there's only one way to know for sure. If you could repro this with the Feedback Hub, we could get a stack trace that we can make sure is the same thing. /feedback
Author
Owner

@ghost commented on GitHub (May 28, 2021):

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 (May 28, 2021): 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)
Author
Owner

@XieJiSS commented on GitHub (May 28, 2021):

I'm thinking that this is probably #10211, but there's only one way to know for sure. If you could repro this with the Feedback Hub, we could get a stack trace that we can make sure is the same thing.

/feedback

Hmmm, I think maybe I need to rollback the 20H1 Update (and install it again) to reproduce this? I'm not quite sure whether I'm able to rollback the update, but I'll try anyway.

@XieJiSS commented on GitHub (May 28, 2021): > I'm thinking that this is probably #10211, but there's only one way to know for sure. If you could repro this with the Feedback Hub, we could get a stack trace that we can make sure is the same thing. > > /feedback Hmmm, I think maybe I need to rollback the 20H1 Update (and install it again) to reproduce this? I'm not quite sure whether I'm able to rollback the update, but I'll try anyway.
Author
Owner

@zadjii-msft commented on GitHub (May 28, 2021):

Oh sorry, no, don't bother with that. If you've already repaired and it's gone away, then reinstalling windows isn't going to re-break it again unfortunately. This is one of those things that only happens when an app is updated by the store.

I'll just assume that this one was #10211, based on the fact that a repair fixed it. We've got like 8 other "it crashed immediately" threads, so I'm sure whatever the underlying issue here is, it's tracked by one of them 😆

/dup #10211

@zadjii-msft commented on GitHub (May 28, 2021): Oh sorry, no, don't bother with that. If you've already repaired and it's gone away, then reinstalling windows isn't going to re-break it again unfortunately. This is one of those things that only happens when an app is updated by the store. I'll just assume that this one was #10211, based on the fact that a repair fixed it. We've got like 8 other "it crashed immediately" threads, so I'm sure whatever the underlying issue here is, it's tracked by _one_ of them 😆 /dup #10211
Author
Owner

@ghost commented on GitHub (May 28, 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 (May 28, 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!
Author
Owner

@tvance929 commented on GitHub (May 29, 2021):

I could fix this issue by using the repair options in the settings of the app

that did it for me as well

image

@tvance929 commented on GitHub (May 29, 2021): > I could fix this issue by using the repair options in the settings of the app that did it for me as well ![image](https://user-images.githubusercontent.com/1489627/120078387-f8552100-c074-11eb-8449-935589d2e695.png)
Author
Owner

@ghost commented on GitHub (May 30, 2021):

Same problem, same resolution... cheers everyone.

@ghost commented on GitHub (May 30, 2021): Same problem, same resolution... cheers everyone.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#14004