Me AutoUpdate Dont ??

My update log begins 20 October 2003 because 1-2 weeks
prior, (shortly) after a doing an update (wxms or xmls?),
my system restore was inop, break points were in-
accessable, help center gave script error messages and
wouldnt load and autoupdate would hang at 33%(back then).
Since then, after several visits I've received zero
critical updates, just like the download.ject patch I
just tried to download...No Updates Available !
The urrent version in registry is correct.
Thanks in advance

My update log begins 20 October 2003 because 1-2 weeks
prior, (shortly) after a doing an update (wxms or xmls?),
my system restore was inop, break points were in-
accessable, help center gave script error messages and
wouldnt load and autoupdate would hang at 33%(back then).
Since then, after several visits I've received zero
critical updates, just like the download.ject patch I
just tried to download...No Updates Available !
The current version in registry is correct.
No background AV/scanner(s), firewall, adblockers etc.
are used.
Thanks in advance

Can you access this page ? :
http://v4.windowsupdate.microsoft.com/troubleshoot/

If not, then it may be that the MSXML files or the parser are
damaged . This may have resulted from attempting to install the
update you mentioned without temporarily disabling the antivirus
program prior to doing the updating.
Here are the suggested resolutions from the Troubleshooter page for
MSXML issues :

" Suggestion 1:

Make sure the MSXML files are registered correctly by following the
steps below.

NOTE: You may not have the files listed in Steps 2 and 3 installed
on your PC but please perform all 3 steps. If you don't have one of
the files, when you try to register it you will see a popup window
that has this text:

LoadLibrary("filename.dll") failed - The specified file name could
not be found.

Just disregard the error and continue to the next step.

Follow these steps:

1. Click on Start, Run and type "REGSVR32
C:\WINDOWS\SYSTEM\MSXML.DLL" (w/o the quotes). You should see a
popup message that this process succeeded.
2. Click on Start, Run and type "REGSVR32
C:\WINDOWS\SYSTEM\MSXML2.DLL" (w/o the quotes). You should see a
popup message that this process succeeded.
3. Click on Start, Run and type "REGSVR32
C:\WINDOWS\SYSTEM\MSXML3.DLL" (w/o the quotes). You should see a
popup message that this process succeeded.
Now try the Windows Update site and see if you get the same error.

Suggestion 2:

This error can be the result of a file mismatch or corruption of the
MSXML.DLL files. Try upgrading your XML parser to the most recent
version, which is currently MSXML Parser 3.0 Service Pack 2 Release.
You can download the latest parser from this site:

http://msdn.microsoft.com/library/de...xmlgeneral.asp
--------------------------------------------------------------------------------
The latest version of MSXML Parser 3.0 is Service Pack 4.

MowGreen [MVP]
===============
*-343-* FDNY
Never Forgotten
===============


MrSmartButt2U wrote:

My update log begins 20 October 2003 because 1-2 weeks
prior, (shortly) after a doing an update (wxms or xmls?),
my system restore was inop, break points were in-
accessable, help center gave script error messages and
wouldnt load and autoupdate would hang at 33%(back then).
Since then, after several visits I've received zero
critical updates, just like the download.ject patch I
just tried to download...No Updates Available !
The urrent version in registry is correct.
Thanks in advance

Thanks Mow, it d/l kb840315, I suspect there
should have been more criticals.

-----Original Message-----
Can you access this page ? :
http://v4.windowsupdate.microsoft.com/troubleshoot/

If not, then it may be that the MSXML files or the parser
are
damaged . This may have resulted from attempting to
install the
update you mentioned without temporarily disabling the
antivirus
program prior to doing the updating.
Here are the suggested resolutions from the
Troubleshooter page for
MSXML issues :

" Suggestion 1:

Make sure the MSXML files are registered correctly by
following the
steps below.

NOTE: You may not have the files listed in Steps 2 and 3
installed
on your PC but please perform all 3 steps. If you don't
have one of
the files, when you try to register it you will see a
popup window
that has this text:

LoadLibrary("filename.dll") failed - The specified file
name could
not be found.

Just disregard the error and continue to the next step.

Follow these steps:

1. Click on Start, Run and type "REGSVR32
C:\WINDOWS\SYSTEM\MSXML.DLL" (w/o the quotes). You
should see a
popup message that this process succeeded.
2. Click on Start, Run and type "REGSVR32
C:\WINDOWS\SYSTEM\MSXML2.DLL" (w/o the quotes). You
should see a
popup message that this process succeeded.
3. Click on Start, Run and type "REGSVR32
C:\WINDOWS\SYSTEM\MSXML3.DLL" (w/o the quotes). You
should see a
popup message that this process succeeded.
Now try the Windows Update site and see if you get the
same error.

Suggestion 2:

This error can be the result of a file mismatch or
corruption of the
MSXML.DLL files. Try upgrading your XML parser to the
most recent
version, which is currently MSXML Parser 3.0 Service Pack
2 Release.
You can download the latest parser from this site:

http://msdn.microsoft.com/library/default.asp?
url=/downloads/list/xmlgeneral.asp
----------------------------------------------------------
----------------------
The latest version of MSXML Parser 3.0 is Service Pack 4.

MowGreen [MVP]
===============
*-343-* FDNY
Never Forgotten
===============


MrSmartButt2U wrote:

My update log begins 20 October 2003 because 1-2 weeks
prior, (shortly) after a doing an update (wxms or
xmls?),
my system restore was inop, break points were in-
accessable, help center gave script error messages and
wouldnt load and autoupdate would hang at 33%(back
then).
Since then, after several visits I've received zero
critical updates, just like the download.ject patch I
just tried to download...No Updates Available !
The urrent version in registry is correct.
Thanks in advance

.

Sorry I couldnt resist the subject but nothing funny
about the useless endless loops I experience on the
MS site.
My situation is I cant find a way to verify what was
actually downloaded from the update site that day.
SFP gave a window claiming it installed some catalog
number. ABout IE shows SP1,q824145,q832894 and q831167
(still), the updatelog reveals nothing useful and the
xml log is even more cryptic to me.
1 critical download last year and 1 last week does not
coincide with tech tv's mention of several monthly.
Thanks

-----Original Message-----
Thanks Mow, it d/l kb840315, I suspect there
should have been more criticals.

-----Original Message-----
Can you access this page ? :
http://v4.windowsupdate.microsoft.com/troubleshoot/

If not, then it may be that the MSXML files or the
parser
are
damaged . This may have resulted from attempting to
install the
update you mentioned without temporarily disabling the
antivirus
program prior to doing the updating.
Here are the suggested resolutions from the
Troubleshooter page for
MSXML issues :

" Suggestion 1:

Make sure the MSXML files are registered correctly by
following the
steps below.

NOTE: You may not have the files listed in Steps 2 and
3
installed
on your PC but please perform all 3 steps. If you don't
have one of
the files, when you try to register it you will see a
popup window
that has this text:

LoadLibrary("filename.dll") failed - The specified file
name could
not be found.

Just disregard the error and continue to the next step.

Follow these steps:

1. Click on Start, Run and type "REGSVR32
C:\WINDOWS\SYSTEM\MSXML.DLL" (w/o the quotes). You
should see a
popup message that this process succeeded.
2. Click on Start, Run and type "REGSVR32
C:\WINDOWS\SYSTEM\MSXML2.DLL" (w/o the quotes). You
should see a
popup message that this process succeeded.
3. Click on Start, Run and type "REGSVR32
C:\WINDOWS\SYSTEM\MSXML3.DLL" (w/o the quotes). You
should see a
popup message that this process succeeded.
Now try the Windows Update site and see if you get the
same error.

Suggestion 2:

This error can be the result of a file mismatch or
corruption of the
MSXML.DLL files. Try upgrading your XML parser to the
most recent
version, which is currently MSXML Parser 3.0 Service
Pack
2 Release.
You can download the latest parser from this site:

http://msdn.microsoft.com/library/default.asp?
url=/downloads/list/xmlgeneral.asp
---------------------------------------------------------
-
----------------------
The latest version of MSXML Parser 3.0 is Service Pack 4.

MowGreen [MVP]
===============
*-343-* FDNY
Never Forgotten
===============


MrSmartButt2U wrote:

My update log begins 20 October 2003 because 1-2 weeks
prior, (shortly) after a doing an update (wxms or
xmls?),
my system restore was inop, break points were in-
accessable, help center gave script error messages and
wouldnt load and autoupdate would hang at 33%(back
then).
Since then, after several visits I've received zero
critical updates, just like the download.ject patch I
just tried to download...No Updates Available !
The urrent version in registry is correct.
Thanks in advance

.

.

download and run Belarc Advisor - it'll give you a full list of the patches
that are applied, and whether they're correctly applied
post back with the details, and we'll see where you are.

--
Noel Paton (MS-MVP 2002-2004, Win9x)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm
http://tinyurl.com/6oztj

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

wrote in message
...
Sorry I couldnt resist the subject but nothing funny
about the useless endless loops I experience on the
MS site.
My situation is I cant find a way to verify what was
actually downloaded from the update site that day.
SFP gave a window claiming it installed some catalog
number. ABout IE shows SP1,q824145,q832894 and q831167
(still), the updatelog reveals nothing useful and the
xml log is even more cryptic to me.
1 critical download last year and 1 last week does not
coincide with tech tv's mention of several monthly.
Thanks

-----Original Message-----
Thanks Mow, it d/l kb840315, I suspect there
should have been more criticals.

-----Original Message-----
Can you access this page ? :
http://v4.windowsupdate.microsoft.com/troubleshoot/

If not, then it may be that the MSXML files or the
parser
are
damaged . This may have resulted from attempting to
install the
update you mentioned without temporarily disabling the
antivirus
program prior to doing the updating.
Here are the suggested resolutions from the
Troubleshooter page for
MSXML issues :

" Suggestion 1:

Make sure the MSXML files are registered correctly by
following the
steps below.

NOTE: You may not have the files listed in Steps 2 and
3
installed
on your PC but please perform all 3 steps. If you don't
have one of
the files, when you try to register it you will see a
popup window
that has this text:

LoadLibrary("filename.dll") failed - The specified file
name could
not be found.

Just disregard the error and continue to the next step.

Follow these steps:

1. Click on Start, Run and type "REGSVR32
C:\WINDOWS\SYSTEM\MSXML.DLL" (w/o the quotes). You
should see a
popup message that this process succeeded.
2. Click on Start, Run and type "REGSVR32
C:\WINDOWS\SYSTEM\MSXML2.DLL" (w/o the quotes). You
should see a
popup message that this process succeeded.
3. Click on Start, Run and type "REGSVR32
C:\WINDOWS\SYSTEM\MSXML3.DLL" (w/o the quotes). You
should see a
popup message that this process succeeded.
Now try the Windows Update site and see if you get the
same error.

Suggestion 2:

This error can be the result of a file mismatch or
corruption of the
MSXML.DLL files. Try upgrading your XML parser to the
most recent
version, which is currently MSXML Parser 3.0 Service
Pack
2 Release.
You can download the latest parser from this site:

http://msdn.microsoft.com/library/default.asp?
url=/downloads/list/xmlgeneral.asp
---------------------------------------------------------
-
----------------------
The latest version of MSXML Parser 3.0 is Service Pack 4.

MowGreen [MVP]
===============
*-343-* FDNY
Never Forgotten
===============


MrSmartButt2U wrote:

My update log begins 20 October 2003 because 1-2 weeks
prior, (shortly) after a doing an update (wxms or
xmls?),
my system restore was inop, break points were in-
accessable, help center gave script error messages and
wouldnt load and autoupdate would hang at 33%(back
then).
Since then, after several visits I've received zero
critical updates, just like the download.ject patch I
just tried to download...No Updates Available !
The urrent version in registry is correct.
Thanks in advance

.

.

Mow, I failed to see your mention of AV software before,
NO AV software was running, I run those utils exclusively
one at a time.
I visited Win Update on 2 Aug (no updates) and just now,
KB867801 was available. Two critical updates released
since 12 or 13 July, is that accurate ??
The true reason I'm contacting you again is, yesterday I
was using my machine to show a friend how to use system
restore when I noticed that my oldest break point is
3 July ?? I have NOT disabled system restore and I have
1300+ Meg allocated for storage ??
Thanks

(Some text deleted for the sake of brevity)
-----Original Message-----
Thanks Mow, it d/l kb840315, I suspect there
should have been more criticals.

-----Original Message-----
Can you access this page ? :
http://v4.windowsupdate.microsoft.com/troubleshoot/

If not, then it may be that the MSXML files or the
parser are damaged . This may have resulted from
attempting to install the update you mentioned without
temporarily disabling the antivirus program prior to doing
the updating. ****************

MrSmartButt2U wrote:

My update log begins 20 October 2003 because 1-2 weeks
prior, (shortly) after a doing an update (wxms or
xmls?),
my system restore was inop, break points were in-
accessable, help center gave script error messages and
wouldnt load and autoupdate would hang at 33%(back
then).
Since then, after several visits I've received zero
critical updates, just like the download.ject patch I
just tried to download...No Updates Available !
The urrent version in registry is correct.
Thanks in advance