Good Day to you all,

It seems that the Windows Update thing and the Blaster affected different
machines differently. Note these facts.

I work for a company that has no onsite IT or ISSO, so I work as both
occasionally. My day was full last Tuesday with clearing the
w32.blaster.worm from our network.

We have multiple computers that all go through the same server, via 2
different routers.

On most of the systems, even some that came up with the worm, we can run
Windows updates normally. On a few of the systems, however, Windows Update
does not function.

Interesting point of fact, if you follow the step 4 proceedure for the
0x80001391 error fix and add the three windowsupdate addresses into the
exceptions under the advanced settings of the LAN connections, then the
system comes up with the cannot connect local internet warning. If you take
those addresses out of the exceptions list, you can load the Windows Update
initial site, the site tells you there is a problem with using Windows
update and try the troubleshooter.

Fascinating, huh.

If anyone has an idea, let me know. Just note, I do not believe the
problems some people are facing are MS fault. MS, Symantec, McAfee and
others are working fast and furious to get all this cleaned up. After all,
It has only been, what.........a week?????

Ever watched a contractor build a house in Western Washington? Now that can
be SLLLOOWWWWW.

Checking the trusted sites list is step 2 or 3 of the fix mentioned. Yes, I
did check those. And they are good. Understand, I did this on 17 computers
in the last week. Only 3 have update problems. Of those 3, only two had
the virus.
But thanks for your input. I should have mentioned that in the original
post.



"Maurice N" <maurice@mvps.org> wrote in message
news:eoA4yrbZDHA.2632@TK2MSFTNGP12.phx.gbl...

Oh, correction to the error code....
0x800A1391
Okay......No one said techs could type. Or there would be no code
errors.........yeah

"greyhwk" <greyhwk@hotmail.com> wrote in message
news:#wd8LXbZDHA.2284@TK2MSFTNGP10.phx.gbl...

Here's a copy of a recent reply of mine, on this type error, but mind you,
I'm quoting Lucy Eby at MS.
You have already tried Trusted Sites section. Maybe see if you can "tweak"
proxy exception settings.
PLUS be sure your systems are not using Tweakmaster program. Also recheck
the Hosts file on each problem pc.

Quote from Lucy at MS : "Typically the 0x800A1391 error is cause by 3rd
party software interference.
A program is preventing the download of the ActiveX controls. Are you
behind a Firewall? Proxy? " </enquote>

Do you have any browser-popup stopper - type program ? There are a
bunch that cause hiccups.
So could add-on download helpers.

If you have AdShield, NetPopup, or any popup ad remover, you need to
insure that program is OFF before doing Windows Update.
It can also be an over-eager antivirus program (if you have one) that is
interfering.

If none of these are the source, then, if you have a 3rd-party firewall
program, try turning that off & then test Windows Update results.

Quoting some items for this error -- from MS Windows Troubleshooter:
It appears to be because the customer can not download the ActiveX
component.

#1. Try turning off firewall.
- - -
Suggestion 2
============
We may be able to resolve this issue by adding
http://windowsupdate.microsoft.com

http://v4.windowsupdate.microsoft.com

https://v4.windowsupdate.microsoft.com (Note: The https is correct)

http://download.windowsupdate.com

to the trusted sites list in the Internet Options.
To access the Exceptions settings.
1. Open Internet Explorer
2. Click Tools / Internet Options
3. Click the Security Tab
4. Click on the Trusted Sites Icon
5. Click on the Sites button
6. Unselect the check box "Require server verification (httpsfor all
sites in this zone"
7. Add all 4 sites listed above
=====
Suggestion 3
============
This issue may be resolved by adding the Windows Update sites to the
exceptions list in the Internet Options Proxy Settings.
To access the Exceptions settings.
1. Open Internet Explorer
2. Click Tools / Internet Options
3. Click the Connections Tab / LAN Settings
4. Click the Advanced Button and add
windowsupdate.microsoft.com

v4.windowsupdate.microsoft.com

download.windowsupdate.com

to the exceptions list.
=========

--
Maurice N
MVP Windows - Shell / User
- -
"greyhwk" wrote