Linked by Thom Holwerda on Sun 11th Nov 2012 15:49 UTC
Windows "Yesterday my desktop died, and so I went ahead and got a brand new Windows 8 laptop. It's always been my feeling that as years go on, user experience has been going down for people who use a computer and the Internet, because of decisions all companies make that are clearly anti-user, either because they think they know best, or in many cases, for financial gains. But from spending all night reinstalling everything and customizing the laptop, I realized just how bad it has become." Probably the biggest reason to go Mac or Linux. Such a shame Microsoft found it more important to pressure OEMs into silly Secure Boot nonsense instead of doing something about the anti-user crapware disaster. Goes to show who Microsoft cares about. Hint: it ain't you.
Permalink for comment 542166
To read all comments associated with this story, please click here.
RE[2]: Comment by ilovebeer
by ilovebeer on Mon 12th Nov 2012 16:39 UTC in reply to "RE: Comment by ilovebeer"
Member since:

As far as taking several hours to install & customize Windows -- that's just a silly. Unless you're being stupid about reinstalling, for example not using the most recent OS image, and you're installing a million apps there's no reason what-so-ever it should/would take all night. That's completely ridiculous.

That's assuming you have an OS-image at hand. But what if you've just gotten the PC and you don't have an OS-image yet? Downloading and installing the several hundreds of megabytes of patches alone does indeed take around two hours.

I don't count ISO download time (whether it's Windows or linux) towards installation time because downloading what you need is pre-installation, not installation. None-the-less, the download time isn't that long for anyone with a decent internet connection. Also, 2 hours is a long way from an installation taking several hours to all night along. I stand by what I said -- if it's taking you all night long, or even several hours, then you're doing something wrong or are completely unprepared.

There is something, however, about the way Windows applies certain patches that slows the whole process down without any seemingly good reason: the .NET patches. For some reason even on my quad-core system those patches can take over 25 minutes to apply, and I've had the patches actually get stuck in some sort of a never-ending loop several times where CPU-usage is at zero, and even after leaving the machine on for a whole night it still wasn't finished in the morning -- only a reboot or two and then trying to reinstall the patch fixed it.

Another user already explained this so no need to do it again. Without question .NET can be the longest part, but it also has legitimate reason.

Reply Parent Score: 2