-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Incorrect package name matching #3696
Comments
I wonder if #3547 (comment) is related |
Update: Changing the PackageName from
Reading this, I'm curious if it's the moniker ( |
I don’t think it would, because the moniker should only be used when a user provides it as a query; I don’t think its related to correlation |
I'm having this same issue.
|
I also have this today:
and no idea why I see it now. |
Same here, Winget v1.6.3482.
|
Brief description of your issue
While installing devhome, WinGet could not install the dependency for me as it incorrectly correlates the dependency with an installed package
Logs:
WinGet-2023-09-27-22-55-38.740.log
Digging deeper, it seems to me that WinGet is incorrectly matching an installed package
Windows SDK AddOn
with the PackageId Microsoft.WindowsAppRuntime.1.3I believe this mismatch is due to the fact that 1.3.2 version of WindowsAppRuntime has PackageName
Windows App SDK
which is getting matched with installed package with nameWindows SDK Addon
. Since 1.3.3 manifest PackageName was modified to the correctWindows App Runtime
, the installed package is not getting matched with the 1.3.3 version.ARP Entry for Windows SDK AddOn

ARP Entry(s) for Windows App Runtime after manual installation

Steps to reproduce
Microsoft.WindowsAppRuntime.1.3
Expected behavior
(If I'm understanding this correctly)
Windows SDK AddOn
should not be getting matched withWindows App SDK
. I would expect that the "App" inWindows App SDK
would prevent it from getting matched withWindows SDK AddOn
Actual behavior
Environment
The text was updated successfully, but these errors were encountered: