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]

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.

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.

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.

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.

]]> http://mowgreen.castlecops.com/archives/2007/09/vista_kb938194_appears_to_inst.html http://mowgreen.castlecops.com/archives/2007/09/vista_kb938194_appears_to_inst.html Windows Update Issues, Fixes, and Workarounds Thu, 06 Sep 2007 13:20:39 -0800 http://www.quotationspage.com/quote/30302.html

An eye for an eye makes the whole world blind.

]]> http://mowgreen.castlecops.com/archives/2007/09/a_quote_by_mahatma_gandhi.html http://mowgreen.castlecops.com/archives/2007/09/a_quote_by_mahatma_gandhi.html Commentary Wed, 05 Sep 2007 21:05:21 -0800 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."

]]> http://mowgreen.castlecops.com/archives/2007/09/a_quote_by_thomas_jefferson.html http://mowgreen.castlecops.com/archives/2007/09/a_quote_by_thomas_jefferson.html Commentary Mon, 03 Sep 2007 18:38:05 -0800 Sun JRE Font Parsing Vulnerability

HIGHLY CRITICAL
Description:
A vulnerability has been reported in Sun JRE, which can be exploited by malicious people to compromise a user's system.

The vulnerability is caused due to an unspecified error in the parsing of fonts contained in Java applets. This can be exploited by malicious, untrusted applets to read and write local files, or to execute local applications.

The vulnerability is reported in the following products:
* JDK and JRE 5.0 Update 9 and earlier
* SDK and JRE 1.4.2_14 and earlier

Solution:
Update to the latest versions or apply patches:

JDK and JRE 5.0 Update 10 or later
http://java.sun.com/j2se/1.5.0/download.jsp

SDK and JRE 1.4.2_15 or later
http://java.sun.com/j2se/1.4.2/download.html

Why am I not surprised that there's another issue with applets and Sun's java runtime ?
And remember, bunkies, the java autoupdater does not remove older, vulnerable versions !
One must uninstall it/them from Add/Remove Programs in the Control Panel on Windows OS'.

]]> http://mowgreen.castlecops.com/archives/2007/08/sun_jre_font_parsing_vulnerabi.html http://mowgreen.castlecops.com/archives/2007/08/sun_jre_font_parsing_vulnerabi.html Security Alerts Thu, 23 Aug 2007 14:12:32 -0800 EDIT: August 21, 2007 The Microsoft connection clarified

1. Are we blaming Microsoft for what happened?
We don’t blame anyone but ourselves...

2. What was different about this set of Microsoft update patches?
In short – there was nothing different about this set of Microsoft patches...

3. How come previous Microsoft update patches didn’t cause disruption?
That’s because the update patches were not the cause of the disruption...

Thank you for being honest about the disruption and not passing the blame to "someone else", Skype.

=====================================================================

What happened on August 16

On Thursday, 16th August 2007, the Skype peer-to-peer network became unstable and suffered a critical disruption. The disruption was triggered by a massive restart of our users’ computers across the globe within a very short timeframe as they re-booted after receiving a routine set of patches through Windows Update.

The high number of restarts affected Skype’s network resources. This caused a flood of log-in requests, which, combined with the lack of peer-to-peer network resources, prompted a chain reaction that had a critical impact.

Normally Skype’s peer-to-peer network has an inbuilt ability to self-heal, however, this event revealed a previously unseen software bug within the network resource allocation algorithm which prevented the self-healing function from working quickly. Regrettably, as a result of this disruption, Skype was unavailable to the majority of its users for approximately two days.

The issue has now been identified explicitly within Skype. We can confirm categorically that no malicious activities were attributed or that our users’ security was not, at any point, at risk.

I don't have an LOL that's big enough for that explanation. If their supposition is true, than why didn't previous updates from Microsoft cause this issue before ?
There's no way in heck that all of the systems connected to Skype downloaded, installed updates, and then rebooted at the same time. NO WAY !!!!

I'm not that familiar with Skype's software but, ANY software one installs that insists on running when Windows starts up via it's Duhfault settings, is a major PITA.
There's also security implications to consider. There have been known exploits and vulnerabilities in IM/Chat Clients that are resolved when said issuer of such Clients either patch them or upgrade them. Do you really want a vulnerable Client to be connecting to the internet even though it may have a critical vulnerability for which a newly issued exploit is aimed at ?
If I want to run your software, I very well know how to start it, thank you.

Frankly, I do not recall the latest version of Skype that I installed having that as a Duhfault setting. If it did, it was disabled as soon as it was installed, trust me.

Even if Skype's lame excuse were possible ... then I say GOOD.
Serves you right for having your software run on boot because you were the ones who chose that invasive behavior, not Microsoft.

]]> http://mowgreen.castlecops.com/archives/2007/08/skype_says_your_os_ate_my_p2p.html http://mowgreen.castlecops.com/archives/2007/08/skype_says_your_os_ate_my_p2p.html Commentary Mon, 20 Aug 2007 11:29:15 -0800 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

]]> http://mowgreen.castlecops.com/archives/2007/08/net_framework_updates_fail.html http://mowgreen.castlecops.com/archives/2007/08/net_framework_updates_fail.html Windows Update Issues, Fixes, and Workarounds Tue, 14 Aug 2007 14:29:41 -0800 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.

NOTE: Posted July 10, 2007 Since today is 'Patch Tuesday', I've rechecked if the WuRedir folder can be deleted while wuauclt.exe is listed as a running Process. On this system, Win XP Pro SP2, the WuRedir could be deleted without having to End Process wuauclt.exe. If you find that's not the case for your system, then read on.

-----------------------------------------------------------------------------------------------------------------------------------------------
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

]]> http://mowgreen.castlecops.com/archives/2007/06/error_code_0x80245003.html http://mowgreen.castlecops.com/archives/2007/06/error_code_0x80245003.html Windows Update Issues, Fixes, and Workarounds Mon, 25 Jun 2007 10:20:39 -0800 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

]]> http://mowgreen.castlecops.com/archives/2007/06/error_code_0x80070020.html http://mowgreen.castlecops.com/archives/2007/06/error_code_0x80070020.html Windows Update Issues, Fixes, and Workarounds Mon, 25 Jun 2007 10:13:17 -0800 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

]]> http://mowgreen.castlecops.com/archives/2007/06/live_links_to_the_windows_upda.html http://mowgreen.castlecops.com/archives/2007/06/live_links_to_the_windows_upda.html Windows Update Issues, Fixes, and Workarounds Mon, 18 Jun 2007 14:58:13 -0800 From Microsoft Technet Upcoming Chats

Q&A with the Security MVP Experts

We invite you to attend an Q&A with the Microsoft Security MVPs. In this chat the MVP experts will answer your questions regarding online safety issues such as phishing, spyware, rootkits as well as server related topics. If you have questions on how to protect your PC, please bring them to this informative chat

When: Thursday June 21st

Time: 4pm PST and 7pm EST

Where: TechNet Chat Room

No password required

Clicking on the TechNet Chat Room link will lead one to a sign in page that looks like this

Microsoft.com Chat
To view this specialized content, you are required to sign in with a Windows Live™ ID.
Don't have a Windows Live™ ID?
If you have a Hotmail address, MSN e-mail address, or Microsoft Passport, it's already a Windows Live ID.

You can sign in here with your existing e-mail address and password.
Sign up now to use one Windows Live ID to sign in to Windows Live, Microsoft.com, MSN, and Microsoft Passport sites.

If you do not have a " Windows Live™ ID then you can obtain one by following the above instructions.
If you do not desire a " Windows Live™ ID ", then you can not attend the chat session.

Microsoft established this requirement, MVPs did NOT !

]]> http://mowgreen.castlecops.com/archives/2007/06/qa_with_the_security_mvp_exper.html http://mowgreen.castlecops.com/archives/2007/06/qa_with_the_security_mvp_exper.html Security Alerts Mon, 18 Jun 2007 11:41:24 -0800