False positive in fixlet 1511665?

We are noticing what appears to be a false positive in MS15-116, KB3085561. Machines are reporting the update as missing yet the patch cannot be installed as it reports it is already installed on the system. This seems to be due to the relevance is using the older style detection logic and is looking explicitly for the patch GUID for KB3085561 but the update has actually been applied by the December non-security update KB3114329 which also has newer files than those in KB3085561.

Can fixlet 1511565 be updated to use the logic that caters for this scenario? It look like fixlet 1511623 for the 64 bit version of KB3085561 already contains the logic to cater for this scenario.

Thanks & Regards
Rob

1511665 - MS15-116_ Security Update for Microsoft Office to Address Remote Code Execution - Publisher 2013 SP1 - KB3085561.bes (88.8 KB)

Hi Rob,

Thanks for reporting this to us!

Please try the attached custom copy of Fixlet 1511665 and let us know how it works!

Best Regards,
Sylvia

Hi Sylvia, thank you

The fixlet appears to correct the false positive. Several machines showing relevant for the current fixlet are not showing relevant for this custom fixlet.

Regs
Rob

Hi Rob,

Thanks for the update! There are other customers reporting issue with the same fixlet.

We are waiting for confirmation from other customer’s test as well. The content will be updated once we get the feedback.

Regards,
Sylvia

Great news. Thank you Sylvia

Regs
Rob

Hi Rob,

The change has been published.

Published site version:

Patches for Windows, version 2854.

Regards,
Sylvia

hello i am on the latest site version but it appears i have a machine still having this issue with showing relevance and then error code returned when attempting to deploy the fixlet is that it is already installed yet it still shows relevance… any help?

Hi Jensunm,

Please contact IBM support and open a Salesforce ticket for your issue along with the following information:

  1. client log with the error code you mentioned.
  2. Export the installer key from the native registry of the affected machine:
    “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer” of native registry
  3. any other proof of patch already installed or log

Regards,
Sylvia