-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Package Issue]: Discord.Discord requires explicit targeting and upgrade fails with "Installer hash does not match" #136960
Comments
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:
|
Discord is not running while doing the upgrade. |
Can somebody explain or point to a page that explains why some apps require explicit targeting? |
Direct install also failed
|
This might be through pinning.
|
I don't have any pins: > winget pin list
There are no pins configured. Upgrading with explicit targeting works now: > winget upgrade -h Discord.Discord
Found Discord [Discord.Discord] Version 1.0.9031
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://dl.discordapp.net/distro/app/stable/win/x86/1.0.9031/DiscordSetup.exe
██████████████████████████████ 91.7 MB / 91.7 MB
Successfully verified installer hash
Starting package install...
Successfully installed |
Can not upgrade Discord.Discord now:
|
Discord has auto-updated itself from
|
Obviously they don't want to keep their installation package compatible with winget. So why don't they take themselves out of it? It's annoying to have the updates displayed in Winget but not be able to run them. Those at Discord might find that funny. I think it sucks. |
Could it be that all of the Discord packages were marked in the manifest with the flag: Edit: My gut feel is that apps that requires "approval" of Terms of Service after install, are not included in winget. This happened to VMware Workstation a while back IIRC (it has been added ever since... but it's a bit confusing ngl) |
No, that isn’t the issue. The deny behavior was set because Discord has its own auto updater and the updater doesn’t write the new version to registry; attenpting to update Discord using winget would re-install and erase user settings |
The package cannot be upgraded using winget. Please use the method provided by the publisher for upgrading this package. |
This issue is due to poorly-configured installer manifests using the dynamic i.e. : This appears to have been fixed with the current-version manifests. |
Since the above PRs have been merged, I'll assume that this Issue is complete. If this is in error, please @ me and I'll reopen. |
Still getting the error @stephengillie
|
Yes same here. I have to use |
I have found out about this issue after installing UniGetUI to update my softwares with winget, and the only software which had an issue updating was Discord. I wonder if this could be due to the installation of plugins, such as Vencord, I have not checked with a vanilla Discord installation. Meanwhile, uninstalling then installing Discord worked to update the software. I had to install Vencord again afterwards. |
Please confirm these before moving forward
Category of the issue
Installation issue.
Brief description of your issue
Discord upgrade with
winget upgrade -h --all
fails because it requires a explicit targeting.Upgrading with explicit targeting fails with "Installer hash does not match"
Steps to reproduce
Run
winget upgrade -h --all
, then runwinget upgrade -h Discord.Discord
.Actual behavior
After the first command the upgrade is not executed and I get the following message:
After the second command the upgrade is not executed and I get the following error:
Expected behavior
The upgrade succeeds after the first command, or at least after the second.
Environment
Screenshots and Logs
WinGet-2024-01-29-11-47-13.285.log
WinGet-2024-01-29-11-47-20.241.log
The text was updated successfully, but these errors were encountered: