Skip to content

Windows Terminal v1.22.11141.0 fails to install on Windows 11 version 24H2 #18866

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Eli-Zaretskii opened this issue May 2, 2025 · 5 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@Eli-Zaretskii
Copy link

Windows Terminal version

1.22.11141.0

Windows build number

10.0.26100.3775

Other Software

No response

Steps to reproduce

Go to Microsoft Store and try to update Windows Terminal.
Or just wait for Windows to try to do that by itself, as part of its automatic updates.

Expected Behavior

Expected behavior is that the new version of the Windows Terminal is installed, upgrading the previous one.

Actual Behavior

The upgrade fails. The Event Viewer shows the following:

Log Name: System
Source: Microsoft-Windows-WindowsUpdateClient
Date: 02/05/2025 17:15:58
Event ID: 20
Task Category: Windows Update Agent
Level: Error
Keywords: Failure,Installation
User: SYSTEM
Computer: EliZ-PC
Description:
Installation Failure: Windows failed to install the following update with error 0x80073D02: 9N0DX20HK701-Microsoft.WindowsTerminal.
Event Xml:



20
1
2
1
13
0x8000000000000028

35220


System
EliZ-PC



0x80073d02
9N0DX20HK701-Microsoft.WindowsTerminal
{8f02e7ac-f82e-49ab-aa07-f9268d882d69}
1
{855e8a7c-ecb4-4ca3-b045-1dfa50104289}

@Eli-Zaretskii Eli-Zaretskii added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels May 2, 2025
@DHowett
Copy link
Member

DHowett commented May 7, 2025

Hey there!

As of Windows 11 build 26100 and Terminal 1.21, the store will no longer install updates to Terminal while any part of it is running.

Can you make sure you've closed all instances of Terminal, as well as any possibly-lingering instances of OpenConsole.exe/? (The latter should have been handled for you, but on rare occasion one or two stick around...)

@DHowett DHowett added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label May 7, 2025
@Eli-Zaretskii
Copy link
Author

As of Windows 11 build 26100 and Terminal 1.21, the store will no longer install updates to Terminal while any part of it is running.

That's too bad, because I have 5 Terminal windows open and running at all times, each one with a separate environment and specific configuration and purpose. Previously, installing an update would close them all and then I could reopen them (or maybe they even reopened automatically?) with the entire previous history shown in each instance. Now this will be lost, or is there a way to close all the terminals such that reopening each one will show the history of each one in its window? Or maybe there's a way to close them such that they could be all reopened after the update, showing their respective histories?

Or maybe there's a way to install an update in some other way, so as not to lose that very useful feature?

Can you make sure you've closed all instances of Terminal, as well as any possibly-lingering instances of OpenConsole.exe/? (The latter should have been handled for you, but on rare occasion one or two stick around...)

I closed only the 5 windows I had, and that allowed the update, but just in case: how do I identify the "possibly-lingering instances of OpenConsole.exe"?

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels May 8, 2025
@DHowett
Copy link
Member

DHowett commented May 8, 2025

Sorry, I know it isn't ideal.

You can quit the entire terminal--all open windows--using the "Quit Terminal" action from command palette. It will preserve all your open windows and tabs for later restoration, assuming you use the mode where Terminal remembers these things.

As for instances of OpenConsole... Task Manager (Details section) will be your best bet. I only threw that in there for completeness; we haven't seen lingering instances in a year or more, but I am still scarred from it. 🙂

@DHowett DHowett added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something and removed Needs-Attention The core contributors need to come back around and look at this ASAP. labels May 8, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label May 12, 2025
@Eli-Zaretskii
Copy link
Author

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

Huh? The "need author feedback" was removed 4 days ago.

I didn't yet have an opportunity to try the "Quit Terminal" method, because I can only try that when an update of the Windows terminal is available. Please keep the issue open for a little longer, until I'm able to provide the feedback about your proposals.

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. labels May 12, 2025
@DHowett
Copy link
Member

DHowett commented May 12, 2025

Huh? The "need author feedback" was removed 4 days ago.

FWIW, it was added four days ago. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants