Are you seeing update KB 3185319 being offered for Internet Explorer?

Topic

New Reply

Günter Born just reported that he’s seen two cases of Win7 users being offered KB 3185319 — an update from Sept. 13, 2016 — as a checked Important u
[See the full post at: Are you seeing update KB 3185319 being offered for Internet Explorer?]

1 user thanked author for this post.

Elly

Reply | Quote

Replies

Perhaps it took MS 30 months to remove the bugs?

5 users thanked author for this post.

plodr, Microfix, Myst, Great Lake Bunyip, woody

Reply | Quote

Six or eight months ago, on several of my Win7 computers (both hdw installs and VMs) and for several months running, I had a yellow warning triangle on the Internet icon in the system tray. Hovering over it said “No Internet access,” but there WAS Internet access. This did not happen to all the Win7, just several.

I was finally offered KB 3185319 on those computers. Thought it was odd but installed it anyway. Whatever it did, the yellow caution triangle went away.

@Microfix asked me about it a couple of days ago. It had showed up on his Win 8.1 (It’s an IE11 CU, if I remember). I told him my story. He installed it.

Microsoft – quien sabe!!

4 users thanked author for this post.

gborn, Myst, Great Lake Bunyip, woody

Reply | Quote

PKCano wrote:

Microsoft – quien sabe!!

Solo MS sabe y no hablan. But what else is new, eh?!

MacOS iPadOS and sometimes SOS

Reply | Quote

and posted #1015627

PKCano wrote:

I told him my story. He installed it.

not quite, time for you to revisit your DM, patch was already installed.

Windows - commercial by definition and now function...

Reply | Quote

I’ve seen it on 8.1.

2 users thanked author for this post.

Microfix, bassmanzam

Reply | Quote

Some weeks ago I had offered in Windows Update a patch dating to January, that I hid on advice from Woody that said it was unnecessary, because it fixed things of no importance. This last one, though, must break the record for ancient origins.

And: no, I have not had it offered. Only the three updates for Office 2010 and MSRT for April.

Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

Reply | Quote

? says:

i have not checked for updates since the last green light for march patches on 4/2, however; i did see this post on seven forums that says it was being offered to some lucky folks last November:

https://www.sevenforums.com/windows-updates-activation/417298-why-windows-update-offering-me-kb3185319-now.html

KB3185319 was a garden variety specially crafted webpage RCE, i guess:

https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2016/ms16-104

on a side note when i ran DISM after updating it pulled KB3033929 from 3/15 that was causing problems at that time with Linux dual boot rigs…

Reply | Quote

KB3185319 has been installed on my Win7 computers since October 2016. It is not being re-offered to me via Windows Update. On the other hand, the last IE cumulative update which I have installed is the December 2018 update. I wonder what will happen if I install the latest IE cumulative update. Will KB3185319 suddenly be re-offered by Windows Update?

Reply | Quote

I think this is offered once a total re-installation of W7 or W8.1 has been done. It hasn’t happened on our other devices only this one which had an annual nuke and refresh of W8.1 over a month ago.

Still..it begs the question as to WHY it takes SO long to distribute a patch from Sept 2016 to a system that prior to this, was completely up-to-date for over a month!

 

Windows - commercial by definition and now function...

Reply | Quote

Windows 7 Pro x64…This one was installed on my system 09/16. Not being offered again.

Reply | Quote

KB3185319 was always offered to Win 7/8.1 if the last installed Monthly Rollup is Preview (because it does not have supersedence metadata)

on December 2018, we got out-of-band IE11 CU KB4483187, which took KB3185319 place in the above equation

now, they have expired (removed) KB4483187 from WU (still available for Catalog and maybe WSUS)
so, KB3185319 back in the equation

yet, they did not have the guts to expire this forsaken, old, superseded update
Update for Adobe Flash Player for Windows 8.1 (KB4462930)

3 users thanked author for this post.

GoneToPlaid, PKCano, woody

Reply | Quote

That explains it.

Wotta mess…..

Reply | Quote

Seems the answer then is the 3 Ms – Microsoft’s Mangled Metadata.

2 users thanked author for this post.

woody, abbodi86

Reply | Quote

it seems the KB4462930 flash update for Win8.1 contains some files that were not included in newer flash updates like KB4477029, KB4471331 etc. that’s why I was still allowed to install the KB4462930 update for win8.1, even though I had any newest flash update installed like KB4493478 (and did not get “this update is not applicable to your computer” message with KB4462930 for 8.1)

1 user thanked author for this post.

woody

Reply | Quote

It’s not, it’s completely replaced, bit by bit

you don’t get the “this update is not applicable to your computer” for the same reason we need metadata (refresh or expire) to get rid of KB4462930

CBS applicability mechanism have some limitations that prevent declaring supersedence:

– if an update contain a new component which do not exist in the base RTM components store
e.g. IE11 CU

– if an update contain new “major” version of an existing component
e.g. Adobe Flash update 7.3.9600.x vs. inbox version 6.3.9600.x

– if an update share the same version of some components with newer update
e.g. .NET Rollups

actually, Monthly Rollups and Win 10 CUs falls into the 3rd limitation, but they solve that by linking (chain) all updates with CBS Package Name, which always declare supersedence

there are also two Win 8.1 updates which do not have above limitations, yet they need WU metadata to supersede them
i never managed to understand why
Windows Defender update KB3038936
Quick Note-Taking update KB2968599

3 users thanked author for this post.

GoneToPlaid, PKCano, woody

Reply | Quote

in any case, I’ll just manually download & install the KB4462930 flash win8.1 update from the MS Catalog site and it won’t overwrite any updated adobe flash files since I already have the newest flash update installed on win8.1 and windows update will never offer KB4462930 again.

but at least KB3185319 is NOT showing up thru WU on my Win8.1 machines that already have the April 2019 IE update installed.

Reply | Quote

I installed it back in 2016.  Group A.  No problems  W7x64 , Home Premium, AMD. Not being offered again.

Reply | Quote

I recently did a WU scan on my Win7 machines that already had KB4483187 IE11 update installed and WU now offers the IE11 KB3185319 update again.

PKCano is definitely spot on with MS’s screwed up metadata with older IE updates

Reply | Quote

I am not experiencing this behavior with Win8.1 as the IE11 KB3185319 update is not being offered to Win8.1 systems as I just did a recent WU scan on a Win8.1 laptop which already had either KB4493446 or IE11 KB4493435 update for 8.1 (AND older IE11 updates like KB3185319 and KB4483187 are not installed on 8.1)

the 3185319 problem seems to be recently happening only to Win7 systems

Reply | Quote

It won’t show up unless you install preview rollup KB4493443

Reply | Quote

fortunately I do not install any preview rollups for 8.1.

even after installing the newly released KB4499151 rollup update on 5/14 does not make WU offer KB3185319 (and 3185319 is not even installed on the Win8.1 machine)

Reply | Quote

On April 6 I have installed Windows 7 x64 from scratch on one of my systems. I installed from a DVD including SP1, then used WSUS Offline Update to bring the computer up to date, but, as always, I then needed to install more updates through Windows Updates because WSUS Offline Update does not install all necessary updates. I have never installed any rollup  preview. But since today (possibly yesterday, but I did not check then), I see KB3185319. I have not seen it before.

Reply | Quote

interestingly enough the IE11 KB3185319 update for Win7 is included in the August 2018 Windows 7 SP1 US English ISOs [7601.24214.win7sp1_ldr_escrow.180801-1700]- Windows Update will not offer this when clean installing Win7 SP1 from the Aug. 2018 W7 ISO images (unless KB3185319 was removed)

Reply | Quote

After applying the April updates to a Win 8.1 system WU offered the 3185319 patch.  All of the above discussion is interesting, but the real question remains unanswered.

Should this old patch be installed?

Reply | Quote

I have installed it without any adverse effects on my systems.

If you read above, there is a discussion about why it is being offered. It has to do with metadata and supercedence. Windows Update will not overwrite more recent files in its installation, so the worst that could happen is that it does nothing but satisfy the supercedence requirements.

Reply | Quote

Thank you for your reply.

If the only purpose for installing 3185319 is to address the “Microsoft’s Mangled Metadata” problem then this seems to be something that can be ignored for the time being (wait for MS to clean house) unless the 3M problem can result in WU failing to offer necessary updates in the future.

Reply | Quote

(wait for MS to clean house)

How long do you expect to wait on Microsoft? LOL
You can fix it now by just letting it install.

Reply | Quote

I have no positive expectations with respect to MS and WU.

As a practical matter, if it’s still being offered after Woody has gone to Defcon 4 for the May offerings I’ll most likely install it.

Reply | Quote

you’re better off installing the KB3185319 update and keeping it on there (whether using Win7 or Win8.1) since there’s no way to tell whether or not MS will fix their screwed up WU metadata problem with 3185319

Reply | Quote