winget update --all does not automatically update packages

[stallam-unb]

Brief description of your issue

Until recently, running winget update --all or winget upgrade --all would (barring a couple of exceptions), download any relevant packages and update them automatically. However, recently (maybe for a couple of weeks), it just displays the available updates and just exits.

Steps to reproduce

Run: winget update --all

Expected behavior

Except to see a list of available candidates followed by downloading the installers and updating the relevant applications.

Actual behavior

Only printing out the list of available updates and does nothing after.

Environment

Windows: Windows.Desktop v10.0.22631.3155
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.22.10582.0

[github-actions]

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!

Open similar issues:

• Winget refuses to update packages, ignoring --all as well (#2891), similarity score: 0.92
• winget upgrade --all finds update but does nothing (#3280), similarity score: 0.89
• Winget upgrade --all not updating certain packages when reporting updates available (#2634), similarity score: 0.87
• Winget does not install all some updates (#3510), similarity score: 0.87

Closed similar issues:

• winget always tries to update packages that are already up to date (#2111), similarity score: 0.88

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[Trenly]

Try using the pre-release version v1.7.10661. This is a known issue in v1.7.10582. If you still run into problems, you can report in the tracking issue here #4219

Duplicate of #4219

[microsoft-github-policy-service]

Hello @stallam-unb,

We've identified this as a duplicate of another issue or PR that already exists. This specific instance is being closed in favor of the linked issue. Please add your 👍 to the other issue to raise its priority. Thanks for your contribution!

Template: msftbot/duplicate/closed