What exactly does KB2952664 do?

I do know this. I encourage my local clients to install all Microsoft updates (including KB2592664) other than for hardware, and I do it for the three computers here that run Windows 7, and so far, none of us have experienced any problems which can be accredited to Microsoft updates..

I used the term "fix" in my last response, when I really meant "update" ... sorry for any confusion I may have caused.

You are very fortunate to not have experienced any problems that were accredited to Microsoft updates.

I realize that you stated "other than for hardware" ... but consider the update KB2862330. This was a security update that came out as part of MS13-081 and would have been automatically installed by anyone who had their Windows Update setting on Automatic. The description in MS13-081 does not mention hardware, but says this: "The security update addresses these vulnerabilities by correcting the way that Windows handles specially crafted OpenType Font files and specially crafted TrueType Font (TTF) files, and by correcting the way that Windows handles objects in memory." Many people who installed this update subsequently experienced a blue screen.

Below is an excerpt from Microsoft's description of known issues with KB2862330. While not everyone who installed KB2862330 experienced the known problems described below, many did .... my point being that someone with Windows Update set to automatic could end up installing an update that subsequently caused a blue screen ... so before I install the monthly updates, I prefer to wait a few weeks (except for updates that address zero-day issues) and do some research to see if any of the monthly updates are known to be causing problems after being installed.

I have used System Restore on my Windows 7 computer, but I find that mitigating a problem like the one shown below is seldom as simple as going back to the previous Restore Point ... I'd rather do my due diligence up front and avoid problems like this:

[excerpted from KB2862330]

Known issues with this security update

Symptoms

After you install this security update on a computer that is running Windows 7 SP1 or Windows Server 2008 R2 SP1, you may receive a D1 or 100000D1 stop error message that resembles the following:

*** STOP: 0x000000D1(parameter1, parameter2, parameter3, parameter4)

DRIVER_IRQL_NOT_LESS_OR_EQUAL

Cause

The installation of security update 2862330 should update all the drivers for the USB 2.0 core stack. However, in some specific computer configurations, the Usbport.sys driver is not updated. After the USB 2.0 core stack is in a partly updated state, a D1 or 100000D1 Stop error may occur.

The stop error is observed in any of the following situations:

• When the computer is transitioning to or from a lower power state (Sleep or Hibernation)
• When a USB port resumes from "selective suspend" mode
• During the installation of the update itself

Mike, have you never installed a fix from Microsoft, only to find that the fix had a problem and resulted in a subsequent crash or blue screen .... causing you to waste time figuring out how to remove the errant fix?

Yes to the first part when I have installed a fix which pretty much matches the problem encountered. But as it says on any Microsoft Fix page, unless the problem exactly fits what the fix is set to resolve, it shouldn't be used. So, we give it a go anyway.. whoops..

System Restore is reliable and fast in Windows 8, one of the features which Windows 7 users may appreciate having, so little is lost..

KB2592664 isn't a fix per se. It is an update and may just make the upgrade process quicker or add an extra line of instruction to make something clearer. Does it really matter? No, it does not..

I do know this. I encourage my local clients to install all Microsoft updates (including KB2592664) other than for hardware, and I do it for the three computers here that run Windows 7, and so far, none of us have experienced any problems which can be accredited to Microsoft 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.

Mike,

For those customers who are planning to upgrade their existing computer to the latest version of Windows, then KB2592664 may be "important" ... but Microsoft has not provided a reason for its importance other than the vague statement that it will "ease the upgrade experience".

For customers who have decided to keep the version of Windows currently running on their PC because Windows 8.x does not provide any features they want/need (and does provide a UI that they definitely do not want), then KB2592664 is superfluous. Marking KB2592664 as "important" will result in all of these customers (who do not intend to upgrade, but have set their Windows Update option to automatic) having a superfluous fix installed on their computer (hopefully in this case, KB2592664 is benign ... but we don't know that for sure because Microsoft refuses to provide any details on what KB2592664 does).

Mike, have you never installed a fix from Microsoft, only to find that the fix had a problem and resulted in a subsequent crash or blue screen .... causing you to waste time figuring out how to remove the errant fix? If you have gone through that frustrating experience, then you can understand why one would want to avoid installing superfluous fixes .... even if they are marked as "important".

I think there are plenty of examples of Microsoft providing more technical details in the description of a fix ... so why not do so with KB2592664 ... but I realize that by now my point is moot .... Microsoft is not likely to update the description of KB2592664 now (sigh).

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.

Unless microsoft answered on THIS thread, I'd never know the answer.  As I said earlier, I had given them two chances to explain in windows update by looking for detail (and posted comments to it both times), I will not unhide it and look there again.

It makes me sure I did the right thing letting windows update CHECK but not AUTOMATICALLY install, and it has made me now consider even more what updates I do apply.  Do I now have to check into everything they call "security update" because they may start hiding things that way?  Dunno.  Worse, must I delay every update and check either here or google to see if they snuck something in and called it something else?  Dunno, but it does make me question it now where I hadn't done that before.