What exactly does KB2952664 do?

my pc user score was 7.1 for my processor and after i installed this it was 4.9??

pauluk1978,

You had a very interesting effect from KB2952664.

When it first came out, I hid KB2952664 and never installed it. Just recently, I looked at the list of updates that I have hidden, and KB2952664 is no longer listed! I searched my installed updates, and it is not listed there either.

Microsoft never did provide an adequate explanation of what KB2952664 really does. You may just want to hide it (right click KB2952664) in Windows Update and select Hide.

langware...

Now, for me, you have brought up an even greater concern.  You see, I did install KB2952664, and since then I can no longer install any updates.

I have run a couple "FIX-it' solutions to no success.  Having read this thread, and hearing no proven benefit, I am going to uninstall the update and see if I can then install updates.

I think it doesn't matter anymore if you consider this "answered".  It's been over a month; by now EVERYONE who automatically installs updates has done it, EVERYONE who manually does but generally accepts all has done it, and almost everyone who questions them has either installed it or hidden it.  They have no reason to be more forthcoming, and users likely don't care anymore.

I agree with you. At this point, those with Windows Update set to Automatic (i.e, install updates automatically) have already installed KB2952664 ... regardless of whether they ever intend to upgrade their current computer to Windows 8.x .... and those customers who do not intend to upgrade to Windows 8.x, and examine the monthly fixes in order to manually install those they want/need, have probably hidden KB2952664

I can't resist this (modified) quote from a favorite movie:  "What we have here is failure [on Microsoft's part] to communicate."

Like you, I have my Windows Update setting to check but not automatically install. Unless a fix is meant to address a critical zero-day security issue, I usually delay installing for several weeks ... while I check Google for problems that have come up with any of the monthly fixes .... it's amazing how many serious problems (such as blue screens) turn up in the few weeks after a fix is released (ever get the feeling that you are an unwilling beta tester for Microsoft's fixes). For the cases where customers report serious problems after installing a fix ... unless Microsoft subsequently releases an update to fix the fix ... I just hide it. I do not have the time or desire to be a beta tester for Microsoft's fixes.

Maybe a preemty strike to clear problems for installing Windows 10

Langware, good pursuit; may be useful to consider this:-

I trial any software on the home PC before letting it anywhere near our busy I.T. based office. When 8 arrived it was duly installed and evaluated, but would have caused far too much disruption and cost us thousands in lost business and delays responding to clients. Fixing the PC was easy, just install Classic Shell which has no adware or similar, then turn off the areas on the screen, after all, do we really want or need touch screen on a desktop when typing and eating a greasy chicken leg?

There are advantages to 8.1, it appears to need less performance to run, the home P.C. is an elderly Compaq with a minor memory upgrade and flies now, even though it isn't yet upgraded with an SSD like the office P.C.s

If we update at the office it will be immediately followed by an install of Classic Shell, so the staff member can get on and work without frustration.

This update has been re-released this week and appears in Windows Update as "important", even if previously hidden. The KB article has been updated to show the last review (Oct 14) and revision (2.0), but with no additional information about what the update actually does, or whether it serves any purpose at all for those who have no intention of ever "upgrading" from Windows 7 to Windows 8/8.1.

I hid it the first time around after reading this thread, and have not noticed any issues at all caused by doing so. Under the principle of "if it ain't broke, don't fix it", I will hide it again.

Microsoft does both its customers and itself a disservice by not providing any meaningful information about this (and many other) updates. This has made me skeptical of the "important" classification, and since first reading this thread, I have researched every non-security update, and found that many are equally superfluous.

When in doubt, I hide the update and wait to see if I experience any of the issues it purports to address. So far, nothing.

Caveat emptor.