Demitrius Nelon

There are several different features related to required installer privileges and UAC prompts: https://github.com/microsoft/winget-cli/issues/218 https://github.com/microsoft/winget-cli/issues/271 https://github.com/microsoft/winget-cli/issues/281 We will need to look at adding this as a feature for Inno installers...

Is there any chance you could share the log?

If a UAC isn't acknowledged, there is a timeout period where the client assumes a failure and will continue running the upgrade all process.

@anirugu we aren't fully supported on Windows Server yet (Windows Server 2022 should be considered experimental). We're building the business case with a community [discussion](https://github.com/microsoft/winget-cli/discussions/2361). There are some larger concerns...

There are a couple of related Issues: * https://github.com/microsoft/winget-cli/issues/2434 * https://github.com/microsoft/winget-cli/issues/2436 Is the "App Installer" preinstalled on that VM? Is the Microsoft Store enabled to get an update to "App...

It must. I'm not sure how those SKUs (Azure VMs) are configured.

This has been addressed with `winget upgrade --all`. For individual packages, we aren't able to determine if the latest available package is "newer" than the one installed since the package...

Unfortunately, we can't trust the "displayName" property as it usually contains a "marketing version" rather than a "software build version".

Is this issue resolved with the improvements in [Windows Package Manager 1.3](https://github.com/microsoft/winget-cli/releases/tag/v1.3.2091)?

@lychichem I don't recall another feature on the backlog addressing a generic reboot required. Would you mind a more generic title change? "Inform users a reboot is required after installation"....