Windows Update Agent 7.6.7600.320

If your system had been initiated in early 2012, Windows Update Agent v7.6.7600.256 would have been installed circa June 2012 (and you'd be running IE8 or IE9).

If your system had been initiated prior to July 2009, v7.4.7600.266 would have been installed (and you'd be running IE7 or IE8).

No hard & fast rule but MS generally releases a new Windows Update Agent version once every two (2) years.

Here's a "blast from the past" for your enjoyment:

• Windows Update Agent Update [sic] rolling out over the next couple of months

http://blogs.technet.com/b/mu/archive/2008/10/31/client-update.aspx

More recently:

• Upcoming Update for Microsoft Update Client

http://blogs.technet.com/b/mu/archive/2014/06/24/upcoming-update-for-windows-update-client.aspx

Because when you bought the machine it had the WU engine it needed and now in 2014 they updated it.

They don't update the WU back end plumbing that often, therefore why you prob have not seen it before.

BTW the WU engine update is designed to not need a reboot.  It's thought that Comodo had it's hooks into a location that the WU files were and thus because it wouldn't let the files be replaced it kicked a reboot.

I was looking to understand what an Update, that looks like no other Update in my Updates Review List under Control Panel, was. This thread tells me nothing.

I followed links in some responses here. No further explanation.

Logically I would assume my Windows 7 Home Premium, which has Windows Update turned on since day one, need an update to the Windows Update routine for some mysterious reason. Why this should happen on August 2, 2014 after the system was initiated on April 5, 2013 is another mystery.

I am a user who finds no difficulty at all, I had no problem. This Update just looked odd and stands out among the hundreds of other Updates I add to my Windows 7 system. It was a surprise to see as Windows DLs it's updates on the first Tuesday some months. I wondered if my PC did Updates. This Update just looked odd and stands out.

I hope you are 100% convinced.  The problem here is still the ecosystem of third party software and they are not interacting/getting the communication from Microsoft to then pass along the proper communication to you, the end user.

It may have been announced in June but it looks like it was released quite a bit later and then not without problems for many.