Subscribe to Windows IT Pro

 

Get Newsletters

  • Get the Latest News
  • Product Updates
  • Helpful Tricks
  • Productivity Tips

Subscribe Now!

December 05, 2007 12:00 AM

How Do People Hate Vista? Let Me Count the Ways…

Windows IT Pro
InstantDoc ID #97721
Rating: (6)

Last month, in my commentary "Why, Exactly, Does Everyone ‘Hate' Vista?", I enumerated a few reasons that I thought might explain people's disdain toward the new OS, and I asked for your thoughts on the matter. Many thanks to all of you who shared your Windows Vista stories with me! Here's a far-too-short (I've only got so much space per month!) distillation of your comments and some thoughts of my own.

"Vista has a different UI than does Windows XP, and it seems not to offer much of anything worth upgrading over." I'm not surprised to hear this argument from many people. As I've observed before, computer technology isn't changing as quickly as it used to, and every new version of Windows will probably offer fewer new things. XP is a very nice OS, and if we'd not seen anything new between 2001 and the 2012 arrival of Windows 7 (the current name for Vista's 2012 replacement), the world would keep turning, our businesses would keep running, and we'd all be fine. But I still don't understand why that justifies hating Vista. As I recall, users expressed a lot of vituperation about how XP's UI was so much "harder to understand" than Windows 2000's UI.

"Vista is slower than XP." The same could be said about virtually every OS when compared to an older one. Vista is intended to be Microsoft's desktop OS offering for the next five years or so, so it anticipates ever-faster machines--just as XP did when it was first released. The fact that computer hardware gets a bit faster every year is why XP seems zippy now but was derided as a dog by many when it first arrived. When Windows 7 comes around, it'll seem slow in comparison with Vista on 2012 hardware. Every new OS has this characteristic, so--again--why does it engender the "hate" that I've heard from readers?

"Vista's requirement for activation is annoying." I hate to say it, but, I told you so! When product activation arrived with XP, I understood its purpose--it's a copy-protection scheme that protects Microsoft's market revenues. As someone who makes his living from copyrighted materials, I chafe at every stolen copy of my stuff. But would I force every one of my readers to call me up and "validate" every one of my books that they've purchased before they could read them? Of course not; that would be obnoxious and irritating. But, as I argued back in 2001, Microsoft can do this to its customers for one reason and one reason only: It's a monopoly. Forcing us to deal with product activation was an abuse of monopoly power then, and it's one now.

Microsoft knew that it didn't have the power to make its large customers swallow product activation, so Redmond let volume customers essentially bypass activation. This, I argued, was a divide-and-conquer tactic, and I predicted that the next version of Windows would require activation for volume customers. I was right, but only partially so. Volume customers have to install something called a Key Management Server (KMS) system that does a sort of "pretend validation." The volume customer's KMS does for that customer's copies of Vista what Microsoft's product activation servers do for retail copies of XP and Vista: essentially "blessing" the copy of Windows to run for some period of time. Furthermore, the KMS server doesn't even really keep track of which systems it has activated nor of how many. So, what good is the system then? My guess is that Microsoft is slowly "setting the hook" in the mouths of volume customers, paving the way for a day--Windows 7? Windows 8?--when volume customers must host their own onsite Microsoft activation server.

So heck, if you want to hate Vista for its activation policies for volume customers, then go ahead and hate it. But remember that XP is really what you should find unacceptable, as it first forced that annoyance upon millions of home and small business users.

Meanwhile, I've found my own reason to chafe at Vista: Its increasingly frequent automatic updates. XP and the like seem only to get one bunch of security updates on Patch Tuesday, the second Tuesday of the month. But hardly do three days go by without Vista nudging me to reboot it so that it can install Windows Defender updates. Defender needs to reboot to update its pattern files? Gimme a break.

Please keep sending me your Vista stories, and thanks!

Related Content:

ARTICLE TOOLS

Comments
  • Joshua
    4 years ago
    Jan 02, 2008

    The thing about Vista is that it's worse than XP in just about every regard, so the tradeoffs you mention aren't offset by any gain. It's slower, needs more resources, has a more annoying interface, is much less stable, is buggier. It's more expensive, it's fussier about activation, backup is now useless. Most of the new features don't work very well. UAC is unusable. Sleep mode still doesn't work reliably. The new search feature isn't well thought out. About the only thing I can find to like about it is the new look -- and that's hardly worth making my quad core RAID 0 screamer run slower than my six year old Pentium IV XP machines.

    I've been struggling with Vista ever since it was a release candidate. SP 1 turns it into the equivalent of a beta; before that, it behaved like an alpha, with fatal errors that made it unusable in a production environment. How dare MS charge me an arm and a leg for something they pushed out the door prematurely because they were under pressure to ship?

    Every MS upgrade I've installed in the past has offered something worthwhile. Sure, they were slower and used more resources, but I always got something valuable in return -- proportional fonts, multithreading, memory protection, plug and play, system restore, what have you. Now, I'm actually going to downgrade Vista to XP. I'm far from the only person who has done that.

  • Christopher
    5 years ago
    Dec 11, 2007

    It seems to me that one of MS's underhanded tactics for forcing people to upgrade--the "end of support" date--is totally ineffective.

    Through all the hundreds of problems I've fixed on my Windows machines (Back to 95) have never once actually spoken to someone at MS. Their support doesn't exist right now, as far as I'm concerned, so what does it matter which arbitrary date they declare a product to be at its end of life?

  • Pekka
    5 years ago
    Dec 10, 2007

    Lots of problems with various Vista drivers, some of them really annoying. For instance a paper jam in the printer can't be resolved normally. The printer will stay in offline status. When you turn the printer offline, the status is offline - offline. You get the other offline away, when you turn the printer online, but there is no other way to get it online than reboot. Also, different software applications seem to fight for the same components. One application provides its own content for a component and the other application won't work with it. Vista seems to be stable, though.

  • David
    5 years ago
    Dec 06, 2007

    When XP Pro came out, I actually used one of the release candidates on my main company machine - that's how much better it was at release than anything MS had done previously. Not so with Vista. I waited for the final release, bought a new laptop with Vista on it, and while I see some benefits, it is certainly not miles ahead of XP like XP was to 9x or 2000.

    In fact, one major bug I've run into (i.e. the laptop will essentially sit 5+ minutes with hard drive thrashing when coming out of hibernate or switching from power/battery mode) has seriously caused me to think about switching back to XP.

    Anyway, no Vista for our company until at least SP1 comes out - maybe even longer than that.

  • Alan
    5 years ago
    Dec 06, 2007

    I had to install VISTA on our new computers here at school along with Office 2007 (another horror story), in addition to having an XP partition for the "Windows" class..

    We are running the "Business" version and the main problems I see are the UAC (User Access Control) -- does it need to be turned on or off-- it seems to differ for each problem experienced; and the fact that Microsoft has determined that the print spooler failing when you try to connect a network printer to it at logon time, is a "minor thing" and a fix can be held up until "service pack" time. Having to rebot the computer 2 or 3 times until the spooler does NOT fail is more than a pain. Why do you have to reboot? you may ask. Because Microsoft has decided that one must be an Administrator to restart the Print Spooler service. Would you want students logging on as Administrators?

You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

White Papers

Get your Windows 7 deployment off to the right start by implementing PC lockdown. A locked-down environment is easier and cheaper to support since users are less likely to make unnecessary changes to the core system configuration - read more here!

Essential Guides

Is your iSCSI "lossy"? The reality is that most off-the-shelf Ethernet hardware deployed for iSCSI can lose packets, resulting in slow performance or application downtime. Learn how to assess your current iSCSI infrastructure and engineer an advanced iSCSI SAN infrastructure.

Web Seminars

What's the best way to keep your network safe from malware? In this web seminar, security expert Greg Shields suggests an alternative method to the traditional blacklisting approach that is common with anti-virus and anti-malware solutions.

eLearning Series

We bring the experts direct to you to share their real-world perspective and expertise. During each event, three sessions stream in real time, so you can learn, ask questions, and get solutions.
Upcoming event: Getting the Most with Exchange 2010 with Paul Robichaux

Subscribe to Windows IT Pro!

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.