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 Update breaks Windows Terminal due to Windows App SDK issue #22585

New Issue
Closed
opened 2026-01-31 08:17:40 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 08:17:40 +00:00
Owner
Copy Link

Originally created by @ClausAndersen on GitHub (Nov 22, 2024).

Windows Terminal version

1.21.3231.0

Windows build number

10.0.19045.5131

Other Software

Windows App SDK 1.6.3

Steps to reproduce

TLDR; Windows Terminal broken due to Windows update. This update caused issues with Windows App SDK 1.6.2. This update was pulled but damage had already been done. The temporary fix for that is to update to Windows App SDK 1.6.3. This however leaves Windows Terminal MSIX bundle broken. Installing the latest avaialbe bundle will fail most likely because "WindowsAppSDKSelfContained=true" in the bundle.

Long version:

Windows Terminal stopped working for me after a reboot due to Windows update. At first I simply tried to uninstall it with the intent of re-installing.

This gave me the error 0x80073CFA which led me to a currently ongoing Windows App SDK issue:
https://github.com/microsoft/WindowsAppSDK/issues/4881

I did the manual fix and do now have Windows App SDK 1.6.3

This does however give me a problem when I try to install the latest MSIX bundle:

Microsoft.WindowsTerminal_1.21.3231.0_8wekyb3d8bbwe.msixbundle

This gives the localized error:

Pakken kan ikke installeres, fordi der allerede er installeret en højere version af denne pakke.

Which roughly translates to:

Package cannot be installed, as there is already a newer version of this package.

From the linked Windows App SDK issue this seem to be the problem if you are using self-contained bundles:

WindowsAppSDKSelfContained=true

And it would be worth examining if it is worth having native AOT on.

The system:
Windows 10 22H2
Build 19045.5131
Microsoft.WindowsTerminal_1.21.3231.0_8wekyb3d8bbwe.msixbundle (latest)
Windows App SDK 1.6.3

I think it would be very helpful to the community if a new release was built with SDK 1.6.3 as we now have a lot of breakage in the wild. I do not dare to submit a pull request for this as this will no doubt create a lot of bike shedding. But I think a new build using latest SDK would be most helpful middle of the road quickfix.

Expected Behavior

Being able to install latest Windows Terminal MSIX bundle on a up-to-date Windows 10 installation.

Actual Behavior

Installation reports a newer version is installed/available even though "Terminal" is no longer listed as an installed application and the latest version is used.

Image

Originally created by @ClausAndersen on GitHub (Nov 22, 2024). ### Windows Terminal version 1.21.3231.0 ### Windows build number 10.0.19045.5131 ### Other Software Windows App SDK 1.6.3 ### Steps to reproduce TLDR; Windows Terminal **broken due to Windows update**. This update caused issues with Windows App SDK 1.6.2. This update was pulled but damage had already been done. The temporary fix for that is to update to Windows App SDK 1.6.3. This however leaves Windows Terminal MSIX bundle broken. Installing the latest avaialbe bundle will fail most likely because "WindowsAppSDKSelfContained=true" in the bundle. Long version: Windows Terminal stopped working for me after a reboot due to Windows update. At first I simply tried to uninstall it with the intent of re-installing. This gave me the error 0x80073CFA which led me to a currently ongoing Windows App SDK issue: https://github.com/microsoft/WindowsAppSDK/issues/4881 I did the manual fix and do now have Windows App SDK 1.6.3 This does however give me a problem when I try to install the latest MSIX bundle: Microsoft.WindowsTerminal_1.21.3231.0_8wekyb3d8bbwe.msixbundle This gives the localized error: Pakken kan ikke installeres, fordi der allerede er installeret en højere version af denne pakke. Which roughly translates to: Package cannot be installed, as there is already a newer version of this package. From the linked Windows App SDK issue this seem to be the problem if you are using self-contained bundles: WindowsAppSDKSelfContained=true And it would be worth examining if it is worth having native AOT on. The system: Windows 10 22H2 Build 19045.5131 Microsoft.WindowsTerminal_1.21.3231.0_8wekyb3d8bbwe.msixbundle (latest) Windows App SDK 1.6.3 I think it would be very helpful to the community if a new release was built with SDK 1.6.3 as we now have a lot of breakage in the wild. I do not dare to submit a pull request for this as this will no doubt create a lot of bike shedding. But I think a new build using latest SDK would be most helpful middle of the road quickfix. ### Expected Behavior Being able to install latest Windows Terminal MSIX bundle on a up-to-date Windows 10 installation. ### Actual Behavior Installation reports a newer version is installed/available even though "Terminal" is no longer listed as an installed application and the latest version is used. ![Image](https://github.com/user-attachments/assets/eb600c94-e191-4c06-9d6d-04e333bf3bf5)
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:17:40 +00:00
claunia commented 2026-01-31 08:17:41 +00:00
Author
Owner
Copy Link

@Archomeda commented on GitHub (Nov 22, 2024):

I think I'm hitting the same issue, I cannot even uninstall Windows Terminal via PowerShell. It gives me 0x80073CFA as error.
Right now I can't install, reinstall, remove or boot up Windows Terminal. It's completely unusable.

@Archomeda commented on GitHub (Nov 22, 2024): I think I'm hitting the same issue, I cannot even uninstall Windows Terminal via PowerShell. It gives me 0x80073CFA as error. Right now I can't install, reinstall, remove or boot up Windows Terminal. It's completely unusable.
claunia commented 2026-01-31 08:17:41 +00:00
Author
Owner
Copy Link

@ClausAndersen commented on GitHub (Nov 22, 2024):

It gives me 0x80073CFA as error.

If you go to SDK 1.6.3 you should be able to uninstall. For me I could not install it again after but others have reported success. YMMV.

@ClausAndersen commented on GitHub (Nov 22, 2024): > It gives me 0x80073CFA as error. If you go to SDK 1.6.3 you should be able to uninstall. For me I could not install it again after but others have reported success. YMMV.
claunia commented 2026-01-31 08:17:41 +00:00
Author
Owner
Copy Link

@Archomeda commented on GitHub (Nov 22, 2024):

Aha, I got it to reinstall and work again. But now I've lost all my settings 😂

@Archomeda commented on GitHub (Nov 22, 2024): Aha, I got it to reinstall and work again. But now I've lost all my settings 😂
claunia commented 2026-01-31 08:17:42 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 22, 2024):

Thanks for surfacing this! Terminal actually doesn’t use WinAppSDK at all, neither self-contained nor systemwide. However, it will still be impacted by the WinAppSDK issue.

Once you’re remediated:

If you use Add-AppxPackage with the -AllowUpgradeFromAnyVersion flag, it should let you reinstall the latest version.

You may also be able to effect the same process by using the Repair option in App Settings.

If you are not yet remediated:
Install the optional 11D Cumulative Feature Update.

@DHowett commented on GitHub (Nov 22, 2024): Thanks for surfacing this! Terminal actually doesn’t use WinAppSDK at all, neither self-contained nor systemwide. However, it will still be impacted by the WinAppSDK issue. Once you’re remediated: If you use `Add-AppxPackage` with the `-AllowUpgradeFromAnyVersion` flag, it should let you reinstall the latest version. You may also be able to effect the same process by using the *Repair* option in App Settings. If you are not yet remediated: Install the optional 11D Cumulative Feature Update.
claunia commented 2026-01-31 08:17:42 +00:00
Author
Owner
Copy Link

@ClausAndersen commented on GitHub (Nov 22, 2024):

Thanks for surfacing this! Terminal actually doesn’t use WinAppSDK at all, neither self-contained nor systemwide. However, it will still be impacted by the WinAppSDK issue.

Oh! Cool. Thanks for responding anyway.

If you use Add-AppxPackage with the -AllowUpgradeFromAnyVersion flag, it should let you reinstall the latest version.

Does not work. That flag is not listed with -? but I then found -ForceUpdateFromAnyVersion which did the job for me!

Add-AppxPackage Microsoft.WindowsTerminal_1.21.3231.0_8wekyb3d8bbwe.msixbundle -ForceUpdateFromAnyVersion

This will work from Windows Powershell and not Powershell 7.

So everything works as it is supposed to do. Thanks!

@ClausAndersen commented on GitHub (Nov 22, 2024): > Thanks for surfacing this! Terminal actually doesn’t use WinAppSDK at all, neither self-contained nor systemwide. However, it will still be impacted by the WinAppSDK issue. Oh! Cool. Thanks for responding anyway. > If you use `Add-AppxPackage` with the `-AllowUpgradeFromAnyVersion` flag, it should let you reinstall the latest version. Does not work. That flag is not listed with `-?` but I then found `-ForceUpdateFromAnyVersion` which did the job for me! Add-AppxPackage Microsoft.WindowsTerminal_1.21.3231.0_8wekyb3d8bbwe.msixbundle -ForceUpdateFromAnyVersion This will work from Windows Powershell and not Powershell 7. So everything works as it is supposed to do. Thanks!
claunia commented 2026-01-31 08:17:42 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 22, 2024):

You're totally right, and I misremembered the name of the arg. I'm glad it worked!

@DHowett commented on GitHub (Nov 22, 2024): You're totally right, and I misremembered the name of the arg. I'm glad it worked!
claunia commented 2026-01-31 08:17:42 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Dec 4, 2024):

This should now be fixed. Thanks for reporting it!

@carlos-zamora commented on GitHub (Dec 4, 2024): This should now be fixed. Thanks for reporting it!
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-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#22585
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?