Linked by Thom Holwerda on Wed 1st Apr 2009 13:48 UTC
Bugs & Viruses We're well and deep into April 1 now, and if you were to believe some of the reports and hype on the internet, we should've all been paying in bottle caps right about now. As any sane person already saw coming, the Windows worm Conficker didn't do anything. It just kind of sat there, patiently mocking all those who did not update their machines properly.
Permalink for comment 356332
To read all comments associated with this story, please click here.
RE[7]: April Fools
by darknexus on Wed 1st Apr 2009 21:39 UTC in reply to "RE[6]: April Fools"
Member since:

Oh, I have. Anyone remember what happened, initially, when you tried to install IE7 on XP via Windows Update, and you got unlucky enough to have it error out half-way through the installation? That caused one hell of a mess on any system affected. Been there, done that. It was fixed fairly quickly, but not quickly enough to prevent a lot of people's systems from getting screwed up.
Plus, Microsoft's method of releasing updates and additional patches leaves a lot to be desired. What, may I ask, is the point of having .NET Framework and then on top of it have to download hotfixes or service packs (.NET is merely an example here, there are others)? Novel idea, why not, when a service pack is released, repackage the whole thing with the service pack slipstreamed into it? Leave the hotfix up for those who've already installed the base package, but for those who didn't, we wouldn't have to run cycle after cycle of windows update checks to make sure we've got all the patches, meanwhile having to deal with their temporary files that are left over and weren't deleted when they should have been?

Reply Parent Score: 2