If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Reboot nag after update and how to drive a stake through it's heart
In the middle of a lengthy job I received a notice that an update had been
installed and that I needed to reboot (with the option of doing it later). I opted for later and for the rest of the day every few minutes another reminder would pop up. I just deferred it each time and left for home with the original job still in progress. This morning I discovered the computer was waiting for me to log in (which I assumed was the result of a power glitch). After bringing up the machine a popup message appeared asserting that a reboot had been required which implies that if you ignore the nag and the original option reboot message is not answered XP will do it anyway. Needless to say this was very annoying since it killed my overnight operation and I have to start over again. I wonder if they ever talk to end users about their unilateral decisions like this. I certainly have never seen any surveys requesting such feed back. What gives? And how to I prevent this autonomy in the future? Regards, John |
Ads |
#2
|
|||
|
|||
Reboot nag after update and how to drive a stake through it's heart
Well next time don't update during a mission or time critical operation.
That is what you should have deferred not the install at an inapprpriate time. Also take a look at you windows update settings and make sure you don't have it installing and updating and rebooting at 3am. Rich "JTM" wrote in message ... In the middle of a lengthy job I received a notice that an update had been installed and that I needed to reboot (with the option of doing it later). I opted for later and for the rest of the day every few minutes another reminder would pop up. I just deferred it each time and left for home with the original job still in progress. This morning I discovered the computer was waiting for me to log in (which I assumed was the result of a power glitch). After bringing up the machine a popup message appeared asserting that a reboot had been required which implies that if you ignore the nag and the original option reboot message is not answered XP will do it anyway. Needless to say this was very annoying since it killed my overnight operation and I have to start over again. I wonder if they ever talk to end users about their unilateral decisions like this. I certainly have never seen any surveys requesting such feed back. What gives? And how to I prevent this autonomy in the future? Regards, John |
#3
|
|||
|
|||
Reboot nag after update and how to drive a stake through it's heart
"Rich" wrote in message news Well next time don't update during a mission or time critical operation. That is what you should have deferred not the install at an inapprpriate time. Also take a look at you windows update settings and make sure you don't have it installing and updating and rebooting at 3am. Rich Changed it to Sunday at 3 am. I am assuming that was the reason for the reboot rather than an unattended popup reminder going off on its own. I still would like to disable this repetitive reminder--one click on the "I'll do it later" button should be enough to stop the nag. Regards, John |
#4
|
|||
|
|||
Reboot nag after update and how to drive a stake through it's heart
"JTM" wrote in :
In the middle of a lengthy job I received a notice that an update had been installed and that I needed to reboot (with the option of doing it later). I opted for later and for the rest of the day every few minutes another reminder would pop up. I just deferred it each time and left for home with the original job still in progress. This morning I discovered the computer was waiting for me to log in (which I assumed was the result of a power glitch). After bringing up the machine a popup message appeared asserting that a reboot had been required which implies that if you ignore the nag and the original option reboot message is not answered XP will do it anyway. Needless to say this was very annoying since it killed my overnight operation and I have to start over again. I wonder if they ever talk to end users about their unilateral decisions like this. I certainly have never seen any surveys requesting such feed back. See my post from yesterday... "Windows update reboots without asking". The cure is to set updates NOT to install automatically. Even though you chose "later" it will do it automatically at 3 AM. You can change the time of that or you can just choose "Download updates but let me choose when to install them". I don't like it either... it would have been a big problem for me if I hadn't happened to be up when it happened. Needless to say, I changed my prefernces. -- --- A Freudian slip is when you say one thing but mean your mother. --- |
Thread Tools | |
Display Modes | |
|
|