Important installation sequence to avoid degraded functionality for MS15-065

Usage and Config Patch
1

You must follow an installation sequence when applying Fixlets for Internet Explorer versions 7, 8, 9, 10 and 11.

Refer to the following for the sequence of applying the Fixlets to the corresponding Internet Explorer version. Failure to follow the installation order or failure to install the subsequent updates can lead to degraded functionality.

Follow the sequence of applying the Fixlets depending on the Internet Explorer versions:

Internet Explorer 7, Internet Explorer 8, and Internet Explorer 9

  1. KB3065822
  2. KB3074886

Internet Explorer 10 and Internet Explorer 11

  1. KB3065822
  2. KB3074886
  3. KB3075516

To align with the required installation sequence from Microsoft’s installation instructions, only Fixlets for KB3065822 will show as relevant if no patches from MS15-056 are being installed for the applicable Internet Explorer versions. After the Fixlets for KB3065822 are applied and the computer is restarted, the rest of the Fixlets for the other KBs become relevant in the order that the KBs should be installed.

To find out more about the sequence of installation for Internet Explorer updates, see the installation instructions in the following:

1 Like
2

The relevance isn’t doing what you’re saying WRT forcing ordered installation of 1 and 2. 2. KB3074866 is relevant without 1. KB3065822 installed. However, relevance for 3. KB3075516 is checking and requiring that 2.KB3074886 is installed as you stated. The MS documentation says 1 and 2 must be installed in sequence. Will you be updating the relevance for KB3074886 or is this how it was intended? Thanks

3

I’m not seeing KB3075516 in the IEM console, even though the other 2 that you mentioned are there.

4

That’s correct. KB3075516 shouldn’t be relevant (visible) until KB3074886 is installed. But according to the original post, KB3074886 should also not be relevant (visible) until KB3065822 is installed and that’s not the case.

5

Specifically the issue re not checking for KB3065822 (if there is one) appears to be with fixlets 15065121, 15065129, 15065135, 15065149, 1506573, perhaps more.

6

Hi dhtorsdc,

Thanks for reporting this issue. There were a few Fixlets (15056121, 15056129, 15056135, 15056149) for Windows 2008 R2 that have the relevance checking for KB3065822 missing. They have been updated in the latest published site Patches for Windows (English), version 2281.

Note: For 1506573, the relevance checking for KB3065822 exists. This Fixlet was not updated. Kindly help to verify whether there is indeed an issue with this Fixlet.

Thank you!

7

Thanks. With regard to 1506573, my console was showing it was relevant to a handful of machines. Turns out that an operator had installed KB3065822 this morning on a few machines. So 1506573 seems correct. Thanks again!