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
First usage feedback: multiple non-silent fails, one crash, and two types of repeats #1009
Comments
|
@Master-Guy this is awesome feedback! Thank you for taking the time to be so thorough here. There are several different things you are reporting. I think we have Issues for many of them. Be sure to add your There may be a couple of new asks. I don't think anyone has created a new feature to request the ability to specify either a preference or a requirement for a setting in Edit: It's this one #910 Settings for installer modes The "list" command/feature is used to do most of the heavy lifting to match manifests in the source to Apps in Add / Remove Programs. In some cases, an adjustment to a manifest will address failure to update. In other cases, we have features to add additional keys to the manifest to help with better matching. The "main" actionable item we can look at in the client in this issue is "kill a running download when pressing CTRL+C." |
|
Thank you! I'm really looking forward to using this on an enterprise level, but it requires some finetuning :) |
|
We've made improvements for [Ctrl]+[C] in several areas. Can you confirm if the "kill a running download when pressing CTRL+C" is resolved? I believe we've isolated most of the other issues you've reported. The work is ongoing and primarily tracked with #1243. |
|
@denelon thank you for getting back to me. Since I've re-installed my Windows, a lot of the checks are uncheckable for me now. Ryzen fails due to failed version comparison: Discord fails due to it still running:
Unity is still being installed as a separate version when doing |
|
We've been busy making tons of improvements and we're close to getting Windows Package Manager 1.3 flighted for "Windows Insider Release Preview". That's the last step before GA. Are there any problems you're having that haven't been reported yet? I think we're close to being able to close this issue |
Visual Studio
Discord
No indication of installations running
EPIC Games
Run complete
Corsair iCue
|
|
Sorry, wrong button.. |
|
Corsair iCue "might" be willing to give a custom return code so we can inform the user a reboot is required with expected return codes: winget-cli/schemas/JSON/manifests/v1.2.0/manifest.installer.1.2.0.json Lines 172 to 201 in 9056c0f
Otherwise, we would need add "post install display notes" to the manifest: |
What kinds of ideas do you have that might improve this? Windows Package Manager essentially executes the installer and doesn't show progress until we get indication from the installer. Maybe as a more "appealing" placebo, we could have a timeout on the initial message and then switch the message to |
|
Epic Games Error 1603 is returned, but it's a bit unclear to the user. We've been discussing improving the output to the user so they have some idea of what might be happening. The challenge with MSI Error 1603 is it isn't really clear what happened. |
|
Visual Studio I'm not sure what's happening with Build Tools, I'll have to ask around or dig in deeper. |
|
Run complete I'm not sure why logs aren't produced for:
|
|
Appending a message For Epic: Can we ask them to return the correct returncode if it detects the app running? VS Build Tools: My guess is there just isn't a winget package available for that one. |
I'm not sure there is a better return code for MSI installers. There may be an opportunity to return a custom error code. It might also be a good time to consider migrating from MSI to MSIX (assuming there aren't any blockers). At they end of the day, they should be in control of their customer experience.
|










Brief description of your issue
Sorry if this shouldn't be reported this way, but I'm not yet up-to-speed on the Microsoft ways-of-work on Github.
After installing winget-cli this morning, and running
winget upgrade --all, I got the following feedback:Steps to reproduce
Have an old 32-bit version of Teamviewer installed on your 64 machine, together with any old version of the other apps listed below under Actual behaviour.
Then run
winget upgrade --allas administrator in a Windows Terminal session running Powershell as default.Expected behavior
Winget to update these packages, and kill a running download when pressing CTRL+C.
Actual behavior
While downloading the Unity update of 2GB, I pressed CTRL+C because I needed my bandwidth for a Teams meeting, but it seems the download kept running even though I got my Powershell prompt back.
Multiple packages (also a number of packages not listed here) have visible installers. It wouldn't be too much of an issue if these would be running in the background, but they are being pushed as top window, and get the focus of Windows, which makes it possible to accidentally cancel an installation, otherwise interrupt an installation, or close an error message.
Mozilla Firefox, VLC media player, Zoom and Adobe Acrobat Reader DC aren't automatically updating at all with
winget upgrade --alland returnNo applicable update found.when trying to upgrade them one-by-one.Environment
Logs:
DiagOutputDir.zip
The text was updated successfully, but these errors were encountered: