marticliment
commented
12 hours ago Can you reproduce the same result by calling winget upgrade on a command prompt?
Open hms54 opened 1 day ago
marticliment
commented
12 hours ago Can you reproduce the same result by calling winget upgrade on a command prompt?
hms54
commented
10 hours ago Good question. Not sure how it happened, but Teamviewer updated to the correct version after my last test last night. So I can'tI try the update command. If this problem happens again, I'll document the results.
This package changed overnight in a way that may resolve the underlying issue in future updates.
The original (failing) package Installer URL referenced a generic zip filename that didn't change with new versions:
Installer Url: https://download.teamviewer.com/download/version_15x/TeamViewer_MSI64.zip
But the package today references a different URL that embeds the version number in the filename:
Installer Url: https://download.teamviewer.com/download/version_15x/update/Update_msi_15.59.5_x64.zip
Still not sure why UnigetUI Discover showed the correct version and UnigetUI Software Updates showed the wrong version. I assume they would be the same if they were both looking at the current package.
Please confirm these before moving forward
UniGetUI Version
3.1.3
Windows version, edition, and architecture
Windows 10 Pro
Describe your issue
Software Update page sometimes offers the wrong version of a Winget package even after an updated package is distributed.
Winget Package installations sometimes fail with a hash mismatch when the underlying software is updated, but the package still contains the old hash value. This hash value is generally updated within a day or so in a new package. But even after the correct package is available, the UnigetUI / Software Update continues to offer the older incorrect package. Refreshing the Winget Source index does not fix it, nor does a restart or full reboot.
Steps to reproduce the issue
Not sure how to reproduce this on demand. Must wait for a Winget package to fail with a hash mismatch and then be updated with the correct hash value. Specefics of most recent instance: UnigetUI offered an update of Teamviewer.Teamviewer v1.59.3 to v1.59.4 which failed with a hash mismatch because the current software version was v1.59.5. That package was upgraded and distributed as verified by Winget CLI. However, it still shows in the Software update page as v1.59.4 and still fails to install.
UniGetUI Log
Package Managers Logs
Relevant information
Not sure how to read these logs in detail, but the Package Manager log has been showing " Found package TeamViewer TeamViewer.TeamViewer on source winget, from version 15.59.3 to version 15.59.5" all day long, yet the Software Update window (screenshot below) still shows v15.59.4 as the available version.
Screenshots below:
Discover Packages shows the correct version and if I install that package, I believe it will work (based on past experience.) Software Updatees shows the incorrect version still being offered. It fails to install.
NLite.NTlite also showed up repeatedly with the wrong version until I ran the update from the Discover Packages version.
Note: Multiple attempts to update TeamViewer from Software Update window have failed today with a hash mismatch, but just as I'm ready to send this, the last attempt actually passed the hash and tried to run. It failed with an exit code 2 and the same wrong package is still being offered in Software Updates.
Screenshots and videos
Discover Packages.pdf Software Updates.pdf