Office 2019 Retail update using ODT won't install on standalone PC

Question

We have Office Pro 2019 Retail versions (single purchases) installed on the Win10 22H2 PCs. Microsoft instructions to update Office Pro 2019 RETAIL to next build are to use ODT to download from CDN (on internet connected PC), and that works, got the full next build with cab files. Then copy/move the ODT Tool Folder with the new Office folder to the standalone PC and use the setup.exe /configure option to update the build. We were able to do this update of the original install just one time.

Downloaded new ODT and extracted the setup, xml files and downloaded latest build on 12/7/2023; copied new ODT folder to standalone PC, used original xml to configure/update the build, but now it always errors for "cannot be installed on selected update channel". Have changed the channel (used Monthly for first update that worked before), checked the registry to match what it has, but it won't update. Edited the xml for the UpdatePath = C:\ODT Tool folder to make sure it is looking at the current folder where the new Office files are (registry already has UpdatesEnabled=TRUE) but it won't update. Product Release ID = Professional2019Retail.

Most of the MS responses are for Office 365 or for internet connected PCs; we need specific instructions for Office Pro 2019 retail versions for standalone PCs.

Answer 1

Hi @Galbraith, Fleurette (CONTR)

Thanks for your detailed sharing.

The update channel PerpetualVL2019 is for volume license version of Office Professional Plus 2019, which Product ID is ProPlus2019Volume.

If your Office is retail version of Office Professional 2019, the product ID is Professional2019Retail, the update channel is Current. (Please note, the Channel attribute was changed, for more, you may refer to 'Channel attribute (part of Add element)'.)

I suggest you use one .xml file to download the installation package, and install Office updates.

Because, if you specific "PerpetualVL2019" update channel in .xml file to download the package, then the package is not suitable for retail version of Office Professional 2019.

You may try following .xml file.

<Configuration>
 <Add SourcePath="C:\ODT Tool" OfficeClientEdition="64" Channel="Current">
 <Product ID="Professional2019Retail">
  <Language I="en-us"/>
</Product>
</Add>
  <Display Level="Full" AcceptEULA="TRUE" />
</Configuration>

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

---

Answer 2

sorry for late response:
I checked the registry again today and there WAS a change in the versions, but still does not update the Office version when you open Word.
We have same values as your table except for:  (note that the CDNBaseUrl value starting “4923” reflects the Monthly channel) 
ClientXnoneHash = C770D…
InstallID = 4AA24417…
ClientVersionToReport = 16.0.17029.20068     (was 16.0.16626.20086
ClientXnoneVersion = 16.0.17029.20068         (was 16.0.16626.20134)
Of course the O365 entries are not there.
ProductReleaseIds = Professsional2019Retail
UpdateChannel = C:\ODT Tool
UpdateChannelChanged = True
VersionToReport = 16.0.17029.20068        (was 16.0.16626.20314)

Xml to download Office update from CDN will point to location to store the downloaded files (PerpetualVL2019 given as title for the Retail Office 2019):
<Configuration>
<Add SourcePath=”C:\ODT Tool” OfficeClientEdition=”64” Channel=”PerpetualVL2019”>
 <Product ID=”Professional2019Retail”>
 <Language I=”en-us”/>
</Product>
</Add>
</Configuration>

After the download we get the Office cab folder and sample xmls.

Xml to configure/install on standalone:
<Configuration>
 <Add SourcePath=”C:\ODT Tool” OfficeClientEdition=”64” Channel=”Monthly”>
 <Product ID=”Professional2019Retail”>
  <Language I=”en-us”/>
</Product>
</Add>
  <Display Level=”Full” AcceptEULA=”TRUE” />
</Configuration>

In the logs (cannot post them) I see a lot of scenarios being invoked, some don't run, not applicable, but nothing that speaks explicitly to the errors.

Answer 3

We tried leaving the channel out of the configure xml, tried Current,

MonthlyEnterprise, nothing seemed to make a change. Continue to get the

cannot be installed on selected update channel error.

What should I see in the log that might point to reason for error?

Answer 4

Product ID is Professional2019Retail. I already said we tried the Current channel for the configure/install. The xml we tried is the same as what you have listed. MS states to use the PerpetualVL2019 for the Professional2019Retail also, so we use that for the download and get the full Office/cab files; any other channel for the download gets the wrong version. See the document that lists all the products applicable to the PerpetualVL2019 channel, includes all of the 2019 products including retail.

After the initial install of 2019, the channel becomes Monthly in the registry; I expected the "Current" value would work since it would look at the registry and go with that, but no it did not. I have not gone to the extreme to change the ID in the registry from the Monthly to Current.

Answer 5

It almost seems like when the initial software was loaded using MS instructions that is assigned the wrong channel to begin with in the registry, otherwise why would it still be showing the Monthly ID? There is not a "Current" channel ID that I've seen so I can't just change that in the registry.