SWUPDATE - a task that causes delays and problems

[Guest]

I'd be grateful for your knowledge about a task called "SWUPDATE".

Every hour, SWUPDATE hogs 100% of the CPU, delays the machine and
occasionally precipitates a crash.

I don't know what process or sub-process it is, so am wary of simply
terminating the task. If it's periodic, it's parent is likely launch it
again, in any event.

How can I kill this apparently pointless, and occasionally data-losing, task?

 

[Guest]

Try running msconfig from a command prompt or the START>RUN box. Look under
the startup tab and see if you can find it there. Then uncheck it as a
startup option. If you do not see it by name then you may have to uncheck
several and do a check-uncheck test until you locate the right startup
program.

As for me knowing what SWUPDATE is I do not other than it is a program that
looks for a software update to some other program you have installed on your
PC.

If you cannot find the program in msconfig, then you may need to uninstall
some programs to find which one SWUPDATE is working for.

Wes

 

[John John]

Fine and dandy but if this is a standard W2k installation there is no
msconfig, the user would have had to get it from another OS and stuck it
in the System32 folder. Secondly there is no need to uninstall "some
programs" to find the offender. What and where would you start
uninstalling?

John.

 

[John John]

Look in "Scheduled Tasks" and see if anything is in there. It could be
any software update feature running but my first guess is that it would
be anti virus software. Look in there and see if there is an option to
turn off the auto update feature. If you still can't find it you can
try one of these utilities to help finding the culprit:

CodeStuff Starter: http://members.lycos.co.uk/codestuff/

Sysinternals Process Explorer:
http://www.sysinternals.com/ntw2k/freeware/procexp.shtml

Sysinternals Autoruns:
http://www.sysinternals.com/ntw2k/freeware/autoruns.shtml

John

 

[Guest]

John John,

If you have some value to add to help the user answer their question then
state what you think might be of service to them.

Your reply to my answer was of no use or help to the person asking the
question.

And for that matter, my response to you is of little help also.

Please keep on topic.

Wes

 

[Bob I]

Hello Wes(Additude),

John John REPLIED to YOU, with this message. He ALSO replied to the OP
seperately WITH CORRECT INFORMATION. Please read for awhile and learn to
follow a thread. Thank you for taking taking the time to learn about
Windows 2000.

 

[John John]

Thanks Bob.

John

Hello Wes(Additude),

John John REPLIED to YOU, with this message. He ALSO replied to the OP
seperately WITH CORRECT INFORMATION. Please read for awhile and learn to
follow a thread. Thank you for taking taking the time to learn about
Windows 2000.

 

[Bob I]

Welcome, we all try to help.

Thanks Bob.

John

 

[John John]

I'm sorry if I offended you, that was not my intention. You stated that
"...(my) reply to (your) answer was of no use or help to the person
asking the question." I beg to disagree. It is of use in that it will
correct 2 errors in your original post. First as I stated there is no
msconfig in W2K and if the OP doesn't have it all that your suggestion
will do is have him going around in circles perhaps wondering what is
wrong with his W2K. Secondly I don't think that the advice to
"uninstall some programs" is appropriate at all. What are these "some
programs" that you would have him uninstall without even knowing what
the offending program or underlying cause might be? That suggestion
would only cause needless work for the OP and will or may do absolutely
nothing to fix the problem.

One of the strengths of peer groups is that answers provided by posters
are subject to peer review and corrections when improper or incorrect
advice is given. I have been corrected in the past and am sure I will
be corrected again in the future, we all make mistakes. If you think
your answer to the problem was correct and appropriate then stake your
claim. Should you disprove my answer to your post then I will
gracefully withdraw my comments and apologize for my error. If you
can't make a case to support your answer to the OP's problem then just
accept it and move on, admit that your answer was inappropriate...live
and learn.

John