microsoft / microsoft/winget-pkgs

[Package Issue]: Microsoft.WindowsAppRuntime.1.4

Open
#133,265 9 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Bug
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
376

Description

Please confirm these before moving forward
  • I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
  • I have not been informed if the issue is resolved in a preview version of the winget client.
Category of the issue

Other

Brief description of your issue

Updated package "Microsoft.WindowsAppRuntime.1.4" (package ID), but it keeps showing up as "needs to be updated to version "7.0.14" ", even though it's package name is already "Microsoft Windows Desktop Runtime - 7.0.14 (x64)".

image

Steps to reproduce

(Step 0. Have the "Microsoft.WindowsAppRuntime.1.4" installed. Note: I think it was installed by Visual Studio IDE.)
Step 1. Refresh "Software Updates" page in WingetUi
Step 2. Update this package: (could be called something else first, but the Package Id should be "Microsoft.WindowsAppRuntime.1.4")
image

Step 3. Refresh "Software Updates" page in WingetUi
Step 4. See if Package with ID "Microsoft.WindowsAppRuntime.1.4" is still showing up

Actual behavior
  1. WingetUi gets the installer
  2. Then installer opens a CMD window that shows this:
    image
Expected behavior
  • Not show up as something that needs to be updated.
  • Have correct Package ID (?)
Environment
Windows Package Manager v1.6.3482
Windows: Windows.Desktop v10.0.22631.2861
Package: Microsoft.DesktopAppInstaller v1.21.3482.0
Screenshots and Logs

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin by reproducing the update detection with Microsoft.WindowsAppRuntime.1.4 in WingetUi on the reported Windows Package Manager environment, then inspect the package manifest and its identity and version metadata. Done means the package no longer reappears as needing an update after installation and refresh, with the expected Package ID shown.

Written by the indexing model from the issue text.

Assessment

Domain
operating-systems, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.