[Package Issue]: Microsoft.WindowsAppRuntime.1.4

[GarretWayne]

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)".

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")

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:
   

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

[denelon]

What output do you get from winget list WindowsAppRuntime?

[GarretWayne]

This was my output:

Name	Id	Version
WindowsAppRuntime.1.4	Microsoft.WindowsAppRuntime.1.4_8wekyb3d8bbwe	4000.1049.117.0
WindowsAppRuntime.1.3	Microsoft.WindowsAppRuntime.1.3_8wekyb3d8bbwe	3000.934.1904.0

[denelon]

winget-pkgs/manifests/m/Microsoft/WindowsAppRuntime/1/4/1.4.3/Microsoft.WindowsAppRuntime.1.4.installer.yaml

Line 14 in 53aa1a8

DisplayVersion: 4000.1049.117.0

That looks like the latest version for WindowsAppRuntime.1.4

I'm not sure why you're seeing an upgrade loop. Is this only happening in WinGetUi or is this happening in the CLI as well?

[GarretWayne]

I can confirm that the CLI doesn't show the WindowsAppRuntime package on using command winget upgrade --all command.

Furthermore, it seems I have another oddity too:

• the DeepL.DeepL package says "Unkown installed version"
  • this package was also ignored on the UI, but included in the CMD
  • although it seems by running winget upgrade --include-unknown --all it has updated it? (see CMD lines)
    • CMD Output:

{
    winget upgrade -- all
   No installed package found matching input criteria.
   1 package(s) have version numbers that cannot be determined. Use -- include-unknown to see all results.
   1 package(s) have version numbers that cannot be determined. Use -- include-unknown to see all results.
   PS {user-stuff} winget upgrade -- include-unknown -- all
  Version Available

  DeepL DeepL. DeepL Unknown 23.11.2. 11449 winget
  1 upgrades available.

  Installing dependencies:
  (1/1) Found DeepL [DeepL. DeepL] Version 23.11. 2. 11449
  This application is licensed to you by its owner.
  Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
  Downloading https: //appdownload. deepl. com/windows/0install/DeepLSetup. exe
  4.28 MB / 4.28 MB
  Successfully verified installer hash
  Starting package install ...
  Successfully installed
}

• after running the CMD and removed DeepL.DeepL package from the ignored list in the WinGetUi, it also upgrade loops:
  • What I did:
    1. Ran the CMD upgrade for DeepL.DeepL ( command used: winget upgrade -- include-unknown -- all)
    2. Still showed up in WinGetUi after refreshing the page
    3. Ran WinGetUi update for DeepL.DeepL, gone after reshresing the page
       3.5 actually, it gets automatically added to the Ignored Updates list
    4. Ran CMD command winget upgrade -- include-unknown -- all
    5. CMD updated the package again (and continues to do so on every run of winget upgrade -- include-unknown -- all)
       

Conclusion:

• DeepL.DeepL package is always looped in CMD,
  • gets automatically added to the Ignored Updates list , after manually removed then updated
  • winget list DeepL.DeepL says:
    • 
• Microsoft.WindowsAppRuntime is looped only in WinGetUi

[nemchik]

I am seeing this as well.

Winget CLI:

> winget list WindowsAppRuntime
Name                  Id                                            Version
------------------------------------------------------------------------------------
WindowsAppRuntime.1.3 Microsoft.WindowsAppRuntime.1.3_8wekyb3d8bbwe 3000.934.1904.0
WindowsAppRuntime.1.1 Microsoft.WindowsAppRuntime.1.1_8wekyb3d8bbwe 1005.616.1651.0
WindowsAppRuntime.1.4 Microsoft.WindowsAppRuntime.1.4_8wekyb3d8bbwe 4000.1082.2259.0

WingetUI:

Control Panel:

Updating via winget cli or winget ui seems to reinstall the version that is already installed (6.0.26.33205 currently) and then still list the update as available (same output as above on cli).

[aasril]

I also have this problem

> winget list WindowsAppRuntime
Name                            Id                                            Version
----------------------------------------------------------------------------------------------
Microsoft.WindowsAppRuntime.1.3 Microsoft.WindowsAppRuntime.1.3_8wekyb3d8bbwe 3000.934.1904.0
WindowsAppRuntime.1.5           Microsoft.WindowsAppRuntime.1.5_8wekyb3d8bbwe 5001.70.1338.0
WindowsAppRuntime.1.4           Microsoft.WindowsAppRuntime.1.4_8wekyb3d8bbwe 4000.1136.2333.0

> winget update
No installed package found matching input criteria.

winget upgrade --all --include-unknown
No installed package found matching input criteria.

Meanwhile in WingetUI

As already mentioned above, it keeps showing up even after it said it was successfully updated.

I also reinstalled WingetUI for All Users instead of just for me just in case it was a problem with permission.

[aasril]

I noticed that the package was installed by WingetUI installer. Maybe this is the source of the update loop? WingetUI hard depend on the installed version, but at the same time it notices a newer version is available but can't utilize the update.

[crrodriguez]

I have this same loop with 1.3 and 1.5.. does anyone know how to break it ??