MowGreen

Follow up: 12/7/2007
Installed V. 3.0.566 and the issue was resolved.

This issue is in regards to NOD32 Version 2.7.39. It's been observed on XP Pro SP2 and Media Center 2005.

In the course of checking the WindowsUpdate.log I noticed this:

2007-12-05 07:42:51:313 984 d28 Misc WARNING: Send failed with hr = 80072efd.
2007-12-05 07:42:51:333 984 d28 Misc WARNING: SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2007-12-05 07:42:51:333 984 d28 Misc WARNING: WinHttp: SendRequestUsingProxy failed for . error 0x80072efd
2007-12-05 07:42:51:333 984 d28 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
2007-12-05 07:42:51:333 984 d28 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efd
2007-12-05 07:42:51:333 984 d28 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efd
2007-12-05 07:42:53:586 984 d28 Misc WARNING: Send failed with hr = 80072efd.
2007-12-05 07:42:53:586 984 d28 Misc WARNING: SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2007-12-05 07:42:53:586 984 d28 Misc WARNING: WinHttp: SendRequestUsingProxy failed for . error 0x80072efd
2007-12-05 07:42:53:586 984 d28 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd

Did a few troubleshooting steps which included Stopping and Restarting the Automatic Updates service. The service failed to restart so I ran
sc query wuauserv
This was the error: 0x8007277A

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 12/6/2007
Time: 12:16:24 PM
User: N/A
Computer: C4DFF7AF7CA
Description:
The Automatic Updates service terminated with the following error:
The requested service provider could not be loaded or initialized.

Looked the error up on Google and found a thread which attributed it to
NOD32.
Disabled the AMON service and AU still failed
Disabled the IMON service and the AU service Started

Checked the NOD32 event log and apparently this issue started after the installation of one of these virus signature database updates:

Time Module Event User
12/4/2007 16:46:37 PM Kernel The virus signature database has been successfully updated to version 2703 (20071205).
Time Module Event User
12/4/2007 9:58:23 AM Kernel The virus signature database has been successfully updated to version 2701 (20071204).

Restarted the AMON service in NOD32, ran wuauclt /detectnow
no error in the WU.log
Restarted the IMON service in NOD32, ran wuauclt /detectnow again and the error reappeared in the WU.log
Stopped it and AU successfully connected.

I've pinged someone at Eset, the publisher of NOD32, to notify him of this issue. Will post a follow up when I hear something. [see top of page for the follow up]

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

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.

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.

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.

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

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)

The biggest culprit for .NET Framework updates failing to install properly is Antivirus software
In fact, AVs can also prevent or damage the original installation of said .NET Frameworks, thus, requiring one to uninstall them in order to install subsequent Security updates.
This requires one to completely and TOTALLY disable the installed AV when .NET Frameworks and Security updates are installed.
Not all AVs will cause such issues.
The AVs identified as causing such issues have been Norton, McAfee, or AntiVir.

Please consult the Help file of said AVs or visit the manufacturer's web site to learn how to completely and TOTALLY disable them.
For those who do not want to expose their system to the internet when the AV is disabled, then suggest you download first, disconnect the system from the network or internet, install the downloaded software/updates, reboot if necessary, REENABLE the installed AV, and then reconnect to said network/internet.

When you try to install an update for the .NET Framework 1.0, 1.1, or 2.0, you may receive Windows Update error code "0x643" or Windows Installer error code "1603"

Also, this is the Source as to .NET Framework and update issues:

Unified .NET Framework Troubleshooting Guide

What to do if other .NET Framework setup troubleshooting steps do not help

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

Error code 0x80245003 is caused by an incorrect redirector ID Number in the WINDOWS\SoftwareDistribution\WuRedir subfolder.

Error message when you try to install updates by using the Windows Update Web site: "0x80245003"

You cannot install updates by using the Microsoft Windows Update Web site, and you may receive an error message that resembles the following:

Error number:0x80245003. Windows Update has encountered an error and cannot display the requested page.

To work around this problem, follow these steps:
1. Click Start, click Run, type cmd in the Open box, and then click OK.
2. At the command prompt, type net stop wuauserv, and then press ENTER.
3. Type rmdir /s %windir%\softwaredistribution\wuredir, and then press ENTER.
4. Type net start wuauserv.
5. Use the Windows Update Web site again to install updates.

-----------------------------------------------------------------------------------------------------------------------------------------------
IF wuauclt.exe is NOT a running Process then the WuRedir can be moved to the Recycle Bin without having to stop the AU service.
There is no need to open a Command Prompt to accomplish the above.
Show hidden files, folders, and system files
Navigate to WuRedir using Windows Explorer
Delete WuRedir or it's contents as long as wuauclt.exe is not a running Process
It will be recreated/repopulated on the next visit to either Update sites

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

The error code 0x80070020 has been associated with Spybot Search and Destroy's TeaTimer being Enabled.
Suggest it be Disabled prior to accessing the Windows/Microsoft Update sites if the 0x80070020 error occurs trying to access/install updates from said sites.
Personally, I find that Spybot's added 'protections' cause more issues than they are worth.
YMMV

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

To assist in resolving issues with Windows Updates, the Windows Update website offers a link to the Windows Update Troubleshooter.
BUT, if one can not access Windows Update, those links are fairly useless, aren't they ?

I've copied all of the links for each fix posted on said Troubleshooter along with the issues listed.
They were tested with IE and Firefox, so they *should* also work in Opera.

Live Links To The Windows Update Troubleshooter
-----------------------------------------------------------------------------------------------------------------------------------------

When accessing the Update site, you receive the 0x80072EE2 or 0x80072EFD error. (Resolution 1)
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=32&ln=en

When accessing the Update site, you receive the 0x80072EE2 or 0x80072EFD error. (Resolution 2)
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=48&ln=en

When searching for available updates on the Update site, you see the 0x80072EE7 error
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=22&ln=en

The necessary services are disabled or unavailable. Error 0x80246008 (Resolution 1)
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=9&ln=en

The necessary services are disabled or unavailable. Error 0x80246008 (Resolution 2)
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=47&ln=en

The necessary service "Automatic Updates" (WUAUSERV) is not started or is unavailable. Error 0x80070422 (Resolution 1)
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=8&ln=en

The necessary service "Automatic Updates" (WUAUSERV) is not started or is unavailable. Error 0x80070422 (Resolution 2)
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=46&ln=en

When searching for available updates on the Update site, you see the 0x8024D00C error
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=55&ln=en

When searching for available updates on the Update site, you receive the 0x8024502d error.
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=26&ln=en

When trying to access the Update site, you see a blank page
http://update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=1&ln=en

When clicking a link on the View Installation History page, you see the home page within the main window
http://update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=25&ln=en

When clicking the Details or History link, nothing happens
http://update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=24&ln=en

When clicking Details, you see a blank dialog box
http://update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=2&ln=en

When searching for available updates on the Update site, you receive the 0x80240030 error. (Resolution 1) http://update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=31&ln=en

When searching for available updates on the Update site, you receive the 0x80240030 error. (Resolution 2)
http://update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=54&ln=en

When accessing the Update site, you receive the 0x8ddd0007 error.(Resolution 1)
http://update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=29&ln=en

When accessing the Update site, you receive the 0x8ddd0007 error. (Resolution 2)
http://update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=53&ln=en

When accessing the Update site, you receive the 0x8ddd0011 error (Resolution 1)
http://update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=37&ln=en

When accessing the Update site, you receive the 0x8ddd0011 error (Resolution 2)
http://update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=52&ln=en

When searching for available updates on the Update site, you see the 0x80072F8F error while looking for available updates (Resolution 1)
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=12&ln=en

When searching for available updates on the Update site, you see the 0x80072F8F error while looking for available updates (Resolution 2)
http://update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=50&ln=en

When searching for available updates on the Update site, you see the 0x80072F8F error while looking for available updates (Resolution 3)
http://update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=51&ln=en

The necessary services are disabled or unavailable. Error 0x80246008 (Resolution 1)
http://update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=9&ln=en

The necessary services are disabled or unavailable. Error 0x80246008 (Resolution 2)
http://update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=47&ln=en

When accessing the Update site, you receive the 0x8ddd0004 error
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=36&ln=en

When searching for available updates on the Update site, you see the 0x80070002 or 0x80070003 error
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=17&ln=en

When searching for available updates on the Update site, you receive the 0x800A0046 error.
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=20&ln=en

When attempting to download or install an update, you receive error 0x80070070.
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=33&ln=en

When installing .Net Framework 2.0 you may receive error 0x1011
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=49&ln=en

When accessing the Update site, you receive the 0x800A01AE error.
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=38&ln=en

When searching for available updates on the Update site, you receive the 0x800B0001 error.
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=34&ln=en

When trying to access the Update site, you see the 0x8ddd0003 error
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=6&ln=en

While the Windows Update Web site is loading, you receive Initialization Error 0x800A1391
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=45&ln=en

When searching for available updates on the Update site, you see the 0x800A01AD error
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=15&ln=en

When searching for available updates on the Update site, you see the 0x800A01AD error while looking for updates
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=13&ln=en

When accessing the Update site, you receive the 0x80240020 error.
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=39&ln=en

When searching for available updates on the Update site, you receive the 0x8024402C error.
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=30&ln=en

When searching for available updates on the Update site, you receive the 0x80248011 error.
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=21&ln=en

When searching for available updates on the Update site, you see the 0x8007043B error
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=19&ln=en

When searching for available updates on the Update site, you see the 0x80244001 error
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=14&ln=en

When searching for available updates on the Update site, you see the 0x80248013 error
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=11&ln=en

When trying to access the Update site, you see the Windows Update was disabled by your system administrator error
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=7&ln=en

When trying to access the Update site, you see an Administrators only error. The text reads: Your current security settings prohibit running ActiveX controls
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=5&ln=en

When trying to access the Update site, you see a Thank you page
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=4&ln=en

When tying to save Advanced settings on the Update site, you see the Need to enable Userdata for this feature error
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=3&ln=en

When accessing the Update site, you receive the 0x8007045A error.
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=28&ln=en

When clicking the Details or History link, nothing happens
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=24&ln=en

When clicking a link, you see the HTTP Error 500 - Internal Server Error, Error 0x8ddd0010
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=23&ln=en

When clicking a link on the View Installation History page, you see the home page within the main window
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=25&ln=en

Javascript error on Page, Line: 59, Char: 2
http://www.update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=18&ln=en
-----------------------------------------------------------------------------------------------------------------------------------------

Please report any errors in the above links.
Now that I finally got around to doing this, MS will most likely "update" the Troubleshooter

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

NOTE: There will be new software controls being installed for the V7 Windows/Microsoft Update sites soon. If you do not want to wait for them and are experiencing the SVCHOST issue, then download the latest Windows Update Agent for x86 [Win2K, XP, Microsoft Windows Server 2003, Vista] or Windows Update Agent for x64 [XP, Microsoft Windows Server 2003, Vista]
Save it, do NOT run it.
Then download and save KB927891 This is NOT FOR VISTA When the downloads are complete close the browser.
Now run WindowsUpdateAgent30-xXX.exe
Finally, install KB927891
PLEASE NOTE that there are different download links on the KB927891 page for x86 | x64 XP ,an x86 version for Win 2K, and x86 | x64 | ia64 for Microsoft Windows Server 2003
This is NOT FOR VISTA
Restart the system
From The WSUS Product Team Blog - Update on svchost/msi performance issue and 3.0 Client distribution plan

There are numerous threads in the Microsoft Windows Update Newsgroup that deal with the Infamous SVCHOST Issue
MS states that it's caused by the Windows Installer, specifically the msi.dll.
There are even [b]2[/b] MSKB articles that offer a newer version of msi.dll.
KB916089 states that one should not even bother with it. Instead, MS states KB927891 supercedes KB916089

Symptoms of the issue usually appear when a system first boots up, is awakened from Standby, Sleep, or Hibernation, and/or, accesses the Windows or Microsoft Update sites.
When systems with the Automatic Updates service running do any of the above , SVCHOST will start to consume most of the CPU cycles while spawning the wuauclt.exe [Windows Automatic Update Client] process.
SVCHOST may even take all of the CPU cycles, effectively locking the system up, temporarily, until the detection scan has finished.
Other contributing factors in this issue may also be disk fragmentation, data | log corruption, left over files,binaries, or metadata in the SoftwareDistribution folder, and/or interference | file corruption by security software.

Temporary steps that will help mitigate this issue :
1) First, show hidden files, folders, and system files
2) Using Windows Explorer, navigate to the WINDOWS\SoftwareDistribution\Download folder.
Delete the contents of this folder. Exit Windows Explorer.
Initiate a manual visit to the Windows|Microsoft Update site.
If that did not resolve the issue
3) Go to Start > Run > type in net stop wuauserv
Click OK or press Enter
Using Windows Explorer, navigate to the WINDOWS\SoftwareDistribution\DataStore folder
Delete DataStore.edb
NOTE: This will remove the update history that one sees on the Windows | Microsoft Update sites
4) Go to Start > Run > type in net start wuauserv
Click OK or press Enter
Initiate a visit to the Windows|Microsoft Update site.
5) If the above does not resolve the issue, then stop the Automatic Updates service from either the Services console or by running the command previously given.
Then either rename the SoftwareDistribution folder to SoftwareDistribution.old or delete it's contents, not the folder itself.
Now restart the Automatic Updates service.
The contents of SoftwareDistribution will be recreated the first time the system accesses the Windows | Microsoft Update sites or when the Windows Automatic Update Client is spawned.

The Hard Drive can be defragmented using either the native Windows utility or from a 3rd party tool.
Please consult the Help file from Start > Help and Support
Enter disk defragmentation in the Search field and then click the Green arrow.

Check the Help file of the installed antivirus software so that it can be configured to not scan the SoftwareDistribution folder during regularly scheduled system scans. At this time, there is no malware that uses that folder as an infecting vector.


UPDATE - Virus scanning recommendations for computers that are running Windows Server 2003, Windows 2000, or Windows XP

Do not scan the following files and folders. These files are not at risk of infection. If you scan these files, serious performance problems may occur because of file locking. Where a specific set of files is identified by name, exclude only those files instead of the whole folder. Sometimes, the whole folder must be excluded. Do not exclude any one of these based on the file name extension. For example, do not exclude all files that have a .dit extension. Microsoft has no control over other files that may use the same extensions as the following files.
• Microsoft Windows Update or Automatic Update related files
• The Windows Update or Automatic Update database file. This file is located in the following folder:
%windir%\SoftwareDistribution\Datastore
Exclude the Datastore.edb file.
• The transaction log files. These files are located in the following folder:
%windir%\SoftwareDistribution\Datastore\Logs
Exclude the following files:
• Edb*.log

Note The wildcard character indicates that there may be several files.
• Res1.log
• Res2.log
• Edb.chk
• Tmp.edb

Posted by MowGreen at 10:35 PM | Permalink | Comments (0) | TrackBacks (0)

There have been frequent reports of the reoffering of KB927978 (MS06-071) and KB925672 (MS06-061) in the MS Windows Update newsgroup. Users are reporting that even after the so-called successfull installation of KB925672 and the subsequent installation of KB927978, they are both reoffered. After installing them over and over, they are still reoffered.
KB927978 supercedes KB925672 in respect to

Note This security update only replaces the MS06-061 security update for Microsoft XML Core Services 4.0 and Microsoft XML Core Services 6.0 as both Microsoft XML Core Services 3.0 and Microsoft XML Core Services 5.0 are not affected.

Since KB927978 has a CRITICAL severity rating, it would behoove one to get it installed ASAP. I can not find any article that states that the vulnerability is being actively exploited, but I *think* it was being used when the Genuine Santa's web page was hacked.

OK, let's get this installed so that it's not reoffered.

Uninstall KB927978 from Add/Remove Programs.
It will be listed as MSXML 4.0 SP2 (KB927978)
Reboot

Now uninstall KB925672 from Add/Remove Programs.
It will be listed under Windows XP - Software Updates at the bottom
(The Show updates box at the top next to Currently installed programs and updates must be checked to see the installed Windows Updates)
Reboot

After rebooting, download MSXML 4.0 SP2 KB927978
Save it, do NOT run it.
Close the browser and ANY other open window
If you've done any printing, suggest rebooting prior to installation.

Install msxml4-KB927978-enu.exe now
Reboot

If either KB927978 or KB925672 are not listed in Add/Remove Programs (and Show updates is checked), then please show hidden files, folders, and system files
Using either Windows Explorer or My Computer, navigate to the WINDOWS directory (folder)
Check to see if either $NtUninstallKB927978$ and/or $NtUninstallKB925672$ are present.
Open the folders and then open the spuninst folder and run spuninst.exe for each of the installed updates, rebooting between each uninstall.
Then install msxml4-KB927978-enu.exe.
NOTE : As pointed out by Torgeir Bakken, MVP, one can also download MSXML 4.0 SP2 . Download the msxml.msi run it, and choose Remove from the 3 options presented, Modify/ Repair /Remove. If prompted to, reboot the system. If not, run msxml.msi once more to install it.
Then download the SECURITY update from here save it, close the browser, then run msxml4-KB927978-enu.exe to install it.

In addition, KB927978 generates randomly named folders on either the root drive, usually C:\ , or on the drive with the most free space, for each attempt at installing it. The folders contain the installation log file.
These folders can be safely deleted.

Posted by MowGreen at 12:17 PM | Permalink | Comments (36) | TrackBacks (0)

Issue:

On accessing WU - progress bar keeps going and then the 0x80248011 error appears

2006-11-08 17:54:42 2564 130 Misc = Process:
C:\WINDOWS\system32\wuauclt.exe
2006-11-08 17:54:42 2564 130 AUClnt FATAL: Error:
0xc8000408. wuauclt datastore: failed to spawn COM server
2006-11-08 17:54:42 1304 678 DtaStor FATAL: DS: Out of
proc datastore process exited with error 0xc8000408 before signalling
ready event.
2006-11-08 17:54:42 1304 678 Agent * WARNING: Exit code
= 0x80248011

Additonally, when attempting to run System Restore, the resultant error message is
Error 15: Cannot find the drive specified

Also System restore tells me that it is not able protect the computer and I should restart the machine.

XP Pro - right click C:\ >, choose Properties, Security
Add System with Full Control
XP Home Editon - boot to Safe Mode to access the Security tab by logging on as Administrator

For XP, the command can be shortened to regsvr
Windows 2000 requires the full command

3- regsvr32 wups.dll

4- regsvr32 wuaueng.dll

5- regsvr32 wucltui.dll

6- regsvr32 wuweb.dll

7- regsvr32 jscript.dll

8- regsvr32 atl.dll

9- regsvr32 softpub.dll

10- regsvr32 msxml3.dll

11- net start wuauserv

Reboot and try the Windows Update site again.

Posted by MowGreen at 7:31 AM | Permalink | Comments (0) | TrackBacks (0)

Automatic Updates options are greyed out by Ramesh Srinivasan,
Microsoft MVP - Windows Shell/User

When you open the Automatic Updates tab in My Computer Property sheet, or from Control Panel, all of the Automatic Updates configuration options may be grayed out. This happens due to any of the following reasons:

1. You're not logged on as Administrator (or equivalent)
2. Automatic Updates Policy is enabled
3. Automatic Updates (and Windows Update) access is blocked via Group Policy

Resolution

To make the Automatic Updates options configurable by the user (only for stand-alone systems), remove the restrictions 2 & 3 above.

* Click Start, Run and type REGEDIT.EXE
* Navigate to this location:

HKEY_LOCAL_MACHINE \ SOFTWARE \ Policies \ Microsoft \ Windows \ WindowsUpdate \ AU

* In the right-pane, delete the two values AUOptions and NoAutoUpdate
* Navigate to this location:

HKEY_CURRENT_USER \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ Policies \ WindowsUpdate

* In the right-pane, delete the value DisableWindowsUpdateAccess

Using the Group Policy Editor - for Windows XP Professional

* Click Start, Run and type gpedit.msc Click OK or press Enter
* Navigate to the following location:

=> Computer Configuration
==> Administrative Templates
===> Windows Components
====> Windows Update

* In the right-pane, double-click Configure Automatic Updates and set it to Not Configured
* Then, navigate to this location:

=> User Configuration
==> Administrative Templates
===> Windows Components
====> Windows Update

* In the right-pane, set Remove access to all Windows Update features to Not Configured

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

It's been reported in the Windows Update newsgroup that there are some systems experiencing issues with sound cards and installation failures associated with KB920872. Some Users report a continual prompt to reinstall it after a supposedly successful installation.
First, if there are continual prompts to reinstall it or there are sound issues, uninstall KB920872 from Add/Remove Programs in the Control Panel. ( If it is not listed there, then go to the end of this article for instructions on removing it )

This has been attributed to OEM manufacturers who have imaged the kmixer.sys, wdmaud.sys and splitter.sys drivers as unsigned.
Update.exe will treat these drivers as OEM drivers and not overwrite them.
This suggested workaround was posted by Eric Brodish, MS

1. Download the update from hereand save it to the C: \ drive (or whichever is the root drive)

2. Click on Start > Run

3. Type C:\WindowsXP-KB920872-x86-ENU.exe /o and click OK
(once again, C:\ being the root drive)

If the update had installed previously with loss of sound and it is not listed in Add/Remove Programs in the Control Panel, then show hidden files, folders, and system files.
Navigate to the WINDOWS directory (folder)
Locate the $NtUninstallKB920872$ folder and open it
Open the spuninst folder and run spuninst.exe
This will uninstall KB920872
Restart the system

Now install the update using the above method.

Posted by MowGreen at 7:00 PM | Permalink | Comments (0) | TrackBacks (0)

Workarounds for issues associated with Microsoft Security Bulletin MS05-051- Vulnerabilities in MSDTC and COM+ Could Allow Remote Code Execution (902400) and Microsoft Security Bulletin MS05-052 - Cumulative Security Update for Internet Explorer (896688) are available.


Systems that have changed the default Access Control List permissions on the %windir%\registration directory may experience various problems after you install the Microsoft Security Bulletin MS05-051 for COM+ and MS DTC

SYMPTOMS
On a computer that is running Microsoft Windows XP, Microsoft Windows 2000 Server, or Windows Server 2003, one or more problems may occur after you install the critical update that is discussed in Microsoft Security Bulletin MS05-051. These problems include the following:

• The Windows Installer service may not start.

• The Windows Firewall Service may not start.

• The Network Connections folder is empty.

• The Windows Update Web site may incorrectly recommend that you change the Userdata persistence setting in Microsoft Internet Explorer.

• Active Server Pages (ASP) pages that are running on Microsoft Internet Information Services (IIS) return an “HTTP 500 – Internal Server Error” error message.

• The Microsoft COM+ EventSystem service will not start.

• COM+ applications will not start.

• The computers node in the Microsoft Component Services Microsoft Management Console (MMC) tree will not expand.

• Authenticated users cannot log on, and a blank screen appears after the users apply the October Security Updates.

1.032: c:\06dcef1fbf2f33a9684e702fa40c34\update\update.exe (version 6.1.22.4)
1.042: Hotfix started with following command line: /log:D:\xx.log
1.132: Unexpected Error While Executing Line 1 ( Test.IE7InstallBlock.Section ) of PreRequisite
1.152: KB896688 Setup canceled.
2.744: Message displayed to the user: KB896688 Setup canceled.
2.744: User Input: OK
2.744: Update.exe extended error code = 0xf00d
2.744: Update.exe return code was masked to 0x643 for MSI custom action
compliance.

Posted by MowGreen at 5:27 AM | Permalink | Comments (1) | TrackBacks (0)