Patch That POS PC!!

HardOCP News

[H] News
Joined
Dec 31, 1969
Messages
0
Microsoft says they are seeing another wave of attacks that are targeting an exploit patched last month. You know what that means, there are a bunch of people out there with unpatched boxes and most of us know who they are. So, let’s all do our civic duty and when we visit relatives tomorrow on Turkey Day…patch their POS PC. We will all benefit from your act of kindness. ;)

It is also interesting to note that the worm patches the vulnerable API in memory so the machine will not be vulnerable anymore. It is not that the malware authors care so much about the computer as they want to make sure that other malware will not take it over too... More details are available in our encyclopedia write up.
 
I may not leave automatic updates on, preferring to wait a couple days to see if one of the updates is borking boxes. But if no problems likely to affect me popup I update, usually within a couple days.
No real excuse weeks later unless in a corporate environment and the patch was actually borking things on their patch roll out test machine. Almost criminal.

Oh, almost forgot, here is the obligatory, "Malware and virus writers should be shot, hung, skull dragged, raped with a rusty tire iron, stabbed numerous times, have their penises fed through a meat grinder, then drawn and quartered in a public venue." Ahh, I feel better now. ;)
 
ive found it extremely rare to have auto updates in windows to harm my pc's... but for boxes like my parents and stuff i leave updates off because of the auto-shutdown process that the auto-update brings. i find it better to just update their boxes when i see them, and let their pc's otherwise run as they wish.
 
With automatic updates on, my family members don't have to worry about these things. Oh, and the chances of a Microsoft update breaking the system are lower than the chances of a hacker's exploit breaking the system, so umm, yeah, automatic updates FTW.

This is one thing I like about Vista. Between automatic updates, daily Defender scans, and weekly defrags it can last more than a week in the average family environment.
 
I can't stand using my father's PC. <.< So much bloat running that it flat out sucks. At least he uses Automatic Updates so his PC stays patched. Will check my sister's laptop though although since I gave it to her she should be patched just fine. :)

My fiance's PC now stays patched because I gave her PC a thorough scrubbing when i first met her. :)
 
I got infected by this the other night. I was able to clean it out though. I hadn't done a bunch of updates. That's my fault. :(
 
My dad probably hasn't updated in over a year and he recently hot hit was some pretty bad spyware. I guess it's time to tell him stop being lazy and update :D
 
Great! When Steve patches his POS then the world will be a much better place. ;)
 
At least he uses Automatic Updates so his PC stays patched.
The only problem is many of the good updates (SP3, IE7 come to mind) actually need the user to install them... Not entirely automatic.

Oh, and the chances of a Microsoft update breaking the system are lower than the chances of a hacker's exploit breaking the system.
Shoot, I even do this to my servers. Call it risky or knock on wood, I've never had an issue with any of it. If there's some high-priority security patch, I'm taken care of right away ;)


but for boxes like my parents and stuff i leave updates off because of the auto-shutdown process that the auto-update brings.

I may not leave automatic updates on, preferring to wait a couple days to see if one of the updates is borking boxes. But if no problems likely to affect me popup I update, usually within a couple days.
No real excuse weeks later unless in a corporate environment and the patch was actually borking things on their patch roll out test machine. Almost criminal.

Oh, almost forgot, here is the obligatory, "Malware and virus writers should be shot, hung, skull dragged, raped with a rusty tire iron, stabbed numerous times, have their penises fed through a meat grinder, then drawn and quartered in a public venue." Ahh, I feel better now. ;)
 
GAHHH!!!! Second time today my wrist hit the touchpad and posted... Darn lack of an edit button!

but for boxes like my parents and stuff i leave updates off because of the auto-shutdown process that the auto-update brings.
I teach logoff.
A ton easier. Good for two reasons.
1) No stuff running. Perfect for your above reason right there. Auto-update reboots the PC? No worries.
2) Fresh load of apps each day. This in itself does wonders. On my network NOBODY did this when I started, and I constantly had issues where all I had to do was either reboot or just restart the app. Logging on each day, those problems are virtually nonexistent.
 
The only problem is many of the good updates (SP3, IE7 come to mind) actually need the user to install them... Not entirely automatic.

Not applicable to security patches. Functionality updates (whether or not they include previous security patches) should be up to the user.
 
I did my duty, cleaned up my roommate's parent's PC.

4 year old computer with XP that had never been patched at all (but we have Norton antivirus! Why would we need patches?).

It was still afraid to hook it up to my network after it was wiped. God knows how much crap this computer had on it.
 
I may not leave automatic updates on, preferring to wait a couple days to see if one of the updates is borking boxes. But if no problems likely to affect me popup I update, usually within a couple days.

I can't remember the last time that an automatic update from Microsoft has screwed anything up. I understand better safe than sorry but for you average home user I don't think this is really an issue.

Video driver updates are a different story, but OS updates, eh, no big deal.
 
ive found it extremely rare to have auto updates in windows to harm my pc's... but for boxes like my parents and stuff i leave updates off because of the auto-shutdown process that the auto-update brings. i find it better to just update their boxes when i see them, and let their pc's otherwise run as they wish.

What do you mean auto shutdown? It will just ask them to reboot their machine. They can tell it no or just do it real quick. Are you telling me that if their machines ever shut down due to a power outage they would never be able to get back into it again?

I did the same to my fiance...not her computer. Viruses are something no one needs :p

LOL. Yes everyone should make sure their significant others is stays virus free also.

I can't remember the last time that an automatic update from Microsoft has screwed anything up. I understand better safe than sorry but for you average home user I don't think this is really an issue.

Video driver updates are a different story, but OS updates, eh, no big deal.

Last one I can think of was an update about 2 years ago or something like that which caused issues with realtek network and audio drivers. I know my work had issues with 2 or 3 machines. I think it was ABC that was knocked on its ass for the day though due to most of their machines using the drivers that confliected with the update. :( It was one of these things where a zero day exploit was found. Microsoft decided that it was major enough that they couldn't wait for the normal testing and through it out to everyone as soon as they got it done. Which I guess in a way killing the tcp/ip stack on a machine would help prevent it from being infected.

But for the most part I too have not seen windows updates cause any issues. XP SP2 took out a few programs. MMC v3 (which would have came with XP SP3) causes issues with Diskeeper v9 in that it will give you an error that you can tell it to ignore. But I still have WSUS set to auto approve mostly anything other than service packs and features.

For your home user they should be fine with auto updates. But for a company or something like a hospital where they need to be 100% sure the machines don't have any ill side effects it would still be a good idea for them to be safe than sorry and do a few days of testing. As there is aways that chance that one of their programs might run into a slight problem with something that gets changed in a service pack or an update.
 
Last one I can think of was an update about 2 years ago or something like that which caused issues with realtek network and audio drivers. I know my work had issues with 2 or 3 machines. I think it was ABC that was knocked on its ass for the day though due to most of their machines using the drivers that confliected with the update. :( It was one of these things where a zero day exploit was found. Microsoft decided that it was major enough that they couldn't wait for the normal testing and through it out to everyone as soon as they got it done. Which I guess in a way killing the tcp/ip stack on a machine would help prevent it from being infected.

But for the most part I too have not seen windows updates cause any issues. XP SP2 took out a few programs. MMC v3 (which would have came with XP SP3) causes issues with Diskeeper v9 in that it will give you an error that you can tell it to ignore. But I still have WSUS set to auto approve mostly anything other than service packs and features.

For your home user they should be fine with auto updates. But for a company or something like a hospital where they need to be 100% sure the machines don't have any ill side effects it would still be a good idea for them to be safe than sorry and do a few days of testing. As there is aways that chance that one of their programs might run into a slight problem with something that gets changed in a service pack or an update.

It is why I said "for your average home user". For a corporate environment you'd obviously want to be more careful. Thanks for the examples though.
 
I can't remember the last time that an automatic update from Microsoft has screwed anything up. I understand better safe than sorry but for you average home user I don't think this is really an issue.

Video driver updates are a different story, but OS updates, eh, no big deal.

I prolly don't have any reason to worry, but once bitten.....
I am talking about, me personally, waiting only 2 or 3 days after the patch comes out to be sure it is not one that MS decides to recall or one that others with similar software/hardware setups to mine have issues with. Not weeks or months later. In any case, I did not recommend that other home users do it, or in any way say it was OK to skip them.
 
What do you mean auto shutdown? It will just ask them to reboot their machine.
Not 100% true. It CAN automatically reboot if you've got it set to be 100% automatic. Mine does it on occasion.

On my business network, I have it set to if the users are logged on: it asks them and never will shut down without prompting.

Last one I can think of was an update about 2 years ago or something like that which caused issues with realtek network and audio drivers.

Drivers are a different story. OS updates are fine but Microsoft drivers through Auto Update = disaster.
 
Not 100% true. It CAN automatically reboot if you've got it set to be 100% automatic. Mine does it on occasion.

On my business network, I have it set to if the users are logged on: it asks them and never will shut down without prompting.

Sorry I was talking about the average home users, not business. If you are not logged in with an admin account then it will just tell you that you have x amount of time before it is going to restart with you having the option to restart later. Or atleast windows 2000 did, I think it gave you 5 minutes. To be honest I never seen that under XP so I don't know if it does the same. I have only ever see it tell you that you need to reboot for windows to finish updating. However in either case it is a restart and you normally are given some type of advanced warning. it isn't like it finished installing 10 of 10 then your machine powers off 0.1 seconds later. Under vista I have always seen it prompt me to restart now or for it to ask me again later.

Now if I am away from the machine when it gets done then yes it might just go ahead and restart as I didn't click on anything and it took that as a ok restart.

Drivers are a different story. OS updates are fine but Microsoft drivers through Auto Update = disaster.

I wasn't talking about a driver update there. It was your standard critical windows xp update KBXXXXXXXX. However something that it changed in windows itself rendered certain realtek audio and network drivers to fail to start any more. And only under certain situtations.

I wish I could have found the article about when that happened. All i remember is that one of the tv stations (which I want to say was ABC) having their machines set to autoupdate for the entire network and it just so happened that they had the right settings for this windows update to take out something like 90% of the computers in their network. And it wasn't just them, I think about 3 or 4 large companies where named at the time. However the TV station was the "bigest" story of course.

Normally you aren't going to see much of an issue as microsoft test their updates before they get released. They go to small test group that gets the updates the moment that microsoft things they are ready and they see how they work for them. If everything goes ok for them then the rest of us gets them during the next monthly rollout. If it doesn't work fully then they fix the problems and try again. However every now and then you are going to have that 1 patch like the one i mentioned that can't be put through the normaly delay due to the level of the threat and they will decide to deal with the backlash of patching too quikcly and causing a few problems other than patching too late and taking backlash for not doing enough in time.
 
Vista does, in fact, auto-restart if you have everything set to full automatic. It's quite convenient, actually. If you put your computer to sleep or hibernate, Vista will wake itself up in the middle of the night, download updates and perform maintenance such as Defender scans and defrags, restart to install the updates, (attempt to) reopen the documents, web pages, and programs you had open before the restart, and put itself back to sleep. The next morning, you often cannot tell that anything happened.

Of course, if you leave unsaved work open, Vista will not auto-restart but will instead ask you to restart the next day.
 
Back
Top