What exactly does KB2952664 do?

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.

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.

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).

Investigating on my Windows 7 Ultimate x64 computer reveals details of which I was not previously aware. KB2952664 was successfully installed on 9 June, 10 and 16 July, and 2 and 7 August 2015. My update history before 9 June 2015 no longer exists so I cannot check back to April 2014 when KB2952664 was originally released.

I investigated versions of Devinv.dll on my computer. There have been a number of updates to the file. This suggests to me that the update has been revised and re-issued a number of times. This supports what you have said. The Knowledge Base Article does not make this clear. I have submitted the comments in the paragraph below to Microsoft. I will not get anything other than the usual automated acknowledgement of my submission.

It seems that there have been a number of revisions to files contained in the original update. It would help users understanding if this was made clear in the Article .

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.

I do not know how the procedure for re-issued updates works. The problem is that where Microsoft needs to correct the content of an update because the original has caused many users problems, then quicker they do so is best for affected users and others who can still be affected. If an affected user has hidden the update the question is, is it better to have the re-issued update installed ASAP or allow those who have hidden the update to miss out because they are unaware that the problem update has been re-issued. What do you think?

If the revised update is not installed then it can create further problems in the future, which result in subsequent updates not being offered or installed correctly.

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.

Are you hiding it because you have encountered past problems with installing the update or because you do not think you need the update?

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.

True.

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 wasintendedby 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

I suspect, as you say, that Microsoft do want customers to install KB2952664.  Why shouldn’t they, if they believe it will improve their customers experience when using Windows?

Perhaps Microsoft is doing this for the good/benefit of their customers; perhaps for the good/benefit of Microsoft.

Is what they are doing detrimental to the interests of customers?

Perhaps KB2952664 only impacts the upgrade process; perhaps KB2952664 does something more?

What evidence do you have to suspect that perhaps KB2952664 does something more?

does not justify repeated unhiding,

This point is discussed above.

and is just not enough information for me to decide to install it.

I doubt you will get any more information. Some times you have to take some things on trust to get the best outcome.

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,

I suspect you over state your case. Most customers are only interested in a computer that works for them!

why can't Microsoft just incorporate whatever KB2952664 does into the upgrade itself

If they did what you suggest that would not ease the upgrade process.

(so that ONLY those customers who choose to upgrade get changes that KB2952664 brings)?

They are hoping that over time the vast majority of customers will upgrade. Time will tell us the answer.

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.

The users would actually see no benefit.

I keep a manual log of all changes made to my computer.  Here is an excerpt:

04/28/2014 15:38  KB2952664 Upd Win 7  (Windows Update assistance)  #1

05/13/2014 13:23  KB2952664 Upd Win 7  #2

06/10/2014 12:52  KB2952664 Upd Win 7  #3        failed 80070308

06/10/2014 13:29  KB2952664 Upd Win 7  #3a

07/08/2014 13:02  KB2952664 Upd Win 7  #4

08/12/2014 13:27  KB2952664 Upd Win 7  #5

09/09/2014 12:24  KB2952664 Upd Win 7  #6

10/14/2014 12:52  KB2952664 Upd Win 7  #7 FAILED?

11/11/2014 12:46  KB2952664 Upd Win 7  #8

12/09/2014 12:35  KB2952664 Upd Win 7  #9

02/10/2015 12:33  KB2952664 Upd Win 7  #10

03/24/2015 13:08  KB2952664 Upd Win 7  #11

04/09/2015 14:41  KB2952664 Upd Win 7  #12

06/02/2015 21:04  KB2952664 Upd Win 7  #13

07/08/2015 08:52  KB2952664 Upd Win 7  #14

07/08/2015 13:42  KB2952664 Upd Win 7  #15

07/11/2015 21:27  KB2952664 Upd Win 7  #16

07/27/2015 20:10  KB2952664 Upd WIn 7  #17

08/04/2015 15:06  KB2952664 Upd WIn 7  #18

--Barry Finkel

Barry

What are you trying to prove? You are simply demonstrating what I said in my previous message. Your list might have been shorter if you had set Windows Update to Check for updates but let me choose whether to download and install them.