I see even more idiots who think that the "postpone" option, even if it is unlimited, matters when the user could be asleep or in the hospital, as the OP was (see his other thread). Even more people don't seem to get why the OP is challenging the "PEBKAC" insult that is getting thrown around. His whole point is that it happens WITHOUT user instruction/intervention. Just because a user CAN intervene doesn't mean that they ALWAYS can and doesn't mean it's OK to make such behavior default without explicitly warning the user, especially when they have grown accustom to the old way and know that behaving differently would be asking for data loss (illogical).
Exactly. To install the updates, it must reboot your machine.
/thread
No, to FINISH installing them *the machine* must
sometimes be rebooted. *IT* doesn't have to be the one to do it, especially when the machine will often be rebooted in the course of normal use. It is completely different than a prompt saying that they are ready to install, which a user may ignore forever and therefore never get the important update.
The OP does have a point, though I think at this point ATOT is trolling the OP so hard, and he's gone batshit insane already, that nobody will agree with him even if they know 100% he is correct. A few people here get it. A computer should not restart without your approval when there is no way for an average user to know that the computer MAY restart.
Nobody here can deny that fact that NOWHERE in the Windows Update settings page does it say "The computer may automatically restart after updates are installed".
Numenorean, who appears to have gone just as batshit insane as the OP, hasn't acknowledged this fact, or the fact that gpedit does not exist in home editions of Windows.
Also, the fact that it once behaved differently conditioned users to continue expecting that behavior after they changed it. At one time, enabling automatic installation in XP would install them automatically and, if they required a restart, it would only PROMPT you, as it should, unless you specifically configured the PC to restart. When they changed this, there was NOTHING indicating the change. At the very least, if a program refuses to close because it contains unsaved information, it should fall back to a prompt unless you specifically over-ride that with policies to force them to close. This is because the VAST MAJORITY of users are home users with REPEATED assurances from MS that their PC is more stable and reliable than ever and that they should not be afraid of the OS being to blame for any seemingly-random reboot.