It's almost 2010, why do we still have to reboot for windows updates?

[Red Squirrel]

This burns me, why is it that Windows wants to reboot every single time an update is put in? There has to be a way around that which they could code, like have it restart the services involved, unload/reload the modified files etc... it's rediculous. I find windows as a server is a joke. Servers are meant for uptime, but if you keep up with patches you're rebooting it like twice a day. Nobody actually does this, but in reality if you really want to keep up with the patches you'd have to.

 

[Meghan54]

Exaggerate much?

 

[Nothinman]

Exaggerate much?

The frequency of required reboots may be exaggerated but the number of patches that require a reboot is still stupidly large.

 

[Zargon]

I had to reboot my old ubuntu server friggin weekly almost too, and it was a way biger PITA to do anything on that my 2008 server machines

 

[Nothinman]

I had to reboot my old ubuntu server friggin weekly almost too, and it was a way biger PITA to do anything on that my 2008 server machines

I find that hard to believe, the only thing that really requires a reboot in Linux is a kernel update and those don't come out weekly.

 

[Zargon]

I find that hard to believe, the only thing that really requires a reboot in Linux is a kernel update and those don't come out weekly.

well it only lasted a month :awe:

then I switched to sever08 cuz my boss approved the PO for a server license

but I did have to reboot a few times...

 

[JACKDRUID]

just turn off automatic update (still d/l the file), and update / reboot on your own schedule.

 

[JackMDS]

For the same reason that it is 2010, most people live are very good as compare to their family previous generations, yet they wasting most of their time complaining much more than their predecessors did.

 

[HannibalX]

I find that hard to believe, the only thing that really requires a reboot in Linux is a kernel update and those don't come out weekly.

Maybe as far as the OS is concerned but planet of applications want a warm boot frequently.

 

[Nothinman]

well it only lasted a month :awe:

then I switched to sever08 cuz my boss approved the PO for a server license

but I did have to reboot a few times...

No offense but reboots were probably not really required. For core things like libc it's recommended, but it's only really required for kernel updates. Everything else can be restarted without a reboot.

 

[GrumpyMan]

For the same reason that it is 2010, most people live are very good as compare to their family previous generations, yet they wasting most of their time complaining much more than their predecessors did.

Ahhhh!!!!! My computer doesn't boot at the speed of light, it takes 15 seconds. Ahhhhh....I want to kill somebody!!!!!

Just kidding of course.

 

[Nothinman]

Maybe as far as the OS is concerned but planet of applications want a warm boot frequently.

Which except for crap like Tomcat take ~2s to restart. Sure that might mean an outage for a few seconds, and you should still plan accordingly, but it's a lot less time than a full reboot.

 

[AndroidVageta]

just turn off automatic update (still d/l the file), and update / reboot on your own schedule.

This. Quit complaining and do something about it if you don't like it...you DO have control over what your PC does.

 

[Zargon]

No offense but reboots were probably not really required. For core things like libc it's recommended, but it's only really required for kernel updates. Everything else can be restarted without a reboot.

no offense taken!

I kindly do what the magic boxes ask, so that when they take over, they might leave me alive to atleast see my enemies killed first ()

 

[RebateMonger]

I don't know anybody who uses automatic updates on Windows Servers. At least not the ones they care about. I wait at least a week after "Patch Tuesday", monitoring IT consulting forums for any issues that come up.

 

[Red Squirrel]

We schedule on our own but that's not the point, the point is, if it did not require a reboot updates could actually be applied at any time without issues.

Then there's all the other programs that also require a reboot when updated. This is more seen on workstations. There's flash, java, AV software etc... if you actually clicked yes everytime something wants to update you'd be spending most of the day rebooting. It's rediculous, really.

I've never had to reboot a Linux server for any kind of update. Sometimes I'll reboot anyway to make sure it did not break anything that would only be aparent after a reboot.

 

[MrChad]

I've never had to reboot a Linux server for any kind of update. Sometimes I'll reboot anyway to make sure it did not break anything that would only be aparent after a reboot.

Those statements seem contradictory.

 

[MrChad]

This is supposedly better in Windows Vista / 2008 / 7. The addition of the Restart Manager in Windows Installer 4.0 is supposed to minimize these reboots.

 

[xSauronx]

I find that hard to believe, the only thing that really requires a reboot in Linux is a kernel update and those don't come out weekly.

ubuntu has them way, way too often. i had to reboot 9.04 and 8.10 way, way too often if i left the automatic updates running. easily twice a month i had to reboot because of some kernel change. it was annoying as all hell. i never bothered to see what the hell they were updating so much.

 

[nerp]

This is a non-issue for me. But that's probably because my job doesn't involve updating computers.

 

[theevilsharpie]

Ahhhh!!!!! My computer doesn't boot at the speed of light, it takes 15 seconds. Ahhhhh....I want to kill somebody!!!!!

Just kidding of course.

A desktop or a virtual machine may take only 15 seconds to restart. A server can take 5-10+ minutes.

 

[corkyg]

It is not required on all updates. Only those that make a change or changes in the Registry. The reason is obvious - the Registry is only replaced during boot. Therefore, to make the changes in effect, a reboot is required. Maybe someday we'll have a dynamic Registry.

 

[theevilsharpie]

It is not required on all updates. Only those that make a change or changes in the Registry. The reason is obvious - the Registry is only replaced during boot. Therefore, to make the changes in effect, a reboot is required. Maybe someday we'll have a dynamic Registry.

I'm struggling to determine if this is a joke post or not :hmm:

 

[Nothinman]

I'm struggling to determine if this is a joke post or not :hmm:

Same here...

 

[Fox5]

Most of the time when something requires you to reboot, it's not actually necessary. I think it's just a standard bit of text that gets thrown into most installers now.

Oh, and for Ubuntu, I think the only thing that needs a reboot at this point is kernel updates (which apparently there are ways to update without rebooting) and usually proprietary drivers.
Still, Ubuntu updates its kernel way too often, and I'm not sure why. IMO, considering almost all the other ubuntu software gets held back until the next release, the kernel should NOT be updated more frequently than the 6 month time schedule they set for new versions. At least not until they can make it happen more smoothly, almost every problem I've had with ubuntu (that wasn't my own fault) was due to a kernel update.