starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Installation of .msixbundle fails cause Microsoft.UI.Xaml.2.8 is missing #22382

New Issue
Closed
opened 2026-01-31 08:11:33 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 08:11:33 +00:00
Owner
Copy Link

Originally created by @ChaosBladeCoder on GitHub (Oct 11, 2024).

Windows Terminal version

1.21.2701

Windows build number

10.0.20348.2762 (Windows Server 2022 Standard)

Other Software

N/A

Steps to reproduce

  1. Downloaded the latest Stable release (1.21.2701) as a .msixbundle.
  2. Copied the installer to my offline Windows Server 2022 machine
  3. Tried to follow the "Other install methods" on https://github.com/microsoft/terminal, specially:
  4. Double-clicking the .msixbundle file didn't work, as there was no handler for this file type. Ok, disappointing, but I'll use PowerShell instead.
  5. Ran Add-AppxPackage in Powershell

Expected Behavior

Bundle should install correctly, including dependencies, without requiring additional downloads .

Actual Behavior

Add-AppxPackage fails with the following error:

Deployment failed with HRESULT: 0x80073CF3, Package failed updates, dependency, or conflict validation. Windows cannot install package Microsoft.WindowsTerminal_1.21.2701.0.x64 because this package depends on a framework that could not be found. Provide the framework Microsoft.UI.Xaml.2.8 publiched by [... etc].

Originally created by @ChaosBladeCoder on GitHub (Oct 11, 2024). ### Windows Terminal version 1.21.2701 ### Windows build number 10.0.20348.2762 (Windows Server 2022 Standard) ### Other Software N/A ### Steps to reproduce 1. Downloaded the latest Stable release (1.21.2701) as a .msixbundle. 2. Copied the installer to my **offline** Windows Server 2022 machine 3. Tried to follow the "Other install methods" on https://github.com/microsoft/terminal, specially: 4. Double-clicking the .msixbundle file didn't work, as there was no handler for this file type. Ok, disappointing, but I'll use PowerShell instead. 5. Ran Add-AppxPackage in Powershell ### Expected Behavior Bundle should install correctly, including dependencies, without requiring additional downloads . ### Actual Behavior Add-AppxPackage <package> fails with the following error: Deployment failed with HRESULT: 0x80073CF3, Package failed updates, dependency, or conflict validation. Windows cannot install package Microsoft.WindowsTerminal_1.21.2701.0.x64 because this package depends on a framework that could not be found. Provide the framework Microsoft.UI.Xaml.2.8 publiched by [... etc].
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:11:33 +00:00
claunia commented 2026-01-31 08:11:35 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Oct 11, 2024):

@DHowett will have to correct me here, but I believe that Windows Server comes without the necessary XAML dependency. This means you need to use the "PreinstallKit" from our release page. It includes the Microsoft.UI.Xaml...appx package which you can install before installing our msixbundle.

@lhecker commented on GitHub (Oct 11, 2024): @DHowett will have to correct me here, but I believe that Windows Server comes without the necessary XAML dependency. This means you need to use the "PreinstallKit" from our release page. It includes the `Microsoft.UI.Xaml...appx` package which you can install before installing our msixbundle.
claunia commented 2026-01-31 08:11:35 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 11, 2024):

Yes, fully offline installs need to use the preinstallation/provisioning kit.

@DHowett commented on GitHub (Oct 11, 2024): Yes, fully offline installs need to use the preinstallation/provisioning kit.
claunia commented 2026-01-31 08:11:35 +00:00
Author
Owner
Copy Link

@ChaosBladeCoder commented on GitHub (Oct 11, 2024):

Thank you, that is helpful!

However, how is anyone supposed to know this, currently?

This isn't mentioned anywhere in the installation instructions. I didn't find any specific instructions for fully offline installation, nor is it explained anywhere that the preinstallation/provisition kit can/should be used for this. The Windows Terminal Distribution Types page doesn't mention this. In fact the wording of that page immediately made me disregard this package (especially, "Users who do not intend to preinstall Windows Terminal should continue using the Packaged distribution"). I also looked for words like 'redist', 'redistributable package', which also don't appear anywhere.

It would be helpful to have at least some note about fully offline mode in the installation instructions.

@ChaosBladeCoder commented on GitHub (Oct 11, 2024): Thank you, that is helpful! However, how is anyone supposed to know this, currently? This isn't mentioned _anywhere_ in the installation instructions. I didn't find _any_ specific instructions for fully offline installation, nor is it explained anywhere that the preinstallation/provisition kit can/should be used for this. The [Windows Terminal Distribution Types](https://learn.microsoft.com/en-gb/windows/terminal/distributions) page doesn't mention this. In fact the wording of that page immediately made me disregard this package (especially, _"Users who do not intend to preinstall Windows Terminal should continue using the Packaged distribution"_). I also looked for words like 'redist', 'redistributable package', which also don't appear anywhere. It would be helpful to have at least _some_ note about fully offline mode in the installation instructions.
claunia commented 2026-01-31 08:11:35 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 11, 2024):

You know, that's fair feedback. Thanks.

@DHowett commented on GitHub (Oct 11, 2024): You know, that's fair feedback. Thanks.
claunia commented 2026-01-31 08:11:35 +00:00
Author
Owner
Copy Link

@sqwwwok commented on GitHub (Dec 26, 2024):

Yes, fully offline installs need to use the preinstallation/provisioning kit.

how to use this kit? i cannot find it or its instruction.

@sqwwwok commented on GitHub (Dec 26, 2024): > Yes, fully offline installs need to use the preinstallation/provisioning kit. how to use this kit? i cannot find it or its instruction.
claunia commented 2026-01-31 08:11:35 +00:00
Author
Owner
Copy Link

@LtdJorge commented on GitHub (Dec 30, 2024):

Yes, fully offline installs need to use the preinstallation/provisioning kit.

how to use this kit? i cannot find it or its instruction.

Just extract the preinstallation kit and Add-AppxPackage .\Microsoft.UI.Xaml.version_yourarchitecture.appx.

Then Add-AppxPackage .\Microsoft.WindowsTerminal...

@LtdJorge commented on GitHub (Dec 30, 2024): > > Yes, fully offline installs need to use the preinstallation/provisioning kit. > > how to use this kit? i cannot find it or its instruction. Just extract the preinstallation kit and `Add-AppxPackage .\Microsoft.UI.Xaml.version_yourarchitecture.appx`. Then `Add-AppxPackage .\Microsoft.WindowsTerminal...`
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#22382
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?