Relevance issue - MS18-JAN: Security update for Office 2010 - Office 2010 SP2 - KB4011658 Critical

Usage and Config Patch
1

I don’t have Microsoft office installed on this 2008 server, but I do have Microsoft Office 2003 Web Components installed (12.0.6213.1000).

Get the following in the BES log file:
Command succeeded (Exit Code=17028) waithidden __Download\kb24286772010-kb4011658-fullfile-x86-glb.exe /quiet /norestart (group:382762,action:382799)

Ran it manually on the server and got the following message:

Security Update for Microsoft Office 2010 (KB4011658) 32-Bit edition
There are no products affected by this package installed on this system

Please update the relevance.
Thanks,
Scott

2

Have 3 other Windows 7 machines that do have Microsoft office professional plus 2010 installed (14.0.7015.1000)

All three get same exit code: Command succeeded (Exit Code=17028)

Ran it manually on the three workstations and got the following message:

Security Update for Microsoft Office 2010 (KB4011658) 32-Bit edition
There are no products affected by this package installed on this system

Thanks,
Scott

1 Like
3

Machines Failing MS18-JAN: Security update for Office 2010 - Office 2010 SP2 - KB4011658

Greetings All,

Most if not all the machines that are running that patch are failing it with error code 17028. That code indicates “No product installed for contained patch.” Possible bad relevance statement? Anybody else with this issue?

4

yeah, it’s probably just a simple relevance update needed. I noticed this too after accidentally included it in a group selection, it’s showing as relevant to my office 2016 computers, but when pushed it fails of course. still shows as relevant afterwards, etc.

5

@sdemonte @HarthT @Entaille

These seem like related relevance issues with the patches. The patch releases for this month have definitely been unusual.

1 Like
6

That does match the exit code description so both are saying the same thing. Does sound like the relevance needs some tweaking

https://technet.microsoft.com/en-us/library/cc179058(v=office.14).aspx

2 Likes
7

@sdemonte @HarthT @Entaille

I think this has been fixed.

8

Indeed, it has been fixed. Thanks!

1 Like
9

could you suggest, how it has been solved. please share the steps. it would be helpful.