-
Dell Commande Update (Dell.CommandUpdate.Universal) say "Available" when I run:
But when I run: It say: Can someone explain how is that? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
"Available" means that there is a newer version of the package in one of the sources. It doesn't guarantee that the newer package version is able to be installed on your machine. "No Applicable Upgrade" is the indicator that even though a newer version is available, one or more filters are causing the package to not be able to be installed on your system. There are a few reasons this could happen, such as a change in the MinumumOSVersion required for the package, a change in installer type (although I believe this has a separate message), a change in scope (if the package was originally installed in user scope, but the available update only specifies machine scope), even a locale specification could cause an update to be inapplicable. The only way to understand why an upgrade is deemed inapplicable is to run winget upgrade with |
Beta Was this translation helpful? Give feedback.
-
I think there is a real problem here. The verbose log output is over 5MB and still manages to not contain any information about why the upgrade failed... At least, none that's obvious to an end user. I haven't done anything unusual with my winget install. The only maybe weird thing I've done is installed Winget-AutoUpdate. I haven't dug around in the code for that project, but I'd assume it doesn't need to modify anything about winget to function; it should just be using the CLI as-is. Console output for
Here's the end of the log file for this command:
|
Beta Was this translation helpful? Give feedback.
"Available" means that there is a newer version of the package in one of the sources. It doesn't guarantee that the newer package version is able to be installed on your machine. "No Applicable Upgrade" is the indicator that even though a newer version is available, one or more filters are causing the package to not be able to be installed on your system. There are a few reasons this could happen, such as a change in the MinumumOSVersion required for the package, a change in installer type (although I believe this has a separate message), a change in scope (if the package was originally installed in user scope, but the available update only specifies machine scope), even a locale specific…