Problems with installing certain Windows Updates

Usage and Config Patch
1

(imported topic written by Alex Alas)

Hello all,

I have a Windows 2003 R2 SP2 server running TEM 8.2.1409.0, also my network is private with no access to the Internet so this is an air-gapped deployment. I’ve seen some errors on some machines when installing certain windows updates using my BigFix deployment. After reboot is performed, some actions seemed to fail. After that failing error, The console keeps showing up that those updates are still needed on that machine. I tried to re-apply the Updates again with no luck. If I try to install those same updates using standalone executables, they come back saying the updates are already installed. As example, I have a Windows 2003 machine that keeps being flagged with update KB2810071, KB2837593, and KB2850079. If those updates have been installed correctly, that means the issues I am having are related to the BigFix not able to sense that the updates have bee installed on that computer. Those same updates were installed correctly on another Win2k3 machine and obviously are not being flagged as needed on the second Win2k3 system
Any idea how to fix these kind of issues?

This behaviour is a bit frequent and I would like to find a solution besides ignoring or hiding the alert.

Thanks for your help or input in advance,

V/R,

Alex

2

(imported comment written by sylviabeing)

Hi Alex,

Thanks for reporting this and we are looking into the updates.

We will update you soon after investigation!

Regards,

Sylvia

3

(imported comment written by BaiYunfei)

Hi Alex,

The mentioned KBs were replaced (superseded) by later KBs. They are not needed if you have installed later KBs specified below:

KB2837593 should be superseded by MS14-001 (KB2863902) / MS14-017 (KB2863926) / KB2880529

KB2850079 should be superseded by MS14-023 (KB2878284) / KB2863818

KB2810071 should be superseded by KB2837594 / KB2878281

The 3 KBs above have been superseded, published site: Patches for Windows (English), version 2014.

4

(imported comment written by sylviabeing)

Hi Alex,

Please check the applicability of the following KBs for your system:

KB2863926 or KB2880529;

KB2878284 or KB2863818;

KB2878281

Regards,

Sylvia

5

(imported comment written by atlauren)

Hello,

I have a similar issue with these updates in our 8.2.1409 site. I have a Windows 7 system which shows KB2878316 (MS14-023) in Windows Update; neither that update, nor any of the other MS14-023 variants, show as relevant in BigFix for that system.

Also, none of the other listed KBs show as applicable for this system.

Thank you,

Andrew

6

(imported comment written by sylviabeing)

Thanks Andrew.

Are you using x64 system or x86 system?

I have attached both fixlets for you to verify. Please let me know the output.

Regs,

Sylvia

7

(imported comment written by atlauren)

Hi Sylvia,

This is on an x86 system. The fixlet you provided does resolve as relevant on my system.

-Andrew

8

(imported comment written by atlauren)

Update: After installing these just-released fixlets, KB2878316 no longer shows in Windows Update. (Win7 32bit)

Fixed - 2881009: Update for Office 2013 - KB2881009 - Office 2013 (fixlet:288100901)
Fixed - 2881070: Update for Lync 2013 - KB2881070 - Lync 2013 (fixlet:288107013)
Fixed - 2881079: Update for Visio 2013 - KB2881079 - Visio 2013 (fixlet:288107901)
Fixed - 2881083: Update for Lync 2013 - KB2881083 - Lync 2013 (fixlet:288108301)
Fixed - 2883036: Update for Office 2013 - KB2883036 - Office 2013 (fixlet:288303603)
Fixed - 2883049: Update for Office 2013 - KB2883049 - Office 2013 (fixlet:288304903)
Fixed - 2883052: Update for Office 2013 - KB2883052 - Office 2013 (fixlet:288305203)
Fixed - 2883058: Update for Word 2013 - KB2883058 - Word 2013 (fixlet:288305801)
Fixed - 2883060: Update for Office 2013 Spelling and Grammar Check feature - KB2883060 - Office 2013 (fixlet:288306003)
Fixed - 2883061: Update for Excel 2013 - KB2883061 - Excel 2013 (fixlet:288306103)
Fixed - 2883062: Update for Office 2013 File Input/Output (I/O) component - KB2883062 - Office 2013 (fixlet:288306201)

These were pasted from the client log.

9

(imported comment written by sylviabeing)

This is weird! Microsoft does not say any of these KB supersedes KB2878316…

May I know after all these just-released fixlets installed whether the custom copy still shows relevant?

10

(imported comment written by atlauren)

Hi Sylvia,

The custom fixlet does not, and did not, show relevant for this machine.

-Andrew

11

(imported comment written by sylviabeing)

Thanks Andrew!

I think I need some more time to check the newly released KBs. I will keep you updated!

Regards,

Sylvia

12

(imported comment written by sylviabeing)

Hi Andrew,

We have just verified that KB2883052 has updated the same set of files (products) as KB2878316 in MS14-023. Since KB2883052 was released later, once you installed KB2883052, KB2878316 will not applicable and should not show relevant or required.

The behavior you have observed is expected though Microsoft does not say KB2883052 has superseded KB2878316.

We will publish the updates for MS14-023 so that the fixlets can reflect the applicability correctly.

Thanks for your support and feedback!

Regards,

Sylvia

13

(imported comment written by atlauren)

Hi Sylvia,

Thank you for the confirmation. I’m very pleased to find that something that seemed to make no sense did, in fact, make no sense. :slight_smile:

best,

Andrew

14

(imported comment written by sylviabeing)

Hi Andrew,

Fixlets for KB2878316 in MS14-023 have been republished.

Published site version:

Patches for Windows (English), version 2067.

As spoken before, after you installed KB2883052, KB2878316 should not show relevant in your system.

Thanks for your support! Please let us know if you have any other concern.

Regards,

Sylvia

15

(imported comment written by atlauren)

Thank you!

-Andrew

16

My customer is required to install superseded MS patches as they currently are the only ones the vendor for that appliance has approved. I will recommend that they should contact that vendor but how can they install superseded patches that were once relevant and now are not? Second part is there a way to still deploy the patches that were not superseded when originally added to baseline but prior to action they are now superseded?