-
Notifications
You must be signed in to change notification settings - Fork 8.6k
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
Comments
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 |
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?
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 |
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. 🙂 |
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. |
FWIW, it was added four days ago. :) |
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}
The text was updated successfully, but these errors were encountered: