MowGreen

If Automatic Updates or either Windows or Microsoft Update sites can not update the Windows Update Agent successfully, suggest one download them from the following URLs:

x86-based versions of Windows [32 bit]
http://download.windowsupdate.com/WindowsUpdate/redist/standalone/7.0.6000.381/WindowsUpdateAgent30-x86.exe

x64-based versions of Windows [64 bit]
http://download.windowsupdate.com/WindowsUpdate/redist/standalone/7.0.6000.381/WindowsUpdateAgent30-x64.exe

Itanium-based versions of Windows
http://download.windowsupdate.com/WindowsUpdate/redist/standalone/7.0.6000.381/WindowsUpdateAgent30-ia64.exe

If during the installation a message appears that the Windows Update Agent is already installed, add /wuforce to the run line.

EX: WindowsUpdateAgent30-x86.exe is saved to the Desktop
Click Start > Run > click the Browse button. Click the Desktop icon in the left frame.
Locate WindowsUpdateAgent30-x86.exe and click once on it to highlight it.
Click OK.
Click once in the Open: line to highlight it
Push the End button on the keyboard
Push the Space Bar
Enter /wuforce
The command should now appear as:
"C:\Documents and Settings\UserAccount\Desktop\WindowsUpdateAgent30-x86.exe" /wuforce

Click OK and the WUA will install now.
Note:The drive letter may vary depending on how the Hard Drive/partitions are enumerated.
UserAccount is the name of the account being used at the time. It must have Admin privileges to install the WUA.

Posted by MowGreen at 2:44 PM | Permalink | Comments (0) | TrackBacks (0)

Updates are not installed successfully from Windows Update, from Microsoft Update, or by using Automatic Updates after you repair a Windows XP installation
The issue occurs because a file left on the system during the repair installation no longer has a corresponding entry in the registry.
To resolve this, open a Command Prompt, stop the Automatic Updates Service, register the file, and then restart the AU Service:

1. Stop the Automatic Updates service. To do this, follow these steps:
a. Click Start, click Run, type cmd, and then click OK.
b. At the command prompt, type the following command, and then press ENTER:
net stop wuauserv
2. Register the Wups2.dll file. To do this, follow these steps:
a. At the command prompt, type the following command, and then press ENTER:
regsvr32 %windir%\system32\wups2.dll
Note For a computer that is running Windows XP Professional x64 Edition, type the following command, and then press ENTER:
regsvr32 %windir%\syswow64\wups2.dll
b. Click OK on each verification message that you receive.
3. Start the Automatic Updates service. To do this, type the following command at the command prompt, and then press ENTER:
net start wuauserv
4. Exit the command prompt. To do this type exit, and then press ENTER.

I haven't run the commands yet but will do so to find out if just running
regsvr32 wups2.dll will accomplish the same task.

Posted by MowGreen at 10:40 AM | Permalink | Comments (0) | TrackBacks (0)

EDITED: 9/20
There's been a big to-do about the latest update to the Windows Update Agent/Client.

In late August the latest Version of the Windows Update Agent/Client was pushed out via Automatic Updates [Windows Update in Vista] and the Windows | Microsoft Update sites.

This has taken awhile to reach most of the Windows based systems around the world.
Unfortunately, MS never bothered to publish anything about this update until the shinola hit the fan.

The tin-foil crowd had a field day. The media delighted in bashing MS about installing updates when Automatic Updates had been disabled. Some journalists started braying that MS was updating your system without your knowledge and installing .exe's [exectuable files].
Well bunkies, all the update did was to install system files that are required to
be able to update the OS. Nothing more, nothing less.

For XP, there was ONE executable file that was updated, wuauclt.exe.
The rest were mostly .dll files. There were some .cat's installed [meow] and a .cpl file installed [Control Panel applet ]
In all, on my XP Pro box, there were 14 .cab files that contained the updated Windows Update Agent/Client.

An effort was made to explain just what was happening. IMHO, too late.
How Windows Update Keeps Itself Up-to-Date

To avoid creating such a false impression, the Windows Update client is configured to automatically check for updates anytime a system uses the WU service, independent of the selected settings for handling updates (for example, “check for updates but let me choose whether to download or install them”).

Before closing, I would like to address another misconception that I have seen publically reported. WU does not automatically update itself when Automatic Updates is turned off, this only happens when the customer is using WU to automatically install upgrades or to be notified of updates.

Then the Vista Team chimed in: An explanation of Windows Update automatic updating

This self-updating is done regardless of whether the user has enabled automatic checking, download and/or installation of updates. It does so in an effort to avoid WU misleading the user to think s/he is up-to-date simply because s/he was not receiving notification that updates are available. Put another way, WU cannot alert the user that there are security updates available if it is not in the necessary updated state that will allow it to recognize those updates (see "chicken and egg" dilemma).

However, we do recognize that we should have been clearer in our explanation of this process earlier in the game; the MU team's blog post is an effort to rectify that oversight.

Choosing to Disable automatic updating via the Automatic | Windows Update applet in the Control Panel will stop the updateing of the system files that are required in order for the system to be able to communicate with the Update server.

All of this could have easily been headed off by MS with some decent communication. They failed to do that and the subsequent explanations were late or incomplete.

The files required to update should now be at Version 7.0.6000.381
The previous Version was 7.0.6000.374

The files for XP are :

cdm.dll
wuapi.dll
wuauclt.exe
wuaucpl.cpl
wuaueng.dll
wucltui.dll
wups.dll
wups2.dll
wuweb.dll

Vista is not installed here. When I get a reliable list of the updated files, I'll post 'em.

EDITED: 9/18

The files for Vista are:

wuapi.dll
wuapp.exe
wuauclt.exe
wuaueng.dll
wucltux.dll
wudriver.dll
wups.dll
wups2.dll
wuwebv.dll

I did a little testing with a VPC installation of XP Pro [.vhd is the name of the virtual Hard Drive]
The OS had not been booted up since 4/07. The Windows Update Agent installed was an older version, V. 5.8.0.2469.
First it was booted to Safe Mode and the Automatic Updates options applet in the Control Panel
was set to " Turn off Automatic Updates ".
It was then rebooted to normal Windows mode. Since the Automatic Updates Service was not disabled, the OS attempted to connect to the Update servers. It failed to

2007-09-20 09:36:50 764 334 Misc = Process: C:\WINDOWS\Explorer.EXE
2007-09-20 09:36:50 764 334 Misc = Module: C:\WINDOWS\system32\wuaueng.dll
2007-09-20 09:36:50 764 334 Shutdwn Install at shutdown: no updates to install
2007-09-20 09:37:05 208 544 Misc =========== Logging initialized (build: 5.8.0.2469, tz: -0700) ===========
2007-09-20 09:37:05 208 544 Misc = Process: \??\C:\WINDOWS\system32\winlogon.exe
2007-09-20 09:37:05 208 544 Misc = Module: C:\WINDOWS\system32\wuaueng.dll
2007-09-20 09:37:05 208 544 Shutdwn FATAL: WUAutoUpdateAtShutdown failed, hr=8024000C
2007-09-20 09:40:42 964 198 Misc =========== Logging initialized (build: 5.8.0.2469, tz: -0700) ===========
2007-09-20 09:40:42 964 198 Misc = Process: C:\WINDOWS\System32\svchost.exe
2007-09-20 09:40:42 964 198 Misc = Module: C:\WINDOWS\system32\wuaueng.dll
2007-09-20 09:40:42 964 198 Service *************
2007-09-20 09:40:42 964 198 Service ** START ** Service: Service startup
2007-09-20 09:40:42 964 198 Service *********
2007-09-20 09:40:42 964 198 Agent * WU client version 5.8.0.2469
2007-09-20 09:40:42 964 198 Agent * SusClientId = '1cfadecf-3f60-4746-96f1-06209c953012'
2007-09-20 09:40:42 964 198 Agent * Base directory: C:\WINDOWS\SoftwareDistribution
2007-09-20 09:40:42 964 198 Agent * Access type: No proxy
2007-09-20 09:40:42 964 198 Agent * Network state: Disconnected
2007-09-20 09:41:39 964 198 Agent *********** Agent: Initializing Windows Update Agent ***********
2007-09-20 09:41:39 964 198 Agent *********** Agent: Initializing global settings cache ***********
2007-09-20 09:41:39 964 198 Agent * WSUS server:
2007-09-20 09:41:39 964 198 Agent * WSUS status server:
2007-09-20 09:41:39 964 198 Agent * Target group: (Unassigned Computers)
2007-09-20 09:41:39 964 198 Agent * Windows Update access disabled: No
2007-09-20 09:41:39 964 198 DnldMgr Download manager restoring 0 downloads
2007-09-20 09:41:39 964 198 AU ########### AU: Initializing Automatic Updates ###########
2007-09-20 09:41:39 964 198 AU # AU disabled through User preference
2007-09-20 09:41:39 964 198 AU # AU is disabled, not initializing any handlers
2007-09-20 09:44:40 964 47c Misc WARNING: Send failed with hr = 80072f8f. Meaning: ERROR_INTERNET_SECURE_FAILURE ErrorClockWrong One or more errors were found in the Secure Sockets Layer (SSL) certificate sent by the server.
2007-09-20 09:44:40 964 47c Misc WARNING: SendRequest failed with hr = 80072f8f. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2007-09-20 09:44:40 964 47c PT + Last proxy send request failed with hr = 0x80072F8F, HTTP status code = 0
2007-09-20 09:44:40 964 47c PT + Caller provided credentials = No
2007-09-20 09:44:40 964 47c PT + Impersonate flags = 0
2007-09-20 09:44:40 964 47c PT + Possible authorization schemes used =
2007-09-20 09:44:40 964 47c PT WARNING: GetCookie failure, error = 0x80072F8F, soap client error = 5, soap error code = 0, HTTP status code = 200
2007-09-20 09:44:40 964 47c Report Uploading 2 events using cached cookie, reporting URL = http://stats.update.microsoft.com/ReportingWebService/ReportingWebService.asmx
2007-09-20 09:44:42 964 47c Report Reporter successfully uploaded 2 events.
2007-09-20 09:51:28 1388 5c8 Misc =========== Logging initialized (build: 5.8.0.2469, tz: -0700) ===========
2007-09-20 09:51:28 1388 5c8 Misc = Process: C:\WINDOWS\Explorer.EXE
2007-09-20 09:51:28 1388 5c8 Misc = Module: C:\WINDOWS\system32\wuaueng.dll
2007-09-20 09:51:28 1388 5c8 Shutdwn Install at shutdown: no updates to install
2007-09-20 09:51:28 1388 5c8 Shutdwn FATAL: WUCheckForUpdatesAtShutdown failed, hr=8024A000 Meaning: Automatic Updates was unable to service incoming requests.
2007-09-20 09:51:38 964 594 AU AU Restart required....
2007-09-20 09:51:38 964 198 AU ########### AU: Initializing Automatic Updates ###########
2007-09-20 09:51:38 964 198 AU # AU disabled through User preference
2007-09-20 09:51:38 964 198 AU # AU is disabled, not initializing any handlers

I then updated the WUA to the last prior version, V. 7.0.6000.374
The system was then restarted.
The WUA was not updated, contrary to some published reports that it would be
Then I set the Automatic Updates option to " Notify me but don't automatically download or install them "
Right after closing the AU options, the system files were downloaded and installed without any interaction on my part. Here's a graphic of the System Event Viewer showing the update of the WUA had occurred
EventVwr.JPG

In summation, if one chooses to Disable any automatic updates from the
AU applet in the Control Panel, then there will be NO updating of the WUA.
If anyone says that behavior occurred on their systems, then they are liars. Period.

If one chooses to set AU to " Notify me ... " or " Download updates for me, but let me choose when to install them " then any subsequent update to the WUA will occur without any User interaction.

Posted by MowGreen at 10:21 AM | Permalink | Comments (0) | TrackBacks (0)

An update is available that improves the compatibility and reliability of Windows Vista
http://support.microsoft.com/kb/938194

Working with other MVPs, we have discovered that the update appears to install properly and is repeatedly reoffered after installing it.
The issue is that one of the Packages containing a Component update, in this case, WindowsCalendar, fails to install due to there being no WindowsCalendar folder present in Scheduled Tasks.
The WindowsCalendar folder had been deleted.

The result is the Package fails to install, thus the Components of this Package are rolled back.
The other Packages of the Update do install, thus, the Update is reoffered.

Workaround:

Open Task Scheduler, and in the Windows folder
add a WindowsCalendar folder.
No task has to be assigned, just create the WindowsCalendar folder.
Install KB938194 now.

Moral of the story: Don't delete any folders in the Windows folder of Scheduled Tasks.

NOTE: The above scenario dealt with one Component of Vista. There may be other Components that the Package can not update. To view a verbose log of Component Based Servicing [CBS], open the cbs.log located in

%windir%\logs\CBS\cbs.log

The below is where we found that the update was failing to install due to the WindowsCalendar being deleted from Scheduled Tasks:

2007-09-05 03:06:59, Info CSI 000000c1 Begin executing advanced installer phase 32 (0x00000020) index 80 (0x00000050)
(sequence 113) Old component: Microsoft-Windows-Calendar, Version =
6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral New component: Microsoft-Windows-Calendar, Version =
6.0.6000.16513, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral Install mode: install Installer ID: {4f9da785-7ffc-4a7d-9e7e-b1a67ad8b508} Installer name: [12]"Directory SD"
2007-09-05 03:06:59, Info CSI
00000143@2007/9/4:17:06:59.602 CMIADAPTER: Starting install...

2007-09-05 03:06:59, Info CSI
00000144@2007/9/4:17:06:59.617 CMIADAPTER: Invoking AI for install...

2007-09-05 03:06:59, Info CSI
00000145@2007/9/4:17:06:59.617 [194]"Applying ACL
D:P(A;CI;FA;;;BA)(A;OI;FRFWSDWDWO;;;BA)(A;CI;FA;;;SY)(A;OI;FRFWSDWDWO;;;SY)( A; CI;FW;;;AU)(A;OICIIO;FA;;;CO) to directory
"C:\Windows\system32\Tasks\Microsoft\Windows\WindowsCalendar\"

2007-09-05 03:06:59, Error CSI
00000146@2007/9/4:17:06:59.617 (F) [47]"SetNamedSecurityInfo (DACL and SACL) failed (2)" [gle=0x80004005]
2007-09-05 03:06:59, Error CSI
00000147@2007/9/4:17:06:59.617 (F) CMIADAPTER: Inner Error Message from AI HRESULT = HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) [ [44]"The system cannot find the file specified."] [gle=0x80004005]

2007-09-05 03:06:59, Error CSI
00000148@2007/9/4:17:06:59.617 (F) CMIADAPTER: AI failed. HRESULT = HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) Element: [94]"securityDescriptor xmlns="urn:schemas-microsoft-com:asm.v3" name="WindowsCalendarTasksACL" " [gle=0x80004005]
2007-09-05 03:06:59, Error CSI
00000149@2007/9/4:17:06:59.617 (F) CMIADAPTER: Exiting with HRESULT code = HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND). [gle=0x80004005]
2007-09-05 03:06:59, Info CSI
000000c2@2007/9/4:17:06:59.617 CSI Advanced installer perf trace: CSIPERF:AIDONE;{4f9da785-7ffc-4a7d-9e7e-b1a67ad8b508};Microsoft-Windows- Calendar, Version = 6.0.6000.16513, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;23541

2007-09-05 03:06:59, Error CSI 000000c3 (F) Failed execution of queue item Installer: Directory SD
({4f9da785-7ffc-4a7d-9e7e-b1a67ad8b508}) with HRESULT HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND). Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable (2)[gle=0x80004005]
2007-09-05 03:07:17, Info CSI 000000c4 End executing advanced installer (sequence 113) Completion status:

HRESULT_FROM_WIN32(ERROR_ADVANCED_INSTALLER_FAILED)

EDIT: 9/18 - Another successful workaround for this update was posted by NexusAnarchy in the MS WIndows Update newsgroup:

I resolved this issue by checking the cbs.log file and discovering that the install procedure was throwing up a PATH_NOT_FOUND error for the following folder:

C:\ProgramData\Microsoft\Network\Connections\Pbk\

I created an empty folder in that location, re-applied KB938194, rebooted,
and it now reports a succesful installation. I re-check the cbs.log file and
there are no new errors, and all exit conditions report OK.

That folder seems to be related to the Microsoft RAS service, for storage of
Public Keys. Nothing was created in the folder after my successful install -
so it would appear that the test to see if that path exists is falling over.

Posted by MowGreen at 1:20 PM | Permalink | Comments (0) | TrackBacks (0)

http://www.quotationspage.com/quote/30302.html

An eye for an eye makes the whole world blind.

Posted by MowGreen at 9:05 PM | Permalink | Comments (0) | TrackBacks (0)

http://quotes.liberty-tree.ca/quote/thomas_jefferson_quote_efec

"God forbid we should ever be twenty years without such a rebellion.
The people cannot be all, and always, well informed. The part which is
wrong will be discontented, in proportion to the importance of the facts
they misconceive. If they remain quiet under such misconceptions,
it is lethargy, the forerunner of death to the public liberty. ...
And what country can preserve its liberties, if it's rulers are not
warned from time to time, that this people preserve the spirit of
resistance? Let them take arms. The remedy is to set them right as
to the facts, pardon and pacify them. What signify a few lives lost
in a century or two? The tree of liberty must be refreshed from
time to time, with the blood of patriots and tyrants.
It is its natural manure."

Posted by MowGreen at 6:38 PM | Permalink | Comments (0) | TrackBacks (0)