Why aren't Windows updates better?

Soldato
Joined
18 Oct 2002
Posts
6,372
Location
Bedfordshire
It's not often I have to deal with Windows updates these days, they are built into VM templates which are kept fairly up to date.

Recently though I've had the 'joy' of installing a Windows 2008 R2 server from a pre SP1 ISO.

No problem I thought, I'll kick off the patch installs before I leave and then it will be finished when I come in tomorrow.

I came back to it the next morning only to find I could no longer RDP to the box. Upon viewing the console it was stuck on the windows loading screen on update 31/110

Whatever, hit the reset switch and it booted into windows with 100 updates to go. 2 hours later I logon to check, reboot and then it has 1 update available. Installed. Reboot. Check. 1 update available.

That update happens to be SP1. SP1??? Why didn't it do that first?! 2 hours later it's still installing SP1 and I'm reasonably certain there will be many more updates to install once this has finished.

Why are they so bad? With ESXi and linux, for example, you simply install (quick), reboot and it's done. No faffing around, it's just done.

Windows 8/2012 aren't much better so will the process ever be easier than it is now?
 
Sadly it's one of the most annoying things outside of pulling the latest ISO or using an SCCM or NETDeploy build. SCCM 2012 allows you to set SP1 as the first update from 2008 R2. Standard WSUS or using Windows Update doesn't.

You can slipstream SP1 onto Server 2008 R2 as an option and rebuild the ISO as another option.
 
One of the most effective ways to kill a Windows installation is to restart while updates are installing.

Though I agree, it's stupid that it doesn't offer the latest service pack as the default option while updating. I can understand that you might not want the latest service pack for compatibility reasons, so the choice to deselect it should be there, but really it should be the default. Sadly it does the same thing for other products - you'll see updates for Exchange or SQL selected but not the latest rollup or service pack.
 
Never had much problems my self. Only one is in 2008 when an update corrupts and borks the server management screen.

It doesnt normally offer the service pack first thing as there some updates required before.
 
Not quite sure what you aimed to gain there, if you install windows 2008R2 thats pre SP1, the first thing you do is install SP1. Then let it do windows updates..
 
It was a slip on my part but I don't see any reason that the built in process shouldn't know to install a service pack first. That's just silly!

My other gripe is that the install process is so slow, a windows 7 laptop took 2 hours to install SP1 from a flat file the other day. It's a lot less painless with an SSD but I can't help feeling there are ways the process could be improved if Microsoft really put their minds to it.
 
always apply SP before letting windows update kick in. windows 101.

:)

its a pain though that MS are no longer deploying SP's, doing a fresh install of W7 SP1 has about 170 updates.
 
neil_g said:
its a pain though that MS are no longer deploying SP's, doing a fresh install of W7 SP1 has about 170 updates.
The plan is to release a new version of Windows every 12 to 18 months. This will force people onto a subscription model the same way that Software Assurance works currently, except for consumers. We're starting to see it with Server 2012 -> 2012 R2.

In 10 years time you won't own a licence, everything will be rented if Microsoft get their way. It sucks.
 
The plan is to release a new version of Windows every 12 to 18 months. This will force people onto a subscription model the same way that Software Assurance works currently, except for consumers. We're starting to see it with Server 2012 -> 2012 R2.

In 10 years time you won't own a licence, everything will be rented if Microsoft get their way. It sucks.

Which is ridiculous as IT depts don't have time to update to the latest version windows every 12 months.
 
Back
Top Bottom