Linked by Eugenia Loli on Thu 12th Jan 2006 07:36 UTC, submitted by Resolution
Permalink for comment 85159
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2005-07-09
Didnt happen to me. I always disable the automatic updates. Common sense. I decide what gets put on my computer. I decide if I will patch my computer. Not MS. So I go once a month on patch tuesday to MS update service and get my machine up to date. Not really hard. And not something one forgets to do.However I do see MS's reasoning behind this as crappy as it may be in reality. MS wanted to get this flaw fixed especially since it has been around since Windows 3.0!!! But maybe MS should have had a check...if the system processor is not being used or the hard drives are not spinning with I/O or the NIC card is not being used...or other scenarios then reboot. Something nicer than people getting their data fubared.