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
Windows Package Manager 1.7.10661 #4280
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Closed similar issues:
|
I just downloaded the latest version, but when I run it, it looks like it's an older version. |
That's the version of App Installer package that WinGet is shipped as part of. Both softwares have a different version. App Installer If you have other questions, check out the FAQ or open a discussion if you have a question that's not answered there. |
Discussed in #4255
Originally posted by ryfu-msft March 9, 2024
This release is the second release candidate of Windows Package Manager 1.7 for Windows 10 (1809+), and Windows 11.
Experimental features have been disabled in this release.
This release fixes issues related to
winget upgrade --all
(#4219) and addresses problems with the PowerShell cmdletRepair-WinGetPackageManager
which was caused by our dependency on the latest Microsoft.UI.Xaml version 2.8 (#4208).What's Changed
Full Changelog: v1.7.10582...v1.7.10661
This discussion was created from the release Windows Package Manager 1.7.10661.
The text was updated successfully, but these errors were encountered: