Office 2016 32Bit KB4011139 issue

Recommended Posts

xendrome    4,433

Hey guys, running out of ideas here.

 

Just deployed Office 2016 standard onto 82 computers.... everything went well, going from Office 2007 which was uninstalled first. EXCEPT ONE COMPUTER.... seriously... my luck

 

So this install went fine, then comes the updates. The OS is Windows 10 1703 x64, WSUS server so all the clients are now in the Office 2016 group and getting the same updates.

 

The update that fails is KB4011139 https://support.microsoft.com/en-us/help/4011139/october-3-2017-update-for-office-2016-kb4011139 and the update that is suppose to install along with it per the KB, KB4011135 went just fine. The error code that shows up in Windows Update is

 

"0x80070643

 

I have tried

 

1: Downloading the update standalone

2: Uninstalling/Repair installing Office 2016

3: Using the Office 2016 Removal tool to clean out the install

4: CHKDSK /F

5: Clear the Catroot2/SoftwareDistribution folders and resetting SC permissions

6: Disabling Trendmicro Officescan

 

 

It seems that WindowsUpdate.log has been done away with and there is some new complicated process to view the log files in Windows 10 - https://support.microsoft.com/en-us/help/3036646/how-to-read-windows-update-logs-in-windows-10-version-1607

 

Anyone here setup to view these that can assist or have any other ideas on what to try?

Share this post


Link to post
Share on other sites
Circaflex    3,010

Is the unit that is failing, the one that had 2007 left on it? 

Share this post


Link to post
Share on other sites
xendrome    4,433
44 minutes ago, Circaflex said:

Is the unit that is failing, the one that had 2007 left on it? 

Same procedure on each one, I uninstalled Office 2007, office file validation tool, and rebooted. Then installed Office 2016, activated with MAK key, then ran update check.

 

 

Share this post


Link to post
Share on other sites
+Mando    3,631

probs a total curveball but.........you dont think it could be related to the same issue you found with Trend and post fall KB? I know its not the fall update your working on but........

Share this post


Link to post
Share on other sites
xendrome    4,433
1 minute ago, Mando said:

probs a total curveball but.........you dont think it could be related to the same issue you found with Trend and post fall KB? I know its not the fall update your working on but........

Doubt it, I've got like 84 other workstations running the same OS version and Office 2016 install without any issues. This one is the only one.

Share this post


Link to post
Share on other sites
xendrome    4,433

Here is the WindowsUpdate Log of the failure. Anyone know of any way to view any additional info for the MSP install? I've checked Event Viewer>System/Application and Windows Update Log there

 

2017/10/16 18:32:39.3069927 3844  3776  Agent           [0]0F04.0EC0::10/16/2017-18:32:39.306 [agent]*  START  *  Installing updates CallerId = UpdateOrchestrator
2017/10/16 18:32:39.3069936 3844  3776  Agent           [0]0F04.0EC0::10/16/2017-18:32:39.306 [agent]Updates to install = 1
2017/10/16 18:32:39.3087741 3844  3776  Agent           [0]0F04.0EC0::10/16/2017-18:32:39.308 [agent]  Title = Update for Microsoft Office 2016 (KB4011139) 32-Bit Edition
2017/10/16 18:32:39.3087802 3844  3776  Agent           [0]0F04.0EC0::10/16/2017-18:32:39.308 [agent]  UpdateId = 1D7ED09B-9C5B-454A-ADBC-A997A71C8862.200
2017/10/16 18:32:39.3087805 3844  3776  Agent           [0]0F04.0EC0::10/16/2017-18:32:39.308 [agent]    Bundles 1 updates:
2017/10/16 18:32:39.3087824 3844  3776  Agent           [0]0F04.0EC0::10/16/2017-18:32:39.308 [agent]      B059CA21-AE51-4AAD-9BEB-D47C68802DAF.200
2017/10/16 18:32:39.5605078 3844  4524  Agent           [0]0F04.11AC::10/16/2017-18:32:39.560 [agent]WU client calls back to install call {1057E456-AFF9-4D24-8543-737A423CDFC4} with code Call progress and error 0
2017/10/16 18:32:39.6529517 3844  3776  DownloadManager [0]0F04.0EC0::10/16/2017-18:32:39.652 [agent]Preparing update for install, updateId = B059CA21-AE51-4AAD-9BEB-D47C68802DAF.200.
2017/10/16 18:32:39.6532879 8268  11600 Handler         [0]204C.2D50::10/16/2017-18:32:39.653 [lib]* START *   MSI Install
2017/10/16 18:32:39.6532882 8268  11600 Handler         [0]204C.2D50::10/16/2017-18:32:39.653 [lib]Updates to install = 1
2017/10/16 18:32:39.6552788 8268  11600 Handler         [0]204C.2D50::10/16/2017-18:32:39.655 [lib]Extracting MSP file stored in CAB ppaddin-x-none.cab
2017/10/16 18:32:41.2644784 8268  11600 Handler         [0]204C.2D50::10/16/2017-18:32:41.264 [lib]MSP update {B059CA21-AE51-4AAD-9BEB-D47C68802DAF}.200 using full-file patch
2017/10/16 18:32:41.2644828 8268  11600 Handler         [0]204C.2D50::10/16/2017-18:32:41.264 [lib]Batch installing 1 updates
2017/10/16 18:32:41.4733269 8268  11600 Handler         [0]204C.2D50::10/16/2017-18:32:41.473 [lib]List of MSPs in transaction:
2017/10/16 18:32:41.4733285 8268  11600 Handler         [0]204C.2D50::10/16/2017-18:32:41.473 [lib]  C:\WINDOWS\SoftwareDistribution\Download\65ec6a16fd5f8859e461f63fcac54c5f\img\ppaddin-x-none.MSP
2017/10/16 18:32:41.4733311 8268  11600 Handler         [0]204C.2D50::10/16/2017-18:32:41.473 [lib]MSP final command line: DISABLESRCPROMPT=1 LOCALCACHESRCRES=0 NOLOCALCACHEROLLBACK=1 REBOOT=REALLYSUPPRESS MSIRESTARTMANAGERCONTROL=Disable
2017/10/16 18:32:41.7102569 8268  11600 Handler         [0]204C.2D50::10/16/2017-18:32:41.710 [lib]MSP Error List:
2017/10/16 18:32:41.7102572 8268  11600 Handler         [0]204C.2D50::10/16/2017-18:32:41.710 [lib]  No messages in the MSP error list.
2017/10/16 18:32:41.7102575 8268  11600 Handler         [0]204C.2D50::10/16/2017-18:32:41.710 [lib]MSI transaction completed. MSI: 0x80070643, Handler: 0x8024200b, Source: No, Reboot: 0
2017/10/16 18:32:41.7102623 8268  11600 Handler         [0]204C.2D50::10/16/2017-18:32:41.710 [lib]Updating status for update 0.
2017/10/16 18:32:41.7102655 8268  11600 Handler         [0]204C.2D50::10/16/2017-18:32:41.710 [lib]First failure for update {B059CA21-AE51-4AAD-9BEB-D47C68802DAF}, transaction error = 0x8024200b, MSI result = 0x80070643, MSI action = <NULL>
2017/10/16 18:32:41.7103637 8268  11600 Handler         [0]204C.2D50::10/16/2017-18:32:41.710 [lib]Sending completion notification for update 0 ({B059CA21-AE51-4AAD-9BEB-D47C68802DAF}.200).
2017/10/16 18:32:41.7104343 8268  11600 Handler         [0]204C.2D50::10/16/2017-18:32:41.710 [lib]Stopping on first error due to FailOptTerminate.
2017/10/16 18:32:41.7113935 8268  11600 Handler         [0]204C.2D50::10/16/2017-18:32:41.711 [lib]Operation failed at update 0, Exit code = 0x8024200B
2017/10/16 18:32:41.7113941 8268  11600 Handler         [0]204C.2D50::10/16/2017-18:32:41.711 [lib]* END *   MSI Install
2017/10/16 18:32:41.7390328 3844  3776  Agent           [0]0F04.0EC0::10/16/2017-18:32:41.739 [agent]LogHistory called. idUpdate={1D7ED09B-9C5B-454A-ADBC-A997A71C8862}.200, resultMapped=80070643, resultUnMapped=80070643
2017/10/16 18:32:41.7440826 3844  3776  Agent           [0]0F04.0EC0::10/16/2017-18:32:41.744 [agent]Install updates CallerId = UpdateOrchestrator

 

Share this post


Link to post
Share on other sites
+T3X4S    4,432

To install :

KB4011139

you need 

 KB4011135

and to install  KB4011135, you need to have Office 2016 already installed.

What order are you doing everything ?

Sorry - I cant provide any inside help on Win10.

If it were Outlook - then I have the keys to the kingdom . :/

Sorry.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.