# What prevents you from upgrading to newer operating system versions? [closed]

What's the top the reason you're unable - or unwilling - to upgrade to the latest available operating system verions?

-

## locked by IainOct 21 '12 at 16:35

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.

## closed as off topic by Dan, RobM, IainOct 21 '12 at 16:34

Questions on Server Fault are expected to relate to server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

This should probably be community wiki. –  Simon Hartcher May 1 '09 at 0:00
It will be soon enough! (A few more answers) –  Eddie May 1 '09 at 2:29

The current one just works!

-
And saving time testing whether everything works on a newer OS –  Matt Lacey Apr 30 '09 at 8:40
What if the new one provided a good ROI? –  Techboy May 25 '09 at 19:09
How does the new one provide the ROI? If the current one works fine then there wouldn't be a whole lot of improvement. If you're big enough to pull solid ROI out of OS features odds are you're also big enough to have tons of third party apps which will break too. –  sparks May 25 '09 at 20:59

I always format / install. NEVER upgrade. Keep it nice and clean. too many places crap can get lost or dup'd.

But if u mean going from older version to a new version, it's generally

1. Price
2. Having to re-install everything again.

edit: This is referring to Windows OS, not linux, etc.

-
Without any sarcasm, I assume you are talking about windows boxes - I don't know why you wouldn't do an upgrade on unix boxes. –  hyperboreean Apr 30 '09 at 8:47
Ubuntu major releases always have some random fault for me if I do an upgrade-- graphics drivers don't work; It can't find my wireless; PulseAudio has broken again-- I always end up doing a fresh install to remove these problems. –  SCdF Apr 30 '09 at 9:05
oh yeah. definately ment windows. soz. i'll update my post. –  Pure.Krome Apr 30 '09 at 23:53
The only OS that I have seen successfully upgrade over 3 versions without breakage is Debian "stable". I wish I could say it's something a little more exotic like VMS or AIX or even HP-UX, but no, it's just a vanilla Debian installation. –  Avery Payne May 26 '09 at 5:26

Upgrading the OS on a server that is hosting lots of websites means many many hours reinstalling the sites on the new server, not to mention the downtime and the ever-present risk of missing some undocumented third-party component or service installed on the old server.

Same is true on a personal computer (though more of the work goes into reinstalling applications, and reconfiguring the environment).

If it ain't broke, don't fix it.

-
I too subscribe to the "If it ain't broke" school of thought. Unless the new thing is shinier, then I have to have :) –  Xetius Apr 30 '09 at 8:31

In a lot of cases, the compatibility of important software is not known. It may be even worse if the software was not updated since some time.

-

For me, it has to be downtime & loss of productivity.

On the desktop front, even though I try and keep my system relatively "clean" in terms of what is installed, it is still set up exactly how I need it. In the past, I've found it takes 2 or 3 days per year's worth of data / applications / settings to migrate to a clean OS install: with data being the most time consuming - checking out scores of projects from a half dozen different SVN repositories just isn't a quick process.

On the server front, "upgrade" is a bit of a misnomer: I would never ever upgrade the entire OS of a server whilst it was "live": critical patches would be as far as I went (if it ain't broke, don't fix it). When choosing a new server, it really depends on the requirements, but others have said, it's not really worth the hassle of being on the crest of the wave with a new OS - let others who can afford to throw money at problems trial and error it.

-
1. Price
2. As far as windows is concerned, before the 1st service pack is almost always buggy
3. Time

pretty much in that order

-
I always believe the "First service pack" rule is a bit of a misnomer. In reality it's more "the first release of a new or significantly rewritten OS". It doesn't just got for Windows, and Microsoft certainly aren't the only guilty party. –  DavidWhitney Apr 30 '09 at 8:10
This is very true, I'm just more familiar with Windows :) –  Glenn Slaven Apr 30 '09 at 8:13

One Lession that I learned the hard way many times, I treat it as a law: You can NOT upgrade Windows. Formatting/Reinstalling is faster than "upgrading" and dealing with the issues. I've got bitten by this so often, even with seemingly straight-forward upgrades like Win2000 => WinXP.

The other reason is the "Never touch a running system" rule. If it runs and there are no security vulnerabilities impacting it, don't touch it.

-

I used to be the kind of guy who would jump to the latest OS as soon as it was out of beta. But with the shift from XP to Vista, I have become more cautious and conservative. You've all heard the horror stories about simple things that broke. For me it was the ability to connect to my company's VPN and use remote desktop to get to my work machine, which incidentally, I still can't get going.

That experience, coupled with the advances we've seen in virtualization recently (which makes trying an OS before you commit much more practical), means I'll be much slower on the uptake of Windows 7.

Short answer: I got burnt. Pain is an excellent teacher.

-
can't go back to vista from 7 –  Alexander Taran May 25 '09 at 21:24

I subscribe to the "If it ain't broke" policy, especially on server versions. Having to go through the pain of working out how to get everything up and working in the new version tends to keep me with the version I currently have.

Only when the new features become essential and required do I feel the need to go through the process again. And then only when the new essential features outweigh the process of working out how to get everything working again.

-

I use Linux at work (Ubuntu 8.10) and I am very wary of updates around the kernel / driver area or updating to new versions (i.e. 9.04) because:

• It currently works
• I can't afford to not be productive for a day+ while I reinstall my OS

At home it's a different story because that's my time...

-

Stability. We know the applications work on the OS they're running on, and any change to the environment can introduce unintended consequences. Usually the OS is updated at the same time we're planning to deploy new hardware. We can purchase the hardware, configure the OS, install the software and test, test, then test some more before deploying to the production environment.

-

I'm usually keen to upgrade to the latest versions of an OS, however the most common reasons I have found for people not want to upgrade is either the compatability of old software, or not wanting to learn a new OS.

-

The hassle of reinstalling all my applications is the #1 reason for me. That and the fact that even after I reinstall, there'll most probably be incompatibilities.

-

I think it depends on the frequency the software is upgraded. If a new version comes out every 3-6 months, I would be upgrading systems almost everyday.

-

Having a large estate of computers which all need to be upgraded together. Having multiple Operating Systems or versions of operating systems complicates support.

Having to migrate lots of machines at once is also more complicated and requires more app compatibility checking beforehand and user support after.

-
• Inefficiency of the new operating system (e.g. Vista)
• Speed of performing common tasks
• No new features which I really like.
-

Time involvement and stability, whether talking about Linux or Windows. With Windows, I haven't tried an upgrade in a long time, but experience has taught me to avoid the first release of any Windows OS. I always wait until SP1 comes out, unless I hear otherwise from friends who are early adopters.

With Linux, I've always used Red Hat. With Fedora, Red Hat releases have become more bleeding edge than they used to be. Due to this, I don't rush to upgrade my Fedora machines. I wait until a release has been out at least a few weeks and I read reviews from early adopters.

I have no experience with Mac (regarding installation and upgrades), but with Windows and with Linux, I find new releases are often not quite ready for prime time. I know if I used a less bleeding edge Linux distribution (such as Debian) then it would probably be more safe to upgrade as soon as a release comes out, but I'm a hacker from way back, and I like solving problems. (That's one reason I'm on SO and SF!)

Above I talked about the stability aspect. For any OS, it's often easier to reinstall rather than upgrade. For Linux, I'll often upgrade once or twice (a year apart) and then do a complete reinstall in place of the next upgrade. For Windows, I normally just replace the hardware and install a new OS on the new hardware. Why ever reinstall Linux? Well, as open source advances, some packages are replaced or discarded. When you upgrade, bits of flotsam are left behind, some in /etc and some in /var and some in other places. On a re-install, all of that cruft is cleaned away.

That's the time involvement. Doing an upgrade takes time to clean up cruft (in Linux, *.rpmnew and *.rpmsave, for example). A full reinstall takes time, of course, to ensure that nothing is lost, everything is reconfigured and reinstalled, and so on.

-
• Current one is still supported by the vendor
• New one does not work with current software (and I can't get a replacement for the current software)
• New one does not work with current hardware (and I have no budget to upgrade/replace hardware)
• The company I work for has not yet tested the OS from a functional and security perspective
-

If not USB support - i'd still be runing windows NT 4 sp6. But since I moved to 2000 I jump on every new client os as soon as it gets out, just to see where MS are going with it. And only tonns of stored data can stop me for awhile, but not for too long.

-

Nothing.

There are usually enough things I hate about the current version that are fixed in the next one that I end up upgrading sooner rather than later. I was on Vista x64 a year after it was out, and everything worked absolutely fine - which was quite unexpected given all the bad reputation it had.

-

(Sorry for the rant, ignore it if you wish, I just had to write this somewhere.)

Windows 8 is just plain ugly and unusable on a desktop system.

Windows Server 2012 is even worse.

Yes, I know, lots of technical improvements and so on.

But the UI totally sucks, and that's a death blow for Microsoft.

-