What exactly does KB2952664 do?

Gerry,

Thank you for your excellent responses to my previous post.

In response to my question "Why can't Microsoft incorporate whatever KB2952664 does to improve the upgrade experience into the upgrade itself?" You stated:

Microsoft obviously considers their approach to be the most practical way to proceed. KB2952664 was installed on this computer on 2 August. It had not been hidden. I am not encountering any problems but then updates rarely cause me problems. I am not aware of hidden updates being re-offered. Of course if the software distribution folder is not properly updated you could get what appears to be what you describe. Do you think that it is Microsoft or the user who cause the majority of software distribution problems?

In my case, KB2952664 was first offered (i.e., found in my Windows Update list) on April 22, 2014 (over a year and three months ago). At that time, I hid the update (as you know, hiding an update is a very simple process: right click entry in Windows Update list, select hide). Since that time, and on numerous (but not all) occasions, I have seen KB2952664 removed from the list of hidden updates and placed back into the regular list of updates queued for installation. Since I have opted for manual installation of updates, I never installed KB2952664. Each time I would see KB2952664 appear in the list of updates to install, I would again hide it.

This same thing (KB2952664 being hidden, and then re-appearing in the regular list of Windows Updates) happened on three computers in my home, and (based on responses in this and other threads) has also happened to many others.

You asked: Do you think that it is Microsoft or the user who cause the majority of software distribution problems?

Hard to tell whether Microsoft or users cause "majority" of software distribution issues. In the case of KB2952664 being hidden (by user) and then removed from being hidden to being back in regular list (by Microsoft), I would not classify that as a software distribution problem (to me, a "problem" implies an unintended consequence/result ... and I believe the removal of KB2952664 from the hidden list and insertion back into the regular list was intended by Microsoft). I believe that Microsoft really really really wants customers to install KB2952664, and thus is deliberately moving it from the list of hidden updates to the regular list.

Perhaps Microsoft is doing this for the good/benefit of their customers; perhaps for the good/benefit of Microsoft. Perhaps KB2952664 only impacts the upgrade process; perhaps KB2952664 does something more? However, since Microsoft has not been transparent, it is hard to tell exactly what KB2952664 does and why Microsoft keeps unhiding KB2952664. Telling customers that the purpose of KB2952664 is to "ease the upgrade experience" does not justify repeated unhiding, and is just not enough information for me to decide to install it.

Let me just go back to my original question .... if KB2952664 is solely for easing the upgrade experience, and given the concern among many customers about the true purpose of this update, why can't Microsoft just incorporate whatever KB2952664 does into the upgrade itself (so that ONLY those customers who choose to upgrade get changes that KB2952664 brings)? By incorporating whatever KB2952664 does into the upgrade process, Microsoft can easily be assured that all users who choose to upgrade get the full benefit of the "ease in upgrade process" that KB2952664 allegedly brings.

So if easing the upgrade process is truly Microsoft's goal, then incorporating KB2952664 into the upgrade process would seem to be a win-win solution (users who never upgrade do not have to install this mysterious update, and Microsoft does not have to explain why they keep unhiding an update that some users do not want/need). Unless, of course, KB2952664 does something more than ease the upgrade process, and Microsoft wants/needs all users to get that "something more" (regardless of whether or not they ever do an upgrade). If that's the case, Microsoft needs to be more transparent.

I may be wrong but I am guessing that part of this might have to do with adding more and more hardware that has been tested and proven to be compatible with Windows 10.

The first time I got the "Get Windows 10" app, it said that there were some things that it would have problems with. (My graphics card being one of them.) Then I got an update and the warning about my graphics card went away along with the other two warnings.

I have a feeling they have been doing this all along.

Speaking for myself, here's what I need to know before I install KB2952664:

Are you speaking for yourself or putting the questions you think others should be asking?

Exactly what is wrong with the current upgrade experience that warrants a fix to ease the upgrade experience?

Upgrading only started 6 days ago so the results are only now starting to become apparent. The next month or so may provide an answer to your question. Microsoft clearly wants the experience to be smooth so, knowing the changes they have made, they simply want users to make changes to their systems which they think will make the experience better. What is wrong with that?

In what ways does KB2952664 improve the upgrade experience?

You will know more in a month’s time how the upgrade programme is going but I doubt you will ever get to know what difference KB2952664 made.

What impact/consequences would one experience by initiating an upgrade without previously installing KB2952664?

I have no idea but wouldn’t it be foolhardy to disregard recommendations?

Why can't Microsoft incorporate whatever KB2952664 does to improve the upgrade experience into the upgrade itself (so ONLY those who actually choose to upgrade their OS get the changes that KB2952664 brings, and those who choose not to upgrade are not subject to whatever KB2952664 does to improve the upgrade process).

Microsoft obviously considers their approach to be the most practical way to proceed. KB2952664 was installed on this computer on 2 August. It had not been hidden. I am not encountering any problems but then updates rarely cause me problems. I am not aware of hidden updates being re-offered. Of course if the software distribution folder is not properly updated you could get what appears to be what you describe. Do you think that it is Microsoft or the user who cause the majority of software distribution problems?

If Microsoft feels that everyone needs to install KB2952664 (their persistence in unhiding it and re-inserting it into ones Windows Update list would seem to imply that) then perhaps KB2952664 does something besides just improve the upgrade experience. Microsoft's lack of transparency with this update does not breed much trust.

I have some sympathy with the thrust of your point about transparency. However, I can think of countless far worse offenders than Microsoft! Today the world of spin is king.

According to the current description of KB2952664, this update is in its 13th revision. Why did Microsoft need to revise KB2952664 so many times? What was wrong with revision number 1, and more importantly, is there anything wrong with revision 13?

My suspicion is that the revision numbers are when the KB Article has been reviewed -Article ID: 2952664 - Last Review: 08/04/2015 16:12:00 - Revision: 13.0. It does not say that the content of the download has changed 13 times!

I have no plans of ever upgrading the OS (Windows 7) on my computer ... I am quite happy with Windows 7,

My preference is currently Windows 7 but that may change when I know more about Windows 10. I have plans to upgrade my laptop from Windows 7 to Windows 10 so that I have a platform from which help Windows 10 users in the same way I help those using Windows 7 and Windows 8. You may feel different in time and hardware does not go on for ever.

and the small improvements that Windows 10 has over Windows 7 is (to me) not worth the long list of disadvantages that Windows 10 has (compared to Windows 7).

I hope to be able to make that judgement when I have been using Windows 10 for 6-12 months. Everyone decried Windows 8 but it does have some good points. The types of error are certainly different to those created with Windows 7.

So I do not want/need KB2952664 to improve the upgrade process, and I will continue to hide it each time Microsoft inserts it into my Windows Update queue (at least Windows 7 gives one the option to manually install/hide updates ... unlike Windows 10 which forces all updates to automatically be applied ... but that's a subject for another thread).

Well you have slightly under 12 months in which to change your mind.

Gerry, you have good questions, and good points in your questions.  That is a synopsis of this topic.  If one looks at all the DLL names listed in the installer (https://support.microsoft.com/en-us/kb/2952664), it becomes obvious that this update is polling the hardware set of the PC.  My guess (since there has been no real answer) is that changes to the OS to help insure an upgrade from Windows 7 SP1 is as successful as possible.  The frustrating thing is that this particular KB is being repurposed and resent, the latest being over night (August 4th) in the US.  This has been happening for almost 2 years, as of now.  Since I had two out of 50+ PCs experience OS instability requiring a System Repair back to a previous restore point, I am guessing that some major Kernel changes are being made that could impact a small amount of PCs negatively.  Both had SYS files that were an issue found by SFC after the restore point (i.e. - USBUHCI.SYS on one, and a McAfee Virus Scan file "MFEHIDK.SYS", on another).

The only thing I can suggest is to stay on manual approve and select the updates you want to install.  For the vast majority of users, this update will have no negative effect.  From this thread, there are some who have experienced OS issues and dug up this update as being recent to the incurrence of the issues.  It is difficult to say how many of these are actually related and just coincidence.

Take this for what it is... one person's observation.

What more do you need to know?

Gerry,

Speaking for myself, here's what I need to know before I install KB2952664:

1. Exactly what is wrong with the current upgrade experience that warrants a fix to ease the upgrade experience?
2. In what ways does KB2952664 improve the upgrade experience?
3. What impact/consequences would one experience by initiating an upgrade without previously installing KB2952664?
4. Why can't Microsoft incorporate whatever KB2952664 does to improve the upgrade experience into the upgrade itself (so ONLY those who actually choose to upgrade their OS get the changes that KB2952664 brings, and those who choose not to upgrade are not subject to whatever KB2952664 does to improve the upgrade process).
5. If Microsoft feels that everyone needs to install KB2952664 (their persistence in unhiding it and re-inserting it into ones Windows Update list would seem to imply that) then perhaps KB2952664 does something besides just improve the upgrade experience. Microsoft's lack of transparency with this update does not breed much trust.
6. According to the current description of KB2952664, this update is in its 13th revision. Why did Microsoft need to revise KB2952664 so many times? What was wrong with revision number 1, and more importantly, is there anything wrong with revision 13?

I have no plans of ever upgrading the OS (Windows 7) on my computer ... I am quite happy with Windows 7, and the small improvements that Windows 10 has over Windows 7 is (to me) not worth the long list of disadvantages that Windows 10 has (compared to Windows 7). So I do not want/need KB2952664 to improve the upgrade process, and I will continue to hide it each time Microsoft inserts it into my Windows Update queue (at least Windows 7 gives one the option to manually install/hide updates ... unlike Windows 10 which forces all updates to automatically be applied ... but that's a subject for another thread).