RE: PLEASE stop nagging us to reboot!!!!

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Torgeir, thanks for providing the info that Jon (and thousands of other
people) are looking for - how to turn the nag screen off. We have many
machines that cannot auto-update because we want to review the updates first;
however, we review the udpates during working hours and then, if we apply
them, we cannot reboot because the machine is connected to by other users.
We have the machine scheduled for a reboot at night - but don't need the nags
all throughout the day.


"Jeff" wrote:

I just happened upon this post and found it rather silly at first. I thought
Mr Davis was just looking for some excuse to complain about Microsoft After
reading all the post, I thought Jon should get a life, until MisterSinister's
post.
Great job MisterSinister.



"MisterSinister" wrote:

Although I don't agree with your practices, I do agree with you that if the
user has already responded that he or she will reboot the OS later then there
is no reason to keep popping up a reminder.

Yes, the OS needs to reboot for some reason or another. Yes, your updates
are not fully applied until you have rebooted. Yes, you should reboot your OS
when it says it needs to be rebooted.

But that isn't the issue here. When a user makes the choice not to reboot
then don't bother the user by asking again. If you want the OS to be
rebooted, then don't give the user a choice and reboot the OS automatically.
Have a big warning appear before the install begins that says "Your system
will be rebooted immediately following the installation of this update. Close
any open applications now, or select 'Cancel' to stop the installation
process."

Or have the Windows Update icon appear in the systray as a grinning skull
with the number of hours that the user has gone without the required reboot
if you don't want to force the reboot upon them.

Don't sit on the fence with an annoying reminder. Either force the reboot
and give the user a chance to stop the install first, or give the user a
choice and let them live with the consequences if they don't reboot
immediately.

"Jon Davis" wrote:

If anyone at Microsoft is reading this, let me add my voice in and beg you,
on my knees, ...

PLEASE stop nagging us to reboot!!

Some of us are advanced users and we do actually happen to know when the
best time to reboot after an update is. But as a matter of habit I will
often get notice the "Update Available" system tray icon and click on it and
let it do its thing--always first observing what's affected first--but I may
need at least another hour or two of doing other administrative
tasks--actually, in my case, doing development work on things that I know
are not affected by the update I had installed. But every few minutes my
work is inturrupted with a dialog box, "HEY, YOU SHOULD RESTART, WOULD YOU
LIKE TO NOW OR LATER?" I click later and it inturrupts me again. On and on
the cycle goes, sometimes for days if I'm on a system that cannot rebooted
for a while, and I can't roll back. Guys, clicking on that "Later" button ..
that's not "later" that's only a moment.

If I kill the nagging process in the Task Manager, it just goes and replaces
itself!!

This is ludicrous!! Quit assuming that YOUR updates are more important than
OUR productivity. I'll restart whenever I %@^! well feel like it. Please
knock this off!!

Sincerely, wholeheartedly, and very, very annoyed,

Jon



.



Relevant Pages

  • Re: memory exception error - tut system.doc (0/1)
    ... install Windows XP SP3 onto your Windows XP system. ... Reboot so you start with a fresh machine. ... need to logon as an user with administrative priviledges. ... Download, install, run, update and perform a full scan with the following ...
    (microsoft.public.windowsxp.customize)
  • Re: memory exception error
    ... install Windows XP SP3 onto your Windows XP system. ... Reboot so you start with a fresh machine. ... need to logon as an user with administrative priviledges. ... Download, install, run, update and perform a full scan with the following ...
    (microsoft.public.windowsxp.customize)
  • Re: memory exception error
    ... I have not been able to update to SP3. ... Reboot so you start with a fresh machine. ... need to logon as an user with administrative priviledges. ... Download, install, run, update and perform a full scan with the following ...
    (microsoft.public.windowsxp.customize)
  • Re: memory exception error
    ... install Windows XP SP3 onto your Windows XP system. ... Reboot so you start with a fresh machine. ... need to logon as an user with administrative priviledges. ... Download, install, run, update and perform a full scan with the following ...
    (microsoft.public.windowsxp.customize)
  • Re: memory exception error
    ... install Windows XP SP3 onto your Windows XP system. ... Reboot so you start with a fresh machine. ... need to logon as an user with administrative priviledges. ... Download, install, run, update and perform a full scan with the following ...
    (microsoft.public.windowsxp.customize)