MECM M365 updates stopped working since Version 2104 (Build 13929.20408)

Butler, Rick [USA] 1 Reputation point
2021-08-13T15:44:25.663+00:00

I am having a problem with ECM not updating office. Last month and now this month I cannot update these clients to the latest monthly enterprise update build numbers. We never deployed a channel change and the existing systems are on Monthly Enterprise already. I have read about DLL version mismatches for the "C:\Program Files\Common Files\microsoft shared\ClickToRun\APIClient.DLL" but it does not make sense to have to remediate so many clients and none of the articles really explain what DLL version you would actually need to find and replace on these machines.

This is my configuration, the only thing that seems out of place is the "ClientVersionToReport" reading as "16.0.13929.20250" and the "ClientXnoneVersion" and "VersionToReport" reading as "16.0.13929.20408".

My actual M365 Apps report in the GUI as "16.0.13929.20408"

Does anyone know of any better explanation of this issue? Does anyone know where or which APICLIENT.DLL might be needed to fix this?

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration]
"ClientXnoneVersion"="16.0.13929.20408"
"CDNBaseUrl"="http://officecdn.microsoft.com/pr/55336b82-a18d-4dd6-b5f6-9e5095c314a6"
"VersionToReport"="16.0.13929.20408"
"OfficeMgmtCOM"="True"
"AudienceId"="55336b82-a18d-4dd6-b5f6-9e5095c314a6"
"ClientFolder"="C:\Program Files\Common Files\Microsoft Shared\ClickToRun"
"ClientVersionToReport"="16.0.13929.20250"
"WatcherInterval"="3600000"
"PipelineServerName"="ClickToRun_Pipeline16"
"PackageLockerPath"="C:\ProgramData\Microsoft\Office"
"ScenarioCulture"=""
"InstallID"="AC8AA2A5-BED2-48E4-A2BE-C788F0EDC065"
"Platform"="x86"
"InstallationPath"="C:\Program Files (x86)\Microsoft Office"
"ClientCulture"="en-us"
"AudienceData"="Production::MEC"
"VisioProXVolume.MediaType"="Local"
"O365ProPlusRetail.MediaType"="Local"
"SharedComputerLicensing"="0"
"SCLCacheOverride"="0"
"O365ProPlusRetail.DeviceBasedLicensing"="0"
"UpdatesEnabled"="True"
"ProductKeys"=""
"Activate"=""
"VisioProXVolume.ExcludedApps"="access,groove"
"O365ProPlusRetail.ExcludedApps"="access,groove"
"StreamingFinished"="True"
"ProductReleaseIds"="VisioProXVolume,O365ProPlusRetail"
"O365ProPlusRetail.OSPPReady"="1"
"VisioProXVolume.OSPPReady"="1"
"RSODReset"="False"
"UpdateChannel"="http://officecdn.microsoft.com/pr/55336b82-a18d-4dd6-b5f6-9e5095c314a6"
"UpdateChannelChanged"="False"
"OneDriveClientAddon"="INSTALLED"
"TeamsAddon"="INSTALLED"
"O365ProPlusRetail.TenantId"="xxxxxxxx"
"O365ProPlusRetail.EmailAddress"="xxxxxx@X .com"
"O365ProPlusRetail.OneNoteInUse"="True"
"BackgroundTransportMethodDefault"="CachedHttp"
"ClientXnoneHash"="xxxxxxxxxx"
"StreamPackageUrlChanged"="True"
"BingAddon"="INSTALLED"

Office Management
Office Management
Office: A suite of Microsoft productivity software that supports common business tasks, including word processing, email, presentations, and data management and analysis.Management: The act or process of organizing, handling, directing or controlling something.
2,019 questions
Microsoft Configuration Manager
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. AllenLiu-MSFT 41,136 Reputation points Microsoft Vendor
    2021-08-16T08:50:47.507+00:00

    Hi, @Butler, Rick [USA]
    Thank you for posting in Microsoft Q&A forum.

    We'd like to confirm something with you to make the issue more clearer, when you say "MECM M365 updates stopped working", do you mean the updates not available in SCCM console or deploy these updates to client fail? Could you have a more detailed description about this?


    If the response is helpful, please click "Accept Answer" and upvote it.
    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.


  2. Butler, Rick [USA] 1 Reputation point
    2021-08-20T12:31:56.723+00:00

    Automagically started working with no changes made. I cannot explain why it failed one months updates, then wouldn't update for 2 weeks with the next months update. Updatedeployment.log kept indicating the updated was "missing" i/e "not installed" but the clients never prompted for updates.