[Update Request]: Microsoft.Office version 16.0.17531.20046

rhj-kinsley commented 3 months ago

What type of update are you requesting?

A new version of an existing package

Current Package Identifier

Microsoft.Office

Package Version

16.0.17531.20046

Please describe the changes you would like to see

No response

Dragon1573 commented 3 months ago

@rhj-kinsley - Could you please manually close this issue as "completed"? As this issue is successfully fixed by pull request #149367 🎉

PsyEng commented 3 months ago

There´s a little issue here, because the installer (setup.exe) has the version 16.0.17531.20046, but the latest version of Office is 17425.20176, which could be seen here https://learn.microsoft.com/en-us/officeupdates/microsoft365-apps-security-updates. This problem led me to an update via winget, although my office is up to date. In addition, a number of additional packages were installed, which is not desired.

PckgrBot commented 3 months ago

This hasn't been an issue on previous updates. We will need to check what has changed on Office side.

PsyEng commented 3 months ago

@PckgrBot Thanks for the quick reply. Here are some information, about my actual case. I installed Office manually with the ODT (Office deployment tool) over a year ago, which is the installer from the winget package Microsoft.Office, which showed me an update today, so I thought, I can safely update it. After that, it has installed me several other components, which I never installed before and which I excluded by the first install I made.

Because the installer has the version number 16.0.17531.20046, but Microsoft Office itself has only the verison number 17425.20176 (which is 16.0.17425.20176), it shows me now an update, even after I´ve updated the version with winget.

rhj-kinsley commented 3 months ago

@PckgrBot Thanks for the quick reply. Here are some information, about my actual case. I installed Office manually with the ODT (Office deployment tool) over a year ago, which is the installer from the winget package Microsoft.Office, which showed me an update today, so I thought, I can safely update it. After that, it has installed me several other components, which I never installed before and which I excluded by the first install I made.

Because the installer has the version number 16.0.17531.20046, but Microsoft Office itself has only the verison number 17425.20176 (which is 16.0.17425.20176), it shows me now an update, even after I´ve updated the version with winget.

I am seeing this as well on my end when I go to upgrade the Microsoft.Office package.

eric9586 commented 3 months ago

Seeing similar issues. Blank slate on Windows 10 Pro test VM.

PS C:\Windows\system32> winget install microsoft.office
Found Microsoft 365 Apps for enterprise [Microsoft.Office] Version 16.0.17531.20046
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://officecdn.microsoft.com/pr/wsus/setup.exe
  ██████████████████████████████  7.37 MB / 7.37 MB
Successfully verified installer hash
Starting package install...
Successfully installed
PS C:\Windows\system32> winget upgrade
Name                                      Id               Version            Available            Source
---------------------------------------------------------------------------------------------------------
Microsoft Teams (work or school)          Microsoft.Teams  24033.813.2773.520 24060.2623.2790.8046 winget
Microsoft 365 Apps for enterprise - en-us Microsoft.Office 16.0.17425.20176   16.0.17531.20046     winget
2 upgrades available.

PckgrBot commented 3 months ago

@Trenly

Trenly commented 3 months ago

@Trenly

You might have to add AppsAndFeatuesEntries to the manifest @PckgrBot

PckgrBot commented 3 months ago

@Trenly

You might have to add AppsAndFeatuesEntries to the manifest @PckgrBot

I can do that but I'm just trying to work out why it's now out of whack and not matching up :/

PsyEng commented 3 months ago

@Trenly

You might have to add AppsAndFeatuesEntries to the manifest @PckgrBot

I can do that but I'm just trying to work out why it's now out of whack and not matching up :/

It seems that the ODT did receive an update after the Office suite this month. This month, Office received the update at the 9th and ODT at the 15th.

Also, the version of the ODT is ahead of the other Office update channels, like the "Monthly Enterprise Channel", which version number is way lower, then the "Current Channel" of the office suite.

So enterprise installations, will nearly ever have a lower version number and must complain about an update.

The ODT is only for installing office, not office itself, also the installer has to be run with a config file, or it will download a basic installation, which could not be intended, because it can also install the "normal" retail versions of office and not only the 365 version.

The installer itself (which is basically this whole package), doesn't install itself to the system, it even doesn't left a trace to the system, as far as I can see it (maybe it left some registry keys, but I doubt it), which means, you check the version against the office installation and not against the tool itself, which is definitely wrong.

Im aware about the problem, that at this point (as far as I/we know it), there's no proper way to safely get the correct version of the tool, which means, it couldn't be updated with winget.

Maybe someone could search for some traces in the registry to correctly determine the version of the installer to ensure a correct update of the ODT itself. Office should update itself automatically, which could be configured with the configuration file for the ODT.

Edit: The link at site of the ODT tool ODT release history page downloads the Downloader of the ODT tool "officedeploymenttool_17531-20046.exe", which then downloads the "installer.exe" and some configuration files, which then can be used to install the office suite. This package does only download the "installer.exe" and runs it directly, without any options/parameters, which then leads to an unwanted installation to anyone, which installed the office suite, with their own configuration, what happend to me yesterday. It overwrites the current installation without any warning or whatsoever.

I'm pretty sure I the "officedeploymenttool_17531-20046.exe" installer in another winget package yesterday, have to confirm it later, when I'm at work at my computer and will update my comment or post a new one, to confirm it.

PsyEng commented 3 months ago

I´ve checked winget and found the package Microsoft.OfficeDeploymentTool (ODT), named "Office Deployment Tool", which currently has the Installer-URL https://download.microsoft.com/download/2/7/A/27AF1BE6-DD20-4CB4-B154-EBAB8A7D4A7E/officedeploymenttool_16731-20398.exe If you run the program, it downloads the "setup.exe" in the version 16.0.16731.20398 and 4 "configuration.xml" files, which contains default settings for different installation types of the office suite. The package Microsoft.Office, named "Microsoft 365 Apps for enterprise", which has the link https://officecdn.microsoft.com/pr/wsus/setup.exe downloads always the latest version of the "setup.exe" (currently 16.0.17531.20046) without the "configuration.xml" files. The package Microsoft.Office isn´t required and is definitly (in my humble opinion) missleading, because it´s not the office suites, which the description implies.

PckgrBot commented 3 months ago

@stephengillie can you review these comments? I'm wondering if we need to modify this package.

stephengillie commented 3 months ago

So essentially there are 2 issues:

Newer version of Microsoft.Office (16.0.17425.20176) has been released, and should be added to the manifest. Because this Issue's version immediately needs an upgrade.
- If a vanity URL is in use, then previous manifests should be removed too.
Microsoft.OfficeDeploymentTool is like a multi-installer, adding Microsoft.Office, Microsoft.Teams (and I'm guessing Microsoft.OneDrive) to the system - these are frequently licensed and bundled as a productivity suite, which is why they have a bundled installer.
- If it's possible to specify individual software packages through installer switches, then this could be considered almost like a very complicated vanity URL for that package, and could be merge with that package's manifest in some way. Possibly also with Commands to run the ODT to install the other software package.
- If it's not possible to specify which package is installed, then this might be communicated through the locale file, or might become a good reason to remove the package and prevent further confusion. I'm not sure which would be the best route.
- A DisplayVersion in the AppsAndFeaturesEntries might allow for specifying the ODT's installed version while using another package's version as the PackageVersion, but the use case doesn't sound like ODT sould ever become upgraded - and instead installed from a vanity URL, used immediately, and allowed to self-uninstall.

treysis commented 3 months ago

Probably winget shouldn't be used to update an Office installation, but just be used for new installs, unfortunately.

Anyways, I created a PR to revert the Microsoft.Office manifest to the current version of Microsoft 365: https://github.com/microsoft/winget-pkgs/pull/150300

PsyEng commented 3 months ago

Probably winget shouldn't be used to update an Office installation, but just be used for new installs, unfortunately.

Anyways, I created a PR to revert the Microsoft.Office manifest to the current version of Microsoft 365: #150300

Probably. Thanks for the PR :) I think, the issue could be closed, or not?

microsoft / winget-pkgs