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

Cannot install Terminal 1.17.11461.0 on Windows Server 2022 #20033

New Issue
Closed
opened 2026-01-31 07:01:21 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 07:01:21 +00:00
Owner
Copy Link

Originally created by @PGomersall on GitHub (Jun 5, 2023).

Windows Terminal version

1.17.11461.0

Windows build number

20348.1726

Other Software

OS is fully patched Windows Server 2022

Steps to reproduce

Run Add-AppxPackage C:\temp\Microsoft.WindowsTerminal_1.17.11461.0_8wekyb3d8bbwe.msixbundle

This then will error if Microsoft.VCLibs.140.00.UWPDesktop is not installed. If that package is installed, it will then also error if Microsoft.UI.Xaml.2.7 is not installed.

Only if these 2 packages are installed will Microsoft Terminal install. It is noted that for 1.17 VCLibs is still required, but I have not seen any info that UI.Xaml 2.7 is also needed.

Expected Behavior

Note to say Microsoft.UI.Xaml.2.7 is needed.

Actual Behavior

Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF3, Package failed updates, dependency or conflict
validation.
Windows cannot install package Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe because this package depends
on a framework that could not be found. Provide the framework "Microsoft.UI.Xaml.2.7" published by "CN=Microsoft
Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and
minimum version 7.2208.15002.0, along with this package to install. The frameworks with name "Microsoft.UI.Xaml.2.7"
currently installed are: {}

Originally created by @PGomersall on GitHub (Jun 5, 2023). ### Windows Terminal version 1.17.11461.0 ### Windows build number 20348.1726 ### Other Software OS is fully patched Windows Server 2022 ### Steps to reproduce Run Add-AppxPackage C:\temp\Microsoft.WindowsTerminal_1.17.11461.0_8wekyb3d8bbwe.msixbundle This then will error if Microsoft.VCLibs.140.00.UWPDesktop is not installed. If that package is installed, it will then also error if Microsoft.UI.Xaml.2.7 is not installed. Only if these 2 packages are installed will Microsoft Terminal install. It is noted that for 1.17 VCLibs is still required, but I have not seen any info that UI.Xaml 2.7 is also needed. ### Expected Behavior Note to say Microsoft.UI.Xaml.2.7 is needed. ### Actual Behavior Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF3, Package failed updates, dependency or conflict validation. Windows cannot install package Microsoft.WindowsTerminal_1.17.11461.0_x64__8wekyb3d8bbwe because this package depends on a framework that could not be found. Provide the framework "Microsoft.UI.Xaml.2.7" published by "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version 7.2208.15002.0, along with this package to install. The frameworks with name "Microsoft.UI.Xaml.2.7" currently installed are: {}
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 07:01:22 +00:00
claunia commented 2026-01-31 07:01:23 +00:00
Author
Owner
Copy Link

@PGomersall commented on GitHub (Jun 5, 2023):

Version of Microsoft.UI.Xaml seems to specifically need 2.7, as having latest version also prevents install.

@PGomersall commented on GitHub (Jun 5, 2023): Version of Microsoft.UI.Xaml seems to specifically need 2.7, as having latest version also prevents install.
claunia commented 2026-01-31 07:01:23 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 5, 2023):

Thanks for letting us know. In general we haven't noted our dependencies down1 , because the preinstallation kit distribution contains everything you'll need to perform an offline deployment of Terminal at the minimum versions you'll need to install it.

For Server editions of Windows, manual installation with the preinstallation kit is going to be a lot smoother than any other packaged options.

For Desktop editions of Windows, the "Desktop App Installer" automatically sources any necessary dependencies.

  1. except for VCLibs, because 1.18 removed this dependency; however, those notes only apply to the "portable" and "unpackaged" distributions. ↩︎

@DHowett commented on GitHub (Jun 5, 2023): Thanks for letting us know. In general we _haven't_ noted our dependencies down[^1], because the _preinstallation kit_ distribution contains everything you'll need to perform an offline deployment of Terminal at the minimum versions you'll need to install it. For Server editions of Windows, manual installation with the preinstallation kit is going to be a lot smoother than any other packaged options. For Desktop editions of Windows, the "Desktop App Installer" automatically sources any necessary dependencies. [^1]: except for VCLibs, because 1.18 removed this dependency; however, those notes only apply to the "portable" and "unpackaged" distributions.
claunia commented 2026-01-31 07:01:24 +00:00
Author
Owner
Copy Link

@PGomersall commented on GitHub (Jun 5, 2023):

Thanks for quick response Dustin. I was just looking at simple way to automate updating Terminal on Server 2022 using PowerShell and pulling from GitHub and came across this issue. I suppose I could do the same but extract the contents from the preinstallation kit zip.

@PGomersall commented on GitHub (Jun 5, 2023): Thanks for quick response Dustin. I was just looking at simple way to automate updating Terminal on Server 2022 using PowerShell and pulling from GitHub and came across this issue. I suppose I could do the same but extract the contents from the preinstallation kit zip.
claunia commented 2026-01-31 07:01:24 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jun 7, 2023):

I'm going to close this based on Dustin's response, but if Dustin or Pete disagree, happy to reopen. Thanks!

@carlos-zamora commented on GitHub (Jun 7, 2023): I'm going to close this based on Dustin's response, but if Dustin or Pete disagree, happy to reopen. Thanks!
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#20033
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?