«

Well, it happened again. I installed a security update to Win XP
Pro SP1 and it is pestering me every 30 seconds to restart.
There is no "cancel" button, just "restart now" and "notify me
later".

The updater doesn't show up as a running app and I don't see
anything obvious in the list of running processes. What is the
name of this POS and how can I kill it? I'll be God Damned if
I'll let Bill Gates tell me when I have to restart my PC!

--
ATM, aka Jerry

All Things Mopar <> wrote:

|>Well, it happened again. I installed a security update to Win XP
|>Pro SP1 and it is pestering me every 30 seconds to restart.
|>There is no "cancel" button, just "restart now" and "notify me
|>later".
|>
|>The updater doesn't show up as a running app and I don't see
|>anything obvious in the list of running processes. What is the
|>name of this POS and how can I kill it? I'll be God Damned if
|>I'll let Bill Gates tell me when I have to restart my PC!

Try: Start\Run SHUTDOWN -A <enter>

This will abort a system shutdown. You can make a desktop shortcut for
it so it's handy.

FWIW this is a dos command and if you run it in a CMD window you will
see the results.

--
911 operator tells caller fire is actually fog.
Historic fort catches fog, burns to ground.
-Fark.com-

On Thu, 13 Oct 2005 20:23:56 -0500, All Things Mopar <>
wrote:

>Well, it happened again. I installed a security update to Win XP
>Pro SP1 and it is pestering me every 30 seconds to restart.
>There is no "cancel" button, just "restart now" and "notify me
>later".
>
>The updater doesn't show up as a running app and I don't see
>anything obvious in the list of running processes. What is the
>name of this POS and how can I kill it? I'll be God Damned if
>I'll let Bill Gates tell me when I have to restart my PC!

Only thing I have ever found is to push the damn thing as far off the
screen as you can and ignore it until you are ready to let it off.

Today Trax spoke these views with conviction for everyone's
edification:

> Try: Start\Run SHUTDOWN -A <enter>
>
> This will abort a system shutdown. You can make a desktop
> shortcut for it so it's handy.
>
> FWIW this is a dos command and if you run it in a CMD
> window you will see the results.

Thanks. But, when I try it, I see a DOS window open and close
but the updater is sitting in my systray.

--
ATM, aka Jerry

Today EricP spoke these views with conviction for everyone's
edification:

> Only thing I have ever found is to push the damn thing as
> far off the screen as you can and ignore it until you are
> ready to let it off.

Hadn't thought of that. It ****es me off that even the red "X"
to kill the dialog box is grayed out. I very well understand why
some updates require a restart. Fine. But, I'll do it when I'm
good and ready, not when Bill says I have to!

The only thing that is worse is some misguided app installer or
updater that doesn't even ask, it just does a restart and all
you can do is watch it happen. Yeah, Windoze warns you of your
unsaved work, but there are /lots/ of works-in-progress where
you lose the change history as soon as you save, hence you're
scrued.

--
ATM, aka Jerry

All Things Mopar <> wrote:

|>Today Trax spoke these views with conviction for everyone's
|>edification:
|>
|>> Try: Start\Run SHUTDOWN -A <enter>
|>>
|>> This will abort a system shutdown. You can make a desktop
|>> shortcut for it so it's handy.
|>>
|>> FWIW this is a dos command and if you run it in a CMD
|>> window you will see the results.

|>Thanks. But, when I try it, I see a DOS window open and close
|>but the updater is sitting in my systray.

My bad, I thought that was what it was made for

I don't do the auto update thing, having it disabled, so have never
experienced the shutdown window after an update.

If you Start\Run CMD <enter>
then type in Shutdown /? it will give switches, and if you run the -a
switch it will tell you things you might be able to use in the
command.


--
911 operator tells caller fire is actually fog.
Historic fort catches fog, burns to ground.
-Fark.com-

In article <Xns96EED9AFBE95BReplyID@216.196.97.136>, All Things Mopar
<> wrote:

> Well, it happened again. I installed a security update to Win XP
> Pro SP1 and it is pestering me every 30 seconds to restart.
> There is no "cancel" button, just "restart now" and "notify me
> later".
>
> The updater doesn't show up as a running app and I don't see
> anything obvious in the list of running processes. What is the
> name of this POS and how can I kill it? I'll be God Damned if
> I'll let Bill Gates tell me when I have to restart my PC!

You should resist all of Microsoft's and Gates' ideas about almost
everything in the industry, but, um...
Well, in this case it sounds like you updated running system parts.
the system won't use them until they are loaded as system parts.
You have to restart in order to do this. It's basic.

It's like this: you just downloaded a new engine component. It keeps
something from major damage when you are running, so you want this
part.
You can't replace it while the engine is running.
You stop, replace the part, and then start again, and you have the
protection of that new part.
It's the same with an OS component.

"All Things Mopar" <> wrote in message
news:Xns96EEDFDD5AA58ReplyID@216.196.97.136...
> Today EricP spoke these views with conviction for everyone's
> edification:
>
>> Only thing I have ever found is to push the damn thing as
>> far off the screen as you can and ignore it until you are
>> ready to let it off.
>
> Hadn't thought of that. It ****es me off that even the red "X"
> to kill the dialog box is grayed out. I very well understand why
> some updates require a restart. Fine. But, I'll do it when I'm
> good and ready, not when Bill says I have to!
>
Just don't tell Bill that you are doing it, restart the computer but do
not let him know about it. Be sneaky and you will win your personal
battle against Bill Gates.

Alt

Today Trax spoke these views with conviction for everyone's
edification:

> All Things Mopar <> wrote:
>
>|>Today Trax spoke these views with conviction for
>|>everyone's edification:
>|>
>|>> Try: Start\Run SHUTDOWN -A <enter>
>|>>
>|>> This will abort a system shutdown. You can make a
>|>> desktop shortcut for it so it's handy.
>|>>
>|>> FWIW this is a dos command and if you run it in a CMD
>|>> window you will see the results.
>
>|>Thanks. But, when I try it, I see a DOS window open and
>|>close but the updater is sitting in my systray.
>
> My bad, I thought that was what it was made for

No, not your bad, see below.

> I don't do the auto update thing, having it disabled, so
> have never experienced the shutdown window after an update.
>
> If you Start\Run CMD <enter>
> then type in Shutdown /? it will give switches, and if you
> run the -a switch it will tell you things you might be able
> to use in the command.

I opened a CMD window and did as you suggest. shutdown -a is
definitely there but when I type it, I get a message "unable
to abort since no shutdown is in process". I suppose I would
have to try to do this /after/ I've let the Windoze updater at
least initiate the shutdown. I'll try that.

Thanks for the hints. I didn't even know about the shutdown
function.

--
ATM, aka Jerry

Today Mitch spoke these views with conviction for everyone's
edification:

> Well, in this case it sounds like you updated running
> system parts. the system won't use them until they are
> loaded as system parts. You have to restart in order to do
> this. It's basic.

I understand this part just fine. It's just that if I'm in the
middle of something important to me, I don't want to stop
working on it while Windoze takes it's damn sweet time
shutting down, then starting up again, then loading my
account.

For example, if I'm in the middle of a long editing session of
an image in PSP 9, I can and do use the History Pallette to do
selective Undos of things that don't turn out well. Sure, I
can save intermediate versions of a work-in-progress, but when
I do, I lose the change history.

> It's like this: you just downloaded a new engine component.
> It keeps something from major damage when you are running,
> so you want this part.
> You can't replace it while the engine is running.
> You stop, replace the part, and then start again, and you
> have the protection of that new part.
> It's the same with an OS component.

I understand this part just fine, also. It'd be OK if my car
is in the shop and the mechanic needs to restart it, but think
of this analogy if you're driving along, and your car asks to
download a patch to your engine computer. You say "yes" and it
attempts to flash the controller chip. So far, so good. The
car is still running and you are driving OK. Would /you/
immediately shut off the engine and restart it while you're
driving in heavy traffic on an interstate, or wait until you
got to your destination?

A reminder say, once an hour, would be more than enough. But
every 30-60 seconds? Not!

--
ATM, aka Jerry