What exactly does KB2952664 do?

Mike,

I am quite happy with Windows 7 .... no need for me to pre-empt Google and load Linux at this time since Extended Support for Windows 7 lasts until 2020. By that time, I suspect there will be other Operating Systems to choose from.

As far as Linux having a critical flaw for the last 15 years, I won't dispute that ... but Microsoft also has its share of software with long-standing critical flaws:

http://www.pcworld.com/article/2158860/microsoft-will-patch-ie-zero-day-but-doesnt-give-timeline.html

http://www.computerworld.com/s/article/9242469/Hackers_exploit_critical_IE_bug_Microsoft_promises_patch

http://www.computerworld.com/s/article/9231396/Microsoft_confirms_hackers_exploiting_critical_IE_bug_promises_patch

But this thread is not about vendors who have software products with long standing bugs ... this thread is about Microsoft refusing to provide details to their customers about a specific fix (KB2952664) that is supposed to "make improvements to the current operating system in order to ease the upgrade experience to the latest version of Windows."

You have to admit the description provided by Microsoft is rather vague .... and since the fix is rated as "important", then I believe customers have a right/need to know what makes this fix so important? What is wrong with the current upgrade process that needs to be fixed, and how does KB2952664 fix it? And what would the consequences be if one initiated an upgrade to Windows 8.x without first installing KB2952664?

It's not a lot to ask ... Microsoft could easily answer these questions ... if they truly cared about good customer service (and had nothing to hide).

Microsoft and many others who provide software updates rarely if ever are too descriptive about exactly what an update does, so I don't see what all the fuss is about re this one.

Re it's rating as 'important', Microsoft obviously feel that it is for those who are planning to upgrade to Windows 8, and again, why is that a problem in this case? Upgrading from one OS to another has never been an exact science for many, and Microsoft are trying to make that part better at least, bearing in mind that they have the devil's own job encouraging users to stay with an front end that is radically different.

There were many who did have issues upgrading in the first months of Windows 8, so one can hardly blame Microsoft for trying to make it all better. Quite how that equates to Microsoft being secretive is eluding me at present.

If computer users think that Microsoft is underhand, why aren't they using Linux or MacOS. It isn't like there are no alternatives, although in my opinion, Linux and MacOS are poor alternatives.. :-)

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.

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.

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.