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

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

New Issue
Closed
opened 2026-01-31 08:35:49 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 08:35:49 +00:00
Owner
Copy Link

Originally created by @Eli-Zaretskii on GitHub (May 2, 2025).

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}

Originally created by @Eli-Zaretskii on GitHub (May 2, 2025). ### 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: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WindowsUpdateClient" Guid="{945a8954-c147-4acd-923f-40c45405a658}" /> <EventID>20</EventID> <Version>1</Version> <Level>2</Level> <Task>1</Task> <Opcode>13</Opcode> <Keywords>0x8000000000000028</Keywords> <TimeCreated SystemTime="2025-05-02T14:15:58.7982496Z" /> <EventRecordID>35220</EventRecordID> <Correlation ActivityID="{8e7ee601-afd7-001c-8708-708fd7afdb01}" /> <Execution ProcessID="46312" ThreadID="49092" /> <Channel>System</Channel> <Computer>EliZ-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="errorCode">0x80073d02</Data> <Data Name="updateTitle">9N0DX20HK701-Microsoft.WindowsTerminal</Data> <Data Name="updateGuid">{8f02e7ac-f82e-49ab-aa07-f9268d882d69}</Data> <Data Name="updateRevisionNumber">1</Data> <Data Name="serviceGuid">{855e8a7c-ecb4-4ca3-b045-1dfa50104289}</Data> </EventData> </Event>
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 08:35:50 +00:00
claunia commented 2026-01-31 08:35:51 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (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 commented on GitHub (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...)
claunia commented 2026-01-31 08:35:51 +00:00
Author
Owner
Copy Link

@Eli-Zaretskii commented on GitHub (May 8, 2025):

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"?

@Eli-Zaretskii commented on GitHub (May 8, 2025): > 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`"?
claunia commented 2026-01-31 08:35:51 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (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 commented on GitHub (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. 🙂
claunia commented 2026-01-31 08:35:52 +00:00
Author
Owner
Copy Link

@Eli-Zaretskii commented on GitHub (May 12, 2025):

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.

@Eli-Zaretskii commented on GitHub (May 12, 2025): > 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.
claunia commented 2026-01-31 08:35:52 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 12, 2025):

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

FWIW, it was added four days ago. :)

@DHowett commented on GitHub (May 12, 2025): > Huh? The "need author feedback" was removed 4 days ago. FWIW, it was _added_ four days ago. :)
claunia commented 2026-01-31 08:35:52 +00:00
Author
Owner
Copy Link

@Eli-Zaretskii commented on GitHub (Aug 5, 2025):

OK, I've finally had the opportunity to Quit the terminal and then install the update, and it worked well.
Thanks, this issue can be closed.

@Eli-Zaretskii commented on GitHub (Aug 5, 2025): OK, I've finally had the opportunity to Quit the terminal and then install the update, and it worked well. Thanks, this issue can be closed.
claunia commented 2026-01-31 08:35:52 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Aug 6, 2025):

Thanks for confirming! Closing

@carlos-zamora commented on GitHub (Aug 6, 2025): Thanks for confirming! Closing
claunia commented 2026-01-31 08:35:52 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 6, 2025):

FWIW, this is because we requested that Windows defer automatic updates while we are running. It turns out that that prevents manual updates from completing too. >:{

@DHowett commented on GitHub (Aug 6, 2025): FWIW, this is because we requested that Windows defer _automatic_ updates while we are running. It turns out that that prevents _manual_ updates from completing too. >:{
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 Issue-Bug Needs-Attention 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#23224
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?