What exactly does KB2952664 do?

And yet once more, does this update rear its ugly head... I am with Lang on this.. I want to KNOW the who's, what's, where, why's & how's, of an update.. an that goes for just why the heck this update is rated as "Important ".

As with Lang... I have No bloody intent to ever, EVER ... do the upgrade to 8x or 8.1... I will wait until Win 10, an only... ONLY after waiting until near the end of the " Free Upgrade " window. My reasons for this is, to avoid being a Win Op Sys guinea pig... period.

I, too, have to agree that it looks to be that a ton of the updates, are more in the nature of "Superfluous"... addressing issues that might or will never come up. To have a whole... ton, of updates that are essentially "useless" is the epitome of stupidity... more so, especially, when you consider that hard drives only have so much space to hold info, an that includes these so called "Important" updates... why have useless

, unnecessary drivel.... clogging up the works, when that space could be better used for more.. important apps, or programs... allowing for the user to do or use their computer for the reason or purpose of having bought it to begin with.

I went through the... nightmare of dealing with an update that  was tagged as "Important", an then not being able to find or install future updates, after having installed that update... ( I do not recall the exact KB number that was used for that particular update) & know that that update was re-released numerous times... unnecessarily... 

But back to the main point of my replying... Like Lang.. I want to know more info before "I" decide to do... "ANYTHING " & can't without "USEFUL" info... an suprisingly... Microsoft... wants to "CLAM UP".... when it needs to be forthcoming with info, if they want to be looked @ as trustworthy... period.

How many Microsoft engineers does it take to screw in a light bulb?

None. They're all too busy trying to screw the users.

That's the only reason I can think of as to why this update shows up once again, after I have hidden it several times. And, as every other time, the "More information" link provides none, other than some vague statement about how it will "ease the upgrade experience."

It is clear that Microsoft keeps trying to sneak this update past us, and it is equally clear that they don't want us to know what it does. I miss the days when I didn't have to research every single Windows update before deciding whether to install or hide it, but that would mean trusting Microsoft, and they are making it very hard to do that.

I will say it again, and again, and again, as many times as they unhide this update:

The moment a company believes itself to be invincible is the moment it begins the process of proving itself wrong.

P.S. Of 15 "important" updates I received today, 10 were security-related. Of the other 5, two were superfluous for me (although they may be needed for others), two were related to "upgrading" or installing "the latest Windows operating system" (the other one to watch out for is KB3021917), and one was to fix problems caused by a previous update.

Caveat emptor.

I just spent a couple hours trying to fix the update failure for this KB2952664. It failed with Error Code 80246007, and I have not been able to successfully fix it using all the many ways given in another thread.

However, my computer is too old ( Dell Dimension 8400 with maximum RAM and hard drive and converted to Win 7) to ever try Win 8.x, so I will just hide this update and go on. Sure wish I had thought to look up what the update actually did before I spent all that time trying to get it to work!

I had to uninstall this patch since it caused an error and Powershell was continuously crashing on me.  Since it is of no importance to me I've hidden it and hope my problem with Powershell stays away.

Thanks Gerry, but I think I'll pass on the installation of this update as I've got all the other ones and can still update new ones that come up. From all the **** I've heard about this update I don't want it to corrupt my boot up.

                                          Thanks for commenting on my problem;

                                                           Omaha Bullock