Coincidence? WGA Failures Followed Windows Update 381
,----[ Quote ]
| One plausible scenario: Windows PCs running Windows Update version
| 7.0.6000.374 (or earlier) failed to activate/validate against a WGA service
| updated for version 7.0.6000.381. Microsoft had attributed the WGA failure to
| early release of a system update, which could fit this scenario. I haven't
| set up a new Vista PC recently. But if I rightly remember, activation is a
| process that occurs before updating.
`----
http://www.microsoft-watch.com/content/vista/coincidence_wga_failures_followed_windows_update_381.html
Related:
.----[ Quote ]
| If Microsoft ever wanted to get caught with their pants down, they
| succeeded. For most people, the above doesn't make a whole lot of
| sense past the "you might have a virus" part. VerifyMyPC requires a
| little extra knowledge about computer systems when dealing with the
| details. Google is your friend in these cases. Running searches for
| 'wups.dll' and 'wups2.dll' turns up something about Automatic
| Updates. In particular, those DLLs provide Automatic Update
| functionality for Windows.
|
| In other words, the Automatic Updates utility automatically updated
| itself. Now this might not seem like a big deal but I have
| automatic updates set to manual (both download and installation
| have to be approved by me) and not the usual 'automatic' setting
| found on most user PCs. In other words, Windows updated itself
| without my express permission. Such behavior is right in line with
| spyware-like activity.
`----
http://cubicspot.blogspot.com/2007/08/windows-update-updating-without.html
|
|
