Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Direwolf20 said:What windows update usually does, if set to automatic, is popup a window saying "Updates complete, would you like to restart now?" and it has a 5 minute timer. If theres no user action in 5 minutes, it reboots.
In the time it took you to reply to this thread, you could have rebooted. Ask yourself which is more of a "hassle"....rebooting or getting the virus that this fix prevents?J32P2006 said:I don't want to see the dang window every five minutes and I don't to reboot just because an update was installed.
Exactly. It's just a reboot. I can never understand why so many people bother to complain about rebooting.Direwolf20 said:You should reboot, its the best way to ensure the patch was completely applied.
Rumor has it that vista will have less reboots, but time will tell on that. For now, its a best practice, as for making it stop bothering you, the best way I know of is to just reboot.
djnes said:In the time it took you to reply to this thread, you could have rebooted. Ask yourself which is more of a "hassle"....rebooting or getting the virus that this fix prevents?
Exactly. It's just a reboot. I can never understand why so many people bother to complain about rebooting.
Robstar said:Hm, our dual xeon w/ 2G ram exchange server takes 20-30 minutes to reboot. Required rebooting = baaaaaaaaaaaad.
Rob
djnes said:In the time it took you to reply to this thread, you could have rebooted. Ask yourself which is more of a "hassle"....rebooting or getting the virus that this fix prevents?
Exactly. It's just a reboot. I can never understand why so many people bother to complain about rebooting.
30 minutes?! WTF?Robstar said:Hm, our dual xeon w/ 2G ram exchange server takes 20-30 minutes to reboot. Required rebooting = baaaaaaaaaaaad.
Rob
Required booting is definitely something that takes a lot of consideration on enterprise production servers...but as mentioned, I believe this only affects client machines.Robstar said:Hm, our dual xeon w/ 2G ram exchange server takes 20-30 minutes to reboot. Required rebooting = baaaaaaaaaaaad.
Rob
No production server should ever be set to automatically install anything.djnes said:Required booting is definitely something that takes a lot of consideration on enterprise production servers...but as mentioned, I believe this only affects client machines.
kumquat said:No production server should ever be set to automatically install anything.
kumquat said:No production server should ever be set to automatically install anything.
J32P2006 said:
Comment #1
I use Nod32 so I don't really worry that much about viruses. And who's to say that when microsoft releases a patch that it will actually do what it's supposed to do.
But your soo wrong J32P2006, Microsoft patches are the bestest thing in da world.
Comment #2
And Damn, every time I see you post in a thread your complaining about other people.
I swear that you must be pist off all the time or just love telling people how bad what they do is.
And I don't mind rebooting, but when I want to.
One more thing, your complaining, I wasn't just stating my opinion.
I never said it should be. That would be very very bad. Patches should be loaded in a test environment, and worked over. If they pass at that point, then they should be loaded on the production servers.kumquat said:No production server should ever be set to automatically install anything.
djnes said:1) When Microsoft releases a patch to fix a hole this bad, you apply it right away. You're correct in saying it might not be the end all be all to this problem, but it's a hell of a lot better than leaving the system unpatched, right?
2) I do a lot of correcting, etc because these forums have changed dramatically over the past 2 years or so. Anytime I question was asked, it had a great response. When a debate was started, it was always finalized with good clear answers. Now, there seems to be a huge number of posts that don't make any logical sense, or are just flat out wrong. Do you ever read on other forums what is said about these forums?
Speaking of complaining, you were the one who initially complained about something as simple as having to reboot, correct? This is a perfect example of why I get so frustrated. You complain about having to reboot for a security patch. If you didn't apply it, you'd create a thread on how Micro$haft Winblows sucks because you got a virus. Either way, you'd have a complaint that could have been easily remedied. I still stand by my comments that in the time it took to post in this thread, you could have applied the patch and been done with it. I also recommend following kumquat's advice about Automatic Update settings. Then you will know about the patch, but can install it and reboot when you get a minute.
If you didn't apply it, you'd create a thread on how Micro$haft Winblows sucks because you got a virus.
Then you will know about the patch, but can install it and reboot when you get a minute.
illdklli said:i just got back to my computer not long ago. apparently, windows decided to update itself and then restart without asking permission. lovely. seems as though a bunch of my AIM buddies aren't signed on as usual.
hmmm...
S1nF1xx said:This is the one problem with automatic updates IMO. It should never automatically reboot the computer. Instead of doing that, it should automatically apply the updates when you shutdown or reboot the computer. Then I'd actually be able to run automatic updates on my client's computers.