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

App installer failed to install package dependencies. Ask the developer for package #17993

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

Originally created by @GauravSahare1993 on GitHub (Jul 21, 2022).

Windows Terminal version

1.14.1862.0

Windows build number

10.0.22000.318.0

Other Software

No response

Steps to reproduce

App installer failed to install package dependencies. Ask the developer for package, 1st it requires installation of "Microsoft.UI.Xaml.2.7" , after successful installation of this Xaml, still shows package dependencies error.
Screenshot (4)

Expected Behavior

No issue should appear during installation.

Actual Behavior

Still I am facing this error.

Originally created by @GauravSahare1993 on GitHub (Jul 21, 2022). ### Windows Terminal version 1.14.1862.0 ### Windows build number 10.0.22000.318.0 ### Other Software _No response_ ### Steps to reproduce App installer failed to install package dependencies. Ask the developer for package, 1st it requires installation of "Microsoft.UI.Xaml.2.7" , after successful installation of this Xaml, still shows package dependencies error. ![Screenshot (4)](https://user-images.githubusercontent.com/109745579/180238864-15aed993-4252-4bea-9ddc-fb1794b18465.png) ### Expected Behavior No issue should appear during installation. ### Actual Behavior Still I am facing this error.
claunia added the Issue-QuestionNeeds-TriageNeeds-Tag-FixResolution-Answered labels 2026-01-31 06:00:35 +00:00
claunia commented 2026-01-31 06:00:35 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 21, 2022):

I think the Microsoft.WindowsTerminal_Win10_1.14.1861.0_8wekyb3d8bbwe.msixbundle bundle might work better for you. (note 1.14.1861, not 1862)That's got some extra dependencies bundled in.

From the release notes:

Why are there so many packages? How do I choose?

This version of Windows Terminal is distributed in two bundles, one of which works on Windows 10-11 and the other of
which only works on Windows 11. The Windows 11 version is much smaller because we no longer need to work around a
platform issue related to our dependencies.

If you intend on using Terminal as an unpackaged application--that is, extracting the msix file--we recommend that
you use the Win10 bundle. You will need the Visual C++ runtime redistributable.

In addition, if you install the packaged version on either Windows 10 or Windows 11, it now depends on the Visual C++ Universal Runtime Package.

Despite these distributions having different version numbers, they are built from the same code and there is no
functional difference between them.

If you install the Windows 10 verison on Windows 11, it will probably automatically upgrade itself to the Windows 11
version. It turns out that it is impossible to have two bundles with the same version number, so it has to be this
way.

@zadjii-msft commented on GitHub (Jul 21, 2022): I think the [Microsoft.WindowsTerminal_Win10_1.14.1861.0_8wekyb3d8bbwe.msixbundle](https://github.com/microsoft/terminal/releases/download/v1.14.1861.0/Microsoft.WindowsTerminal_Win10_1.14.1861.0_8wekyb3d8bbwe.msixbundle) bundle might work better for you. (note 1.14.186**1**, not 1862)That's got some extra dependencies bundled in. From the release notes: > ### Why are there so many packages? How do I choose? > This version of Windows Terminal is distributed in two bundles, one of which works on Windows 10-11 and the other of > which only works on Windows 11. The Windows 11 version is much smaller because we no longer need to work around a > platform issue related to our dependencies. > > If you intend on using Terminal as an unpackaged application--that is, extracting the `msix` file--we recommend that > you use the `Win10` bundle. You will need the [Visual C++ runtime redistributable](https://docs.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist). > > In addition, if you install the _packaged_ version on either Windows 10 or Windows 11, it now depends on [the Visual C++ Universal Runtime Package](https://docs.microsoft.com/en-us/troubleshoot/developer/visualstudio/cpp/libraries/c-runtime-packages-desktop-bridge?msclkid=3e1dd82aac8b11ec8f9dbd86d5979ca8#how-to-install-and-update-desktop-framework-packages). > > Despite these distributions having different version numbers, they are built from the same code and there is no > functional difference between them. > > If you install the Windows 10 verison on Windows 11, it will probably automatically upgrade itself to the Windows 11 > version. It turns out that it is impossible to have two bundles with _the same version number_, so it has to be this > way.
claunia commented 2026-01-31 06:00:36 +00:00
Author
Owner
Copy Link

@GauravSahare1993 commented on GitHub (Jul 22, 2022):

My thanks for reply, but problem was still present, I investigated more and now I found that this problem exactly happens due to missing package "VCLibs.x64.14.00.Desktop" and "Microsoft.UI.Xaml.2.7" , so I installed both, then I installed the version of terminal app you provided, finally I am no longer facing this issue.
Kindly update this information if someone facing this problem.

@GauravSahare1993 commented on GitHub (Jul 22, 2022): My thanks for reply, but problem was still present, I investigated more and now I found that this problem exactly happens due to missing package **"VCLibs.x64.14.00.Desktop"** and **"Microsoft.UI.Xaml.2.7"** , so I installed both, then I installed the version of terminal app you provided, finally I am no longer facing this issue. Kindly update this information if someone facing this problem.
claunia commented 2026-01-31 06:00:36 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 22, 2022):

Thanks for following up!

@zadjii-msft commented on GitHub (Jul 22, 2022): Thanks for following up!
claunia commented 2026-01-31 06:00:36 +00:00
Author
Owner
Copy Link

@mhadinj commented on GitHub (Apr 13, 2025):

Hi

for ms Ui Xaml
run powershell as admin
Invoke-WebRequest -Uri https://github.com/microsoft/microsoft-ui-xaml/releases/download/v2.8.6/Microsoft.UI.Xaml.2.8.x64.appx -OutFile $env:TEMP\Microsoft.UI.Xaml.2.8.x64.appx Add-AppxPackage $env:TEMP\Microsoft.UI.Xaml.2.8.x64.appx

@mhadinj commented on GitHub (Apr 13, 2025): Hi for ms Ui Xaml run powershell as admin ` Invoke-WebRequest -Uri https://github.com/microsoft/microsoft-ui-xaml/releases/download/v2.8.6/Microsoft.UI.Xaml.2.8.x64.appx -OutFile $env:TEMP\Microsoft.UI.Xaml.2.8.x64.appx Add-AppxPackage $env:TEMP\Microsoft.UI.Xaml.2.8.x64.appx `
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-Question Needs-Tag-Fix Needs-Triage Resolution-Answered
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#17993
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?