Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation issue: dependency issue #2626

Open
fmuntean opened this issue Oct 23, 2022 · 5 comments
Open

Installation issue: dependency issue #2626

fmuntean opened this issue Oct 23, 2022 · 5 comments
Labels
Issue-Docs It's a documentation issue that really should be on MicrosoftDocs

Comments

@fmuntean
Copy link

fmuntean commented Oct 23, 2022

Trying to manually install the msixbundle

Add-AppPackage : Deployment failed with HRESULT: 0x80073CF3, Package failed updates, dependency or conflict validation.
Windows cannot install package Microsoft.DesktopAppInstaller_1.18.2691.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.2109.13004.0, along with this package to install. The frameworks with name "Microsoft.UI.Xaml.2.7" currently installed are: {}

if it is a CLI tool why requires the UI XAML ?

@ghost ghost added the Needs-Triage Issue need to be triaged label Oct 23, 2022
@Masamune3210
Copy link

Because its bundled with the App Installer package, which includes a UI to handle installing APPX and MSIX packages. winget doesn't need the UI framework, but since its in the package, it has the dependency as well

@denelon
Copy link
Contributor

denelon commented Oct 25, 2022

It looks like we need to add Microsoft.UI.Xaml.2.7 to https://github.com/microsoft/winget-cli#manually-update

@denelon denelon added Issue-Docs It's a documentation issue that really should be on MicrosoftDocs and removed Needs-Triage Issue need to be triaged labels Oct 25, 2022
@JuryA
Copy link

JuryA commented Jan 6, 2023

Why is this error still fixed? Installation of Microsoft.UI.Xaml.2.7 is NOT an easy task! How to deal with that from PowerShell? I tried everything but this is not OK - this issue is here for a couple of months!

@denelon denelon added this to WinGet Jan 6, 2023
@denelon denelon moved this to To Do in WinGet Jan 6, 2023
@denelon denelon added this to the v1.5-Client milestone Jan 6, 2023
@denelon
Copy link
Contributor

denelon commented Jan 6, 2023

We've built a PowerShell DSC module which includes pulling in the necessary dependencies. We're working on additional testing, and then we will provide instructions on how to use it. As it is open source, one should be able to pull the necessary bits out so it's possible to install WinGet on systems using just PowerShell as opposed to needing to also understand PowerShell DSC.

@denelon denelon modified the milestones: v1.5-Client, v.Next-Client Jun 6, 2023
@denelon denelon removed this from WinGet Jun 13, 2023
@denelon
Copy link
Contributor

denelon commented Jun 28, 2023

The Repair-WinGetPackageManager cmdlet in the Microsoft.WinGet.Client PowerShell Module does much of the work to handle dependencies, but Microsoft.UI.Xaml is still not handled in the most optimal way. We're looking at some options here to see if we can improve the situation without needing to download and decompress the dependency.

We've also been looking to update the dependency to Microsoft.UI.Xaml 2.8 from 2.7 in WinGet:

@denelon denelon removed this from the v.Next-Client milestone Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Docs It's a documentation issue that really should be on MicrosoftDocs
Projects
None yet
Development

No branches or pull requests

4 participants