none
Office 365 Client Updates Failing 0x80040154 (-2147221164) RRS feed

  • Question

  • I have an issue on a handful of computers (Less than 10 of 200), where Office 365 updates are failing to download.
    Other updates are succeeding, like monthly cumulative windows 10 updates.


    0x80040154
    This error code is not in the windows update error codes list: https://support.microsoft.com/en-ca/help/938205/windows-update-error-code-list
    Probably the SCCM Error:
    [SA fail if SWD not working] createInstance failed for UpdateServiceManager FFFFFFFF80040154
    Class not registered
    https://technet.microsoft.com/en-us/library/bb632794.aspx

    Checking C:\Windows\CCM\Logs
    "ScanAgent.log" "SrcUpdateMgr.log" "UpdatesStore.log" "WUAHandler.log" "UpdatesHandler.log"
    Found these:

    Initiating Scan. Forced = (0)	UpdatesHandler	8/9/2017 2:06:20 PM	10988 (0x2AEC)
    Successfully initiated scan for job ({6837DB27-C51F-41FB-9928-14CE2F0FA8B7}).	UpdatesHandler	8/9/2017 2:06:20 PM	10988 (0x2AEC)
    Scan completion received for job ({6837DB27-C51F-41FB-9928-14CE2F0FA8B7}).	UpdatesHandler	8/9/2017 2:06:20 PM	10856 (0x2A68)
    Evaluating status of the updates for the job ({6837DB27-C51F-41FB-9928-14CE2F0FA8B7}).	UpdatesHandler	8/9/2017 2:06:20 PM	10856 (0x2A68)
    Initiating download for the job ({6837DB27-C51F-41FB-9928-14CE2F0FA8B7}).	UpdatesHandler	8/9/2017 2:06:20 PM	10856 (0x2A68)
    Bundle update (d5644af5-8678-43b2-a708-47441edb8964) is requesting download from child updates for action (INSTALL)	UpdatesHandler	8/9/2017 2:06:20 PM	10856 (0x2A68)
    Ignoring update state (DOWNLOAD_READY) change in job state (2)	UpdatesHandler	8/9/2017 2:06:20 PM	8212 (0x2014)
    Starting download on action (INSTALL) for Alternate Update (d66521cc-f0b2-4361-b568-ee14ccc02173)	UpdatesHandler	8/9/2017 2:06:20 PM	10856 (0x2A68)
    BeginDownload alternate update content failed. Error = 0x80040154	UpdatesHandler	8/9/2017 2:06:20 PM	10856 (0x2A68)
    CBundledUpdate -- Failed to download update (d66521cc-f0b2-4361-b568-ee14ccc02173). Error = 0x80040154	UpdatesHandler	8/9/2017 2:06:20 PM	10856 (0x2A68)
    Ignoring update state (DOWNLOAD_READY) change in job state (2)	UpdatesHandler	8/9/2017 2:06:20 PM	10988 (0x2AEC)
    CDeploymentJob -- Failed to download update (d5644af5-8678-43b2-a708-47441edb8964). Error = 0x80040154	UpdatesHandler	8/9/2017 2:06:20 PM	10856 (0x2A68)
    Download completed for the job ({6837DB27-C51F-41FB-9928-14CE2F0FA8B7}).	UpdatesHandler	8/9/2017 2:06:20 PM	10856 (0x2A68)
    Successfully sent job ({6837DB27-C51F-41FB-9928-14CE2F0FA8B7}) success completion to the SdmAgent	UpdatesHandler	8/9/2017 2:06:20 PM	8212 (0x2014)
    CompleteJob received from SDM.	UpdatesHandler	8/9/2017 2:06:20 PM	10856 (0x2A68)
    Complete - Job ({6837DB27-C51F-41FB-9928-14CE2F0FA8B7}) Cleanup.	UpdatesHandler	8/9/2017 2:06:20 PM	10856 (0x2A68)
    CompleteJob - Job ({6837DB27-C51F-41FB-9928-14CE2F0FA8B7}) removed from job manager list.	UpdatesHandler	8/9/2017 2:06:20 PM	10856 (0x2A68)
    
    This error seems to usually be associated with a DLL that's failed to register.


    I've tried:
    ccmrepair.exe.
    Windows update troubleshooter (  https://support.microsoft.com/en-us/help/4027322/windows-update-troubleshooter ) failed to identify any problems.
    Manual windows update repair.bat

    REM Reset Windows Update
    REM https://support.microsoft.com/en-us/help/10164/fix-windows-update-errors
    REM https://support.microsoft.com/en-ca/help/971058/how-do-i-reset-windows-update-components
    REM https://helpdesk.hemmera.com/helpdesk/ticket.aspx?nonew=-5&tid=10969
    
    
    REM !!!THIS SCRIPT DOESN"T INCLUDE THE REINSTALL OF WINDOWS UPDATE!!!!
    echo '!!!THIS SCRIPT DOESN"T INCLUDE THE REINSTALL OF WINDOWS UPDATE!!!!'
    Timeout 20
    
    
    
    
    Stop the BITS service, the Windows Update service, and the Cryptographic service. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
        net stop bits
        net stop wuauserv
        net stop appidsvc
        net stop cryptsvc
    
    Delete the qmgr*.dat files. To do this, at a command prompt, type the following command, and then press Enter:
    Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"
    rmdir /Q /S %windir%\softwaredistribution\
    mkdir %windir%\softwaredistribution
    REG DELETE HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate  /F
    
    REM If this is your first attempt at resolving your Windows Update issues by following the steps in this article, you should skip step 4 and go to step 5. You should follow step 4 at this point in the troubleshooting only if you cannot resolve your Windows Update issues after you follow all steps except step 4. (Step 4 is performed by the "Aggressive" mode of the Fix it Solution that was mentioned earlier.)
    REM    Rename the softare distribution folders backup copies. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
    ::        Ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak
    ::        Ren %systemroot%\system32\catroot2 catroot2.bak
    REM    Reset the BITS service and the Windows Update service to the default security descriptor. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
    ::        sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
    ::        sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
    
    :: At a command prompt, type the following command, and then press Enter:
    cd /d %windir%\system32
    :: Reregister the BITS files and the Windows Update files. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
    
    regsvr32.exe /s atl.dll
    regsvr32.exe /s urlmon.dll
    regsvr32.exe /s mshtml.dll
    regsvr32.exe /s shdocvw.dll
    regsvr32.exe /s browseui.dll
    regsvr32.exe /s jscript.dll
    regsvr32.exe /s vbscript.dll
    regsvr32.exe /s scrrun.dll
    regsvr32.exe /s msxml.dll
    regsvr32.exe /s msxml3.dll
    regsvr32.exe /s msxml6.dll
    regsvr32.exe /s actxprxy.dll
    regsvr32.exe /s softpub.dll
    regsvr32.exe /s wintrust.dll
    regsvr32.exe /s dssenh.dll
    regsvr32.exe /s rsaenh.dll
    regsvr32.exe /s gpkcsp.dll
    regsvr32.exe /s sccbase.dll
    regsvr32.exe /s slbcsp.dll
    regsvr32.exe /s cryptdlg.dll
    regsvr32.exe /s oleaut32.dll
    regsvr32.exe /s ole32.dll
    regsvr32.exe /s shell32.dll
    regsvr32.exe /s initpki.dll
    regsvr32.exe /s wuapi.dll
    regsvr32.exe /s wuaueng.dll
    regsvr32.exe /s wuaueng1.dll
    regsvr32.exe /s wucltui.dll
    regsvr32.exe /s wups.dll
    regsvr32.exe /s wups2.dll
    regsvr32.exe /s wuweb.dll
    regsvr32.exe /s qmgr.dll
    regsvr32.exe /s qmgrprxy.dll
    regsvr32.exe /s wucltux.dll
    regsvr32.exe /s muweb.dll
    regsvr32.exe /s wuwebv.dll
    
    :: Reset Winsock. To do this, at a command prompt, type the following command, and then press Enter:
    netsh winsock reset
    :: If you are running Windows XP, you have to configure the proxy settings. To do this, at a command prompt, type the following command, and then press Enter:
    :: proxycfg.exe -d
    :: If you are running other versions of Windows, at a command prompt, type the following command, and then press Enter:
    netsh winhttp reset proxy
    :: Restart the BITS service, the Windows Update service, and the Cryptographic service. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
    
        net start bits
        net start wuauserv
        net start appidsvc
        net start cryptsvc
    
    REM From https://social.technet.microsoft.com/Forums/en-US/55a42d60-1432-4ab3-8804-1efede6788af/windows-10-1703-and-wsus?forum=win10itprogeneral	
    	bitsadmin.exe /reset /allusers
    	wuauclt.exe /resetauthorization /detectnow
    	wuauclt.exe /reportnow
    
    REM Windows Vista only: Clear the BITS queue. To do this, at a command prompt, type the following command, and then press Enter:
    :: bitsadmin.exe /reset /allusers
    
    
    REM Install the latest Windows Update Agent.
    
    REM Restart the computer.
    
    REM Get SCCM to do an updates scan cycle
    REM https://www.systemcenterdudes.com/configuration-manager-2012-client-command-list/
    WMIC /namespace:\\root\ccm path sms_client CALL TriggerSchedule "{00000000-0000-0000-0000-000000000113}" /NOINTERACTIVE
    
    REM Reboot (twice) and check C:\windows\ccm\logs\scanagent.log    with CMTRACE.exe
    


    SCCM is version 5.00.8498.1711
    Windows update version: 10.0.14393.1378
    Client: Windows 10 1607 with July 2017 CU applied.  Microsoft Windows [Version 10.0.14393]
    Microsoft Office 365 ProPlus - en-us 16.0.7167.2060 and 16.0.7967.2139 (I don't think the specific version effects this issue as I'd tried updating from 16.0.7167.2060 to 16.0.7967.2139 and the issue persists.)
    This issues has happened to these computers for all of the Office 365 updates. The same GPO's and settings of the working computers are applied. No gpo processing errors.


    Wednesday, August 9, 2017 9:46 PM

Answers

  • I tried an "SFC /Scannow" and it didn't resolve the problem either.

    Uninstalled office 365.
    Did an SCCM updates scan cycle, waited till the update disappeared from software center.
    Reinstalled office 365.
    Did an SCCM updates scan cycle, waited till the update appeared in software center.
    Installed without error!


    I'm not sure if the steps above were excessive and an office online repair might have resolved. the issue.


    • Marked as answer by berwin22 Wednesday, August 9, 2017 10:48 PM
    Wednesday, August 9, 2017 10:48 PM

All replies

  • I tried an "SFC /Scannow" and it didn't resolve the problem either.

    Uninstalled office 365.
    Did an SCCM updates scan cycle, waited till the update disappeared from software center.
    Reinstalled office 365.
    Did an SCCM updates scan cycle, waited till the update appeared in software center.
    Installed without error!


    I'm not sure if the steps above were excessive and an office online repair might have resolved. the issue.


    • Marked as answer by berwin22 Wednesday, August 9, 2017 10:48 PM
    Wednesday, August 9, 2017 10:48 PM
  • Hi Experts, 

    I am also facing the same issue office updates is getting failed with the error code 0x80040154(-2147221164), we are downloading the office updates to SCCM once the update is completed we will be creating a new SUG and schedule the deployment for the PC in the environment. 

    We see this update is getting installed successfully in some PC and getting failed in some PC with the same error code given above. 

    1. Ran the cycles from configuration manager in control panel

    2. Uninstalled and re-installed SCCM still the same issue 

    3. Tried repair also still the same issue 

    but if we open office application either excel or work and give update this is working fine the update is getting installed successfully without issues and the error is getting disappeared from the software center. 

    Kindly suggest us how we can resolve this issue. 

    Thanks

    Balaji S

    Thursday, March 29, 2018 11:39 AM
  • Hi MS,

    I have the same exact issue. Reinstalling office is not an answer for the failure of a 365 update. I have the below error on 200 systems and it is not due to Metered networks because I don't have any. Can we get a answer on this. I can't reinstall office on 200 systems every 6 months when applying updates..

    11751 Updates failures   occurred during enforcement of this assignment -2147221164 80040154 Class not registered

    Thanks

    Dan

    Monday, April 15, 2019 2:53 PM
  • Hello Dan,

    I too was frustrated by the lack of "workable" solutions provided by M$, check this thread out.

    https://social.technet.microsoft.com/Forums/en-US/bcb666bf-3b47-43f3-b823-1338cf2e9164/office-365-client-update-current-channel-16104-32bit-edition-is-failing-with-error-8007007e?forum=ConfigMgrCompliance

    I'm about to attempt the uninstall of the O-Suite, however this isn't a solution for a failed update.

    Office 365 Client Update - Semi-annual Channel (Targeted) Version 1808 for x86 based Edition (Build 10730.20280)

    Getting 0x800775F0(-2146994704) after Status: Failed

    JKB

    Thursday, April 18, 2019 4:59 PM
  • Hello All,

    As workaround try deleting the Updates folder in 'C:\Progam files (x86)\Microsoft Office\' and then start the update again.

    KY

    Tuesday, July 2, 2019 9:29 PM
  • Where I work, the update fails 100% of the time. Like you I remove Office but I just reinstall right away and the update takes without issue.
    Thursday, July 18, 2019 9:25 PM
  • I agree, this is a horrible waste of time uninstalling and reinstalling Office to fix an update failure especially if it happens on a large number of machines. I emailed my coworkers this "fix" and management stated that it is to NOT be considered a fix for the update issue. Until one is presented by the "right" people, this will have to do.
    Thursday, July 18, 2019 9:31 PM
  • Tried that, sorry it didn't work.
    Thursday, July 18, 2019 9:31 PM
  • I'm having the exact same error on a number of my workstations.  I have had a ticket open with Microsoft support but they appear to be stumped as well - I keep getting my ticket shuffled off to other escalation areas.  If anyone has any other tips on this, please let me know.

    --darth.mongo

    Friday, October 18, 2019 4:22 PM