dean-dean said:
Hi Engel,
Windows Update Software 7.0.6000.381 is an update to Windows Update itself.
It is an update for both Windows XP and Windows Vista. Unless the update is
installed, Windows Update won't work, at least in terms of searching for
further updates. Normal use of Windows Update, in other words, is blocked
until this update is installed.
In Vista, it updates the following System32 files to version 7.0.6000.381:
wucltux.dll
wuauclt.exe
wuaueng.dll
wups2.dll
wuapi.dll
wudriver.dll
wups.dll
wuapp.exe
wuwebv.dll
In XP, it updates the following system32 files to version 7.0.6000.381:
wuweb.dll
wuaueng.dll
wuapi.dll
wucltui.dll
wuaucpl.cpl
cdm.dll
wuauclt.exe
wups2.dll
wups.dll
Hope this helps.
Well, it certainly appears that Microsoft is installing updates without
permission or consent. I have Windows Update set to "Notify" (XP Pro SP2,
IE6), and I run WU manually. The date-time stamp of the directory where
wups.dll v7.0.6000.381 is loaded
(C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wups.dll\7.0.6000.381\
for the curious) is 8/24/07. When I check "Installed Updates" on the WU site
I see that I ran WU on 8/15 (for August's Black Tuesday) and again on 8/29
(for KB933360). I checked all of the updates that occurred after the 7/30
date-time stamp of wups.dll and wups2.dll, and none of them list either file
in the "File Information" section for Windows XP.
Interestingly a search at microsoft.com for "wups.dll 7.0.6000.381" turns up
NOTHING while a search for "wups.dll 7.0.6000.374" turns up a couple of hits,
one of which is a KB article (932494 "When you use Automatic Updates to scan
for updates or to apply updates to applications that use Windows Installer,
you experience issues that involve the Svchost.exe process")
http://support.microsoft.com/default.aspx/kb/932494 ...
I checked my Event Viewer log for anything interesting on 8/24 and I found
an entry at 3:34 AM where the Windows Update Agent installed something:
All of the other "Windows Update Agent" Event-19 entries in the System Log
include a KB number:
so this one is particularly disturbing. I find it both curious and very
annoying that Microsoft still hasn't learned not to sneak around behind
people's backs.