-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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]: CologneCodeCompany.XYplorer #211377
Comments
We've found some similar issues:
If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.
|
✅ Issue verified.
|
Here's the URL in the existing manifest: https://www.xyplorer.com/download/XYplorer_26.70_Install.exe According to the vendor, the versioned package links are available in the forum: https://www.xyplorer.com/xyfc/viewtopic.php?p=190279&hilit=download+url#p190279 I just think that the winget package manifests should use these xx.xx.xxxx versioned package links rather than the vanity xx.xx URLs. |
Version But version Edit: The last valid |
The only available release format on Download Center are ZIP and RAR archives. I can't sure how previous contributors find this EXE install wizard. 😕 The above EXE URL with |
The Moving forward, the InstallerUrl in the manifests for XYplorer should be in the XX.YY.ZZZZ format: https://www.xyplorer.com/download/XYplorer_XX.YY.ZZZZ_Install.exe This should ensure proper updates to official releases and resolve the hash mismatch error. |
…02 (#211382) Signed-off-by: Dragon1573 <[email protected]>
Please confirm these before moving forward
Category of the issue
Installer hash mismatch.
Brief description of your issue
XYplorer updates do not (ever?) work with winget. I've never had this application update successfully using winget.
Steps to reproduce
winget upgrade CologneCodeCompany.XYplorer
Actual behavior
Installer hash does not match.
Expected behavior
Upgrade successful.
Environment
Screenshots and Logs
The text was updated successfully, but these errors were encountered: