locked
Office 64-bit updates made available to PCs with Office 32-bit? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi, I'm seeing an issue on some PCs in my environment where Office 64-bit software updates get deployed to systems that only have Office 32-bit installed. The updates will fail to install (because they're not applicable), yet still show up in the Software Center as required. Two examples I pull are the 64-bit versions of KB3114830 and KB3114942. Any ideas?
    Tuesday, April 26, 2016 3:55 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Can you give us a specific example?

    On 64-Bit operating systems with Office 32-bit installed, there are still some 64-bit components of Office.

     

    I hope that helps,

     

    Nash

    Nash Pherson, Senior Systems Consultant
    Now Micro - My Blog Posts
    If you found a bug or want the product to work differently, share your feedback.
    <-- If this post was helpful, please click the up arrow or propose as answer.

    Tuesday, April 26, 2016 4:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Is the computer OS 64-bit? There are some 64-bit runtime components that install to 64-bit computers with 32-bit Office, this is normal. Are you certain they are failing for this reason?

    Jack

    Tuesday, April 26, 2016 4:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    With this specific example, the PC is Windows 8.1 x64. It has Office Professional Plus 2013 SP1 x86 installed. The updates showing in the Software Center are the 64-bit versions of KB3114830 and KB3114942. This particular failure is "Failed to install update(s)". Enforcement error code 0X87D00668, "Software update still detected as actionable after apply". When viewing the list of installed updates on the workstation, neither of those article IDs are found.

    That's just this example. I've had failures in the past related to different article ID's and different error codes. I guess my question is more related to why SCCM thinks a 64-bit version of the product is installed in the first place. If this were expected behavior, I would think we'd be seeing it on every instance of a 64-bit OS with 32-bit office, but we're not. It's seemingly random.


    • Edited by jamccloud Tuesday, April 26, 2016 4:29 PM added additional info
    Tuesday, April 26, 2016 4:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    May be Office was installed 32 bit and project or visio was installed 64 on same PC. Check the PCs appwiz.cpl
    Tuesday, April 26, 2016 5:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yeah that's one of the first things I checked too. For those that have Project & Visio, they're all 32-bit versions.
    Tuesday, April 26, 2016 6:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This post indicates possible corruption of the local updates DB:

    http://www.toddlamothe.com/technology/windows-updates-error-0x87d00668.htm

    Jack


    Tuesday, April 26, 2016 6:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote


    Hi,

    Have you examined the log file WindowsUpdate.log?

    Have you attempted manually install the updates?

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, April 27, 2016 9:28 AM