Flash Player update and KB 2952664

Topic

New Reply

This just in from ER…Adobe has released a new set of Flash Player security updates this Julyin Adobe Security bulletin APSB14-17:https://helpx.adobe
[See the full post at: Flash Player update and KB 2952664]

Reply | Quote

Replies

I had some earlier version of KB2952664 installed, so uninstalled it as you suggested. Then decided I’d let windows ‘check for updates’ to reoffer it. Interestingly enough it did not reoffer it. I’m thinking to leave it off if MS has decided it’s not ‘important’ or even ‘recommended’ anymore.

Woody – Am I making a mistake in not just reapplying it?

Reply | Quote

I uninstalled the old KB 2952664 update and reinstalled the new one, and everything went to hell. My browsers would not work properly, most webpages wouldn’t display properly. Even a simple system restore didn’t fix the problem, what was done was done; or so it seemed. Firefox showed the largest problem, with the most webpages/websites not responding properly. I dinally backed up the pc for the third time, going back 3 months, and that fixed the problem. Reinstalled patches up until the latest black tuesday, and everything works fine so far.

Reply | Quote

@Quick –

Get something posted on the Microsoft Answers forum!

Reply | Quote

@Mike –

If it isn’t in the list, and checked, DON’T go looking for it. Windows Update works in weird ways. If you need it, it’ll show up sooner or later.

Reply | Quote

Did the switcheroo on the update. Win 7 Home Premium, SP1. No issues before, and no issues now. Don’t use Firefox, but Chrome and IE 11 both OK.

Got the latest Flash PLayer for IE 11 in Windows. Chrome for Windows self-updates Pepper Flash. In Linux this issue is complex, as Chromium Browser does not self-update, and the Ubuntu repo never gets a Chromium Update between kernel upgrade releases. (I.E., they’re still on Chrome 34, Stable.)

The Linux way to update Firefox is just to run the Updater, and everything is OK. But Chromium 36 Beta (the current best solution for Ubuntu) does not include Pepper Flash natively (nor certain Google API Keys for some Chrome-like features to be used).

Since I don’t compile from source, I use the method of fetching Pepper Flash from inside the rpm version of the Chrome Beta installer. Which worked fine this time, as long as I manually updated the internal Chromium version so that Pepper Flash would show up as the correct current version when “chrome : plugins” is polled inside the Chromium Browser.

Bottom line — it’s a pain, but in Linux you have to go through a couple of hoops to get the up to date Pepper Flash plugin into Chromium. Linux Chrome should be up to date as long as you get the latest installer directly from Google’s download page.

Since the end of April 2014, Chrome Stable and Chromium Beta for Linux do not support the Firefox-style Netscape Protocol (NPAPI) plugins, including the Adobe version of Flash Player. With the change to the AUR GUI, Chrome for all platforms is going through the same transition, with the same result. Ubuntu’s Chromium Stable will be the same when they upgrade to Chromium 36 or 37 in this Fall with their Ubuntu 14.10 release. The Windows and Mac change is happening with Chrome 35.

Reply | Quote

Today Linux finally got the Flash Player update through normal updates channels. And Windows got Chrome 36. For Linux, this is about a ten-day delay between the exploit being announced and the Pepper Flash plugin being updated. And at least six days since Adobe issued an updated Flash Plugin for Firefox for Linux. Truly sad about the Pepper Flash delay.

Reply | Quote

Woody,
My Flash Player is currently updated to version 14.0.0.125 for both Active X and the plugin for Firefox. I updated them myself when the notification came up from Adobe. I see that the KB2952664 update is part of my July batch of updates (Win 7 x64 SP1). I didn’t install the first one per your instructions for the June updates. Now I’m wondering what this new KB2952664 is going to do to my already up to date Flash player. Should I install it or not?

Being 20 something in the 70's was so much better than being 70 something in the insane 20's

Reply | Quote

Help please. Per your advice, I uninstalled KB2952664 (I think I originally installed it in early July).

KB2952664 is now being offered to me. Should I install it again when the MS-DEFCON condition is raised?

A previous poster mentioned his system went haywire after uninstalling and then reinstalling. I am running Windows 7 Professional…..Thanks.

Reply | Quote

@markjta –

Yep. If it’s checked in your Windows Updates list, install it.

Reply | Quote

@Charlie –

The patch only affects the copy of Flash that’s running inside IE. Go ahead and install it, when the time comes, even ifyou never use IE.

Reply | Quote

Today, September 9, KB2952664 appeared twice in a row on the Important update list with the same 2.5 MB size and the “More Information” descriptions were identical. This update was originally with no known problems in mid July. Long Online chat with Microsoft just now was unproductive and meaningless like the technician never heard of it and gave me a worthless link to kb894199 to refer to. This PC is well protected and maintained and I told that Tech I will not install it until and if the issue is resolved. Frankly, I will not hold my breadth.

Reply | Quote

correction “This update was originally installed (left out the word installed.

Reply | Quote

This morning (10Sep14) the duplicate update entries for kb2952664 were still there. After rerunning Microsoft Check For Updates (ran it multiple times 9Sep14) the duplicate entry has now vanished and only one entry for updating kb2952664 exists. I made no change that would have caused this, perhaps my lengthy conversation with Microsoft Support personnel may have had an impact.

Reply | Quote

@Marty –

It’s entirely possible. Keep pushin’!

Reply | Quote