[Package Issue]: Microsoft.PowerBI

[JimWeaverling]

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

Installer hash mismatch.

Brief description of your issue

PowerBI is installing an older version of 2.139.2054.0, the pull request looks like it was having some issues.

Steps to reproduce

Doing a winget search shows the old version when a new March update is available.

Actual behavior

Winget is installing the older version from Jan/Feb update.

Expected behavior

Winget should install the new version from March.

Environment

PS C:\WINDOWS\system32> winget --info
Windows Package Manager v1.10.340
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19045.5608
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.25.340.0

Screenshots and Logs

#247403

[similar-issues-ai]

We've found some similar issues:

• [Package Issue]: Microsoft.PowerBI #111467 , similarity score: 81%
• [Package Issue]: Microsoft.PowerBI 2.114.864.0 hash mismatch #99666 , similarity score: 81%
• [Update Request]: Microsoft.PowerBI #197547 , similarity score: 81%
• [Package Issue]: Microsoft.PowerBI #101573 , similarity score: 81%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

[SpecterShell]

#247750

[chrismrutledge]

The new package was approved and merged in 2 days ago. Yet the winget CDN still has the old package.

Any idea what the expectation is for a timeline from merge to updated CDN?

[Dragon1573]

The new package was approved and merged in 2 days ago. Yet the winget CDN still has the old package.

Currently the publish pipeline is "unhealthy" and paused for publishing new manifests to WinGet CDN Endpoint. We have to wait for it becomes "healthy" again ...

[chrismrutledge]

Thanks for the clarification and update!

You might take a note of the Sha256 hash as well. When I copied down the manifests to do the installs locally, I noticed I needed to update the hash.

[SpecterShell]

Thanks for the clarification and update!

You might take a note of the Sha256 hash as well. When I copied down the manifests to do the installs locally, I noticed I needed to update the hash.

There was an update yesterday, not being merged yet: #249251