I believe there is a detection flaw in fixlet 447551903 for KB4475519, possibly also fixlet 447551901. Machines with Office 365 (based on Office 2016) start showing applicable for the fixlet after Project 2013 has been installed. This is because Project 2013 adds the product ID 00005109A20000000100000000F01FEC for Microsoft Office 64-bit Components 2013 which is one for the IDs the fixlet relevance uses as a detection method for Lync 2013 / Skype for Business 2015. The update will not install and is not applicable as it reports that “the upgrade patch cannot be installed because the program to upgrade is missing or may require a different version of the program”. Can the relevance for the fixlet be looked at and updated please to avoid this false positive? Maybe add a qualification check like exists regapp “lync.exe” whose (version of it = “15”)
We don’t want to check the “lync.exe” regapp since we don’t want the relevance to target only Lync/Skype for Business.
I would expect the fixlets for KB4475519 to become relevant for systems with Project 2013 SP1 installed since Project 2013 contains a component targeted by the update.
Updates for the Office family aren’t restricted to the specific product labeled by the update. If the update patches a shared office component, then the update will apply to any Office product (whether Word, Project, Excel, Skype for Business, etc) with that shared component.
This is easily demonstrable by installing a standalone Office product like Project or Skype for Business and doing a Windows update scan. The scan will return updates labeled for Office, Word, Excel, etc… all of which can be applied despite not having those specific products.
This is basically explained in Scenario 3 from this KB article: https://support.microsoft.com/en-us/help/830335
The team did some testing on your specific scenario and were able to apply the KB4475519 update on a system with only Project 2013 SP1 installed and on a system with both Office 365 (2016 version) and Project 2013 SP1 installed.
Is your Project 2013 at the SP1 level?
Another thing is maybe try a repair of Project 2013 and/or Service Pack 1 and try reapplying the update.
Thanks @BMA. I’ll do some further digging as I was also able to install the patch on O365 after installing Project 2013 SP1 on a test system.