winget-cli: Office upgrade does not work
Brief description of your issue
I have the following package which is listed twice when entering winget upgrade: Microsoft 365 Apps for enterprise [Microsoft.Office] Version 16.0.14527.20234
Every time I enter winget upgrade --all I have the following problem: When winget tries to update the 2 office packages, a window is displayed which is black and has no output but the office icon. After 2-3 min the update probably completes because the window disapears and winget moves on.
After entering winget upgrade the Microsoft 365 Apps is still displayed in the list of upgradeable packages. Maybe the updater for office could be improved as well. (Not only a black window) I also noticed that when I open a Office App and check the version from within the app it displays that it is up to date. So it appears that it is only updated because I use winget.
Steps to reproduce
Install Microsoft Office for Enterprise. execute winget upgrade --all
Expected behavior
The Office packages should be updated.
Actual behavior
The feedback of the update process is bad (black window). After the update it is still listed as upgradable in winget.
Environment
Windows Package Manager v1.1.12986
Windows: Windows.Desktop v10.0.19043.1288
Paket: Microsoft.DesktopAppInstaller v1.16.12986.0
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 7
- Comments: 20 (4 by maintainers)
This is still an (annoying, occurring repeatedly) issue. Pinning the version cannot be the solution. Any plans to fix this?
We’re close with the release of WinGet 1.5 (it’s in Release Candidate mode). Pinning is a stable feature in WinGet 1.5
Thanks for mentioning pinning. I am using it and it is really a good workaround. I am looking forward for it being included into the regular release. How to use it now?
winget settings
This opens a text editor! with the JSON configuration file:winget pin add Microsoft.Office
How does it look like?
The work on pinning should help a little here. At least, you can pin the packages that are causing trouble so
winget upgrade --all
will skip/ignore the pinned packages.Office has a very complex installer mechanism, and we’re still working with them on improvements to the installer flow so we can give a better experience with WinGet.
I noticed this today. It looks like winget wants to install the “Current Channel” but we are on the “Monthly Enterprise Channel”
https://learn.microsoft.com/en-us/officeupdates/update-history-microsoft365-apps-by-date
I’m not aware of any way to tell winget to install the Monthly Enterprise Channel. Perhaps one day, it will see which channel you’re on and pull from that.
winget upgrade --all
looping update not sucessfull updateafter period time, even its say successfully installed,
I think this can be related to this issue, so I did not open a new one. I tried pinning
Microsoft.Office
just now, got the messageNo installed package found matching input criteria.
.Logs from command
winget pin add Microsoft.Office
Click to expand
Seems
winget-cli
struggles when an app is listed as installed twice?Edit: Never mind, it worked if using
--id
.I see something similar:
This is with Winget v. 1.4.10052.
Office apps themselves indicate that my organization is on the Semi-Annual Enterprise Channel with Office version 2202. So I suspect that the problem has to do with Winget somehow comparing that against what’s available in the Monthly Enterprise Channel v. 2210.
As others have noted, installing/upgrading superficially seems to succeed, but subsequent calls to
winget upgrade
indicate that the version(s) have not actually changed. I can’t help wondering if this comes down to a permissions issue: in many (most?) organizations, the ability to install/upgrade Office apps requires elevated permissions. Could it be that only IT admins are allowed to perform such upgrades, and that Winget is merely mishandling the fault condition and improperly reporting success?Update
I’m seeing this with Winget v1.8.924-preview.
My organization is currently using Office version 2402. Same apparent problem as a year ago: Winget does not seem to honor the governing upgrade channel, and therefore makes an inappropriate version comparison, leading to a false mismatch and a noninstallable “upgrade”.
Yes, we’re really frustrated with the state of winget being pushed by default with every win 11 installation, and we’ll have to support this dumpster fire that is this package manager.
Meanwhile, winget PMs are happily getting their christmas bonus and enjoying their holidays. https://github.com/microsoft/winget-cli/issues/1684