New cumulative update KB 4491113 for IE in Win7 and 8.1 fixes the backslash bug

Topic

New Reply

Microsoft broke IE’s behavior earlier this month. With the update released yesterday, it’s fixed… but under odd circumstances. Here’s the bigger pic
[See the full post at: New cumulative update KB 4491113 for IE in Win7 and 8.1 fixes the backslash bug]

7 users thanked author for this post.

PhotM, Lars220, abbodi86, SueW, fernlady, Microfix, Elly

Reply | Quote

Replies

Just to clear things up for everyone and myself, I presume this ‘silver bullet’ IE patch can be downloaded/installed for Group A as well as Group B?

No doubt it will be included in the March SMQR, it’s just that IE is integral to both OSes so would seem important.

Don’t ask, don’t know sorta style 😛

Windows - commercial by definition and now function...

Reply | Quote

KB 4491113 has already been added to the downloads on AKB2000003.

2 users thanked author for this post.

OscarCP, Microfix

Reply | Quote

So do we download Both KB4486474 & KB4491113 to update IE11?! Or will just KB4491113 do the job?

Bought a refurbished Windows 10 64-bit, currently updated to 22H2. Have broke the AC adapter cord going to the 8.1 machine, but before that, coaxed it into charging. Need to buy new adapter if wish to continue using it.
Wild Bill Rides Again...

1 user thanked author for this post.

SueW

Reply | Quote

Woody:

@PKCano has added the appropriate admonitions to the “Group B” AKB 2000003 list

Microfix:

Just to clear things up for everyone and myself, I presume this ‘silver bullet’ IE patch can be downloaded/installed for Group A as well as Group B?

I see references to AKB2000003 on more than one occasion in various posts, and at times with no “limiting” preface language as to Group B or Group A. So just to clarify application of this KB and for the future, do KB’s listed in PKCano’s AKB2000003 post apply only to Group B followers? Or can Group A followers also utilize these KB’s such as this one under discussion? (Of course, Group A followers should never utilize a listed KB for the Monthly Security Only update).

And if so, why do you call it “Group B” AKB2000003?

Thanks

 

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

Jargon and lingo, always something new. I can see now how that jump happened.

“AKB” is the AskWoody Knowledge Base articles
https://www.askwoody.com/forums/topic/knowledge-base-listing/

Group B was formulated in response to Microsoft changes in the autumn of 2016. It’s full instructions are kept updated
https://www.askwoody.com/forums/topic/2000003-ongoing-list-of-group-b-monthly-updates-for-win7-and-8-1/

This leaves everyone else in the default class Group A. Those full instructions come in the next article
https://www.askwoody.com/forums/topic/2000004-how-to-apply-the-win7-and-8-1-monthly-rollups/

Sort of a B before A listing.

Reply | Quote

Anon,
Thanks and I am good with all you said. My confusion is that this KB and other KB’s (like the original IE 11 patch KB4486474) are listed under posting AKB2000003 which appears to have been established for Group B Security Only update members.

But then this KB is placed under that AKB200003 post (and even referred to by Woody with the preface “Group B”. This leads one to believe that the KB is only for Group B members/followers and not applicable to Group A members/followers.

I suspect that this KB is applicable to both Group A and Group B, but by including it under AKB2000003 it creates the question of whether it can also be used by Group A members without messing up the Group A Monthly Quality Rollup update installation later on.

Thus my request for clarification. If it can be used by both Groups, maybe it (and future others of a similar nature) should be posted elsewhere?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

The links in AKB2000003 are direct download links to the MS Catalog. There are no restriction who can use the MS Catalog.

Reply | Quote

While it certainly is true that anyone can use the MS Catalog, the MS support pages for the February Rollup and IE 11 patches (KB4486563 and KB4486474, respectively) state that IF you install the Rollup first THEN you should not install the IE 11 patch. I believe that what @tex265 is asking is the converse of the above. In other words, IF I install the IE 11 patch first, THEN should I install the Rollup? I don’t recall this latter question ever being addressed.

Presumably, one should not install Rollup first followed by IE 11 patch because of the possibility of bad things happening? Do bad things happen if IE 11 patch is installed first followed by Rollup?

Reply | Quote

If you are currently experiencing the problem with IE11, installing KB4491113 will fix the problem (whatever Group you are in)
Otherwise, when the DEFCON system approves the Feb patches:

For Feb, Group B installs the Security-only Update for Win and the CU for IE11.

For Feb Group A installs the Monthly Rollup (which includes the CU for IE, so there is not need to install the CU for IE separately)

KB4491113 is an out-of-band patch for IE that contains a non-security fix for a specific problem. If you experience that specific problem after installing the Feb updates (irregardless of which Group), installing  KB4491113 will fix the problem.

If you do not experience the problem (maybe you don’t use IE, for example) you can wait until the March updates which will contain the fix.

5 users thanked author for this post.

Lori, SueW, Lars220, bassmanzam, DrBonzo

Reply | Quote

I am the anon#post-330111. I misread you, and believed you thought the A of AKB defined the Group. Sorry for my confusion, thanks for your patience. I’m not clear on how the edit changed your wording.

As PKCano said anyone can avail themselves of the advice. The Group A method would not bother with the catalog and await the IE11 patch in the next rollup. Note that the MS-DEFCON rating #2 does allow, “Unless you have an immediate, pressing need to install a specific patch, don’t do it.” The corollary being if you judge that you do have a pressing need, prepare your fallback position, then go ahead.

(Of course, Group A followers should never utilize a listed KB for the Monthly Security Only update).

Sure they can. They just don’t have to. The next rollup will cause things to line up with Microsoft’s design anyway, the diversion is only temporary.

For myself, I do not feel pressed. When Windows Update includes this in the Rollup, I will get it.

Reply | Quote

Regarding Group B…

Should we install it “now” or wait for next month’s security only patch?

Do you think this will be added to the I.E security only fix for March?

Reply | Quote

Assuming the metadata and supersedence works as intended..your guess is as good as mine.

Windows - commercial by definition and now function...

Reply | Quote

KB4491113 provides a fix for a specific problem. If you are affected by that problem, installing the patch now will fix the problem.

The fix will not be included in March Security-only Quality Update because it is an update for IE11.

It will be included in the March Cumulative Security Update for IE11. If you are not currently affected by the problem, you can wait to install the CU with the March updates.

6 users thanked author for this post.

Lori, Lars220, abbodi86, SueW, Elly, DrBonzo

Reply | Quote

? says:

thank you, Woody + PK! (yet again i would have no clue, thank you bumbling microsoft) i already patched on Valentine’s day (i know DEFCON 2) not that i look at the pictures , anyway

Reply | Quote

PKCano wrote:

KB4491113 provides a fix for a specific problem. If you are affected by that problem, installing the patch now will fix the problem.

Still looking for clarification, PK… so to get caught up on IE11 (since I update but don’t intentionally use IE, my update options are:

• Download KB4486974 and KB4491113 to catch up, OR
• Download the 2019-03 IE11 Cumulative Security Update for March.

Bought a refurbished Windows 10 64-bit, currently updated to 22H2. Have broke the AC adapter cord going to the 8.1 machine, but before that, coaxed it into charging. Need to buy new adapter if wish to continue using it.
Wild Bill Rides Again...

Reply | Quote

KB4486974 was approved by the Jan DEFCON for installation.

This applies to KB4491113. Are you having the specific problem? This is NOT a fix for a security issue.

When the Feb patches are DEFCON approved, install KB4486474 (or the Rollup for Group A). If you experience the problem, then install KB4491113. (If history serves, KB4491113 will replace KB4486474 (since it is “cumulative”) so you only need latest one. But I have not analyzed the files, so I am speculating at this point). The fix is apparently in the Feb Preview as well, but we don’t install unchecked Previews – Right?

Otherwise, if you don’t experience the problem, the fix will be included in the March CU for IE11 and in the March Rollup.

1 user thanked author for this post.

WildBill

Reply | Quote

Thereagain, we are at MS-DEFCON 2 so..ask yourself this:
How does this patch affect the supersedence if February IE KB4486474 (w7) or KB4486474 (W8.1) Security Only patch isn’t already installed?
I’d say hang off until MS-DEFCON 3 or higher.

Windows - commercial by definition and now function...

1 user thanked author for this post.

woody

Reply | Quote

FWIW, this “silver bullet” isn’t quite ready to be fired; it caused problems with the game Halo: Spartan Strike by omitting some of the sound and then letting the game hang after a few minutes. It may also have caused some problems with videos on Firefox. Upon uninstalling, the Spartan is again killing Covenanters and Prometheans with full sound. 🙂

Windows 8.1; update downloaded from Microsoft Update Catalog.

2 users thanked author for this post.

Microfix, woody

Reply | Quote

As usual, Micrsoft ‘fixed’ something that wasn’t broken. If the URL is malformed (backslashes are not allowed), Web browsers shouldn’t load.

Reply | Quote

Reminds me of when you post  and use the back quote symbol instead of the apostrophe it makes the post look odd and the MVP’s have to correct it.

Reply | Quote

Perhaps this is idiosycratic to my setup, Dell Desktop Computer, Win 7, Group B, Waterfox is my main browser, but KB4491113 caused a significant disruption to my start-up programs and caused other oddities with my boot-up to the desktop, including slowing it down.  Once KB4491113 was removed, via the Windows Update protocol, everything immediately went back to normal.  As Group B IE updates are cumulative, I will wait until the March update appears stable before trying an IE KB.

Reply | Quote

Same with me I’m removing it and waiting until March.

Reply | Quote

Many thanks for your post
it’s solve my problem

Reply | Quote

Is there no fix to this for Windows 10?

Reply | Quote

Yeah, we have only applied the buggy update to Windows 10 and there’s no fix released for that yet 🙁

Reply | Quote

more proof   that the current way of patching is not the best. I still think each patch should be by it self. That patch that broke the sound might fix the / but another patch might break the sound. The current madness means that the GOOD do not get a chance to do their good because the bad parts break them.

Reply | Quote