|
Option 3, weirdly I've never had any issues with Windows Updates. Seem to be in a minority.
|
|
|
|
|
Don't worry, you'll never be as minority as someone like me, who
- Always had problems with Windows updates
- Always had problems with driver updates
- Was completetly satisfied with Windows Me given that in 3 years on a crappy old machine never crashed, while 98SE was driving me nuts (at least more nuts than my average).
|
|
|
|
|
I remember Microsoft. I still use it at work; our gatekeepers only allow through essential updates that are proven.
At home I switched from Vista to Linux years ago and never really looked back, although I keep an old box with 7 on in the kitchen for out of the way jobs(like torrents). Every now and again I turn it on and just let it update.
It would be of little consequence if I lost it.
|
|
|
|
|
I don't like anything to be automatic...it always seems to choose the worst possible time to do its thing.
|
|
|
|
|
Quote: it always seems to
This is optimism, and lower your voice - it can hear you! 
|
|
|
|
|
No it can't, I pulled the microphone! 
...oh, wait...maybe it can read my lips through the web cam? 
|
|
|
|
|
|
Option 2 for the same reason as most others, I've had issues with them twice in the last ten years, but if you keep your computer free of malware that's about all you get.
Wrong is evil and must be defeated. - Jeff Ello
Any organization is like a tree full of monkeys. The monkeys on top look down and see a tree full of smiling faces. The monkeys on the bottom look up and see nothing but assholes.
|
|
|
|
|
Well, it's been my experience that MS updates are mainly stable. Installing at inopportune times is another matter .
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
#2. And only critical updates, thank you.
/ravi
|
|
|
|
|
Might be a good suggestion for a poll.
2
|
|
|
|
|
I have never had one problem with a Microsoft update. I have them update critical fixes automatically and I control the rest.
...knock on wood. 
|
|
|
|
|
I recently encountered a case where an entire week was lost because M$oft neglected to consider the new H97 motherboards with isolated graphics adapters in one of their updates. A new driver from the video card manufacturer revealed the fault and an emergency update from M$oft corrected it. If I had known this was the case a lot of unnecessary email with a third party software supplier would have been averted.
|
|
|
|
|
Always 3 for my personal and development machines. 99% of updates exist for a good reason so I have no issue with letting them all in, they have never caused an issue. In fact WinUpdates have saved me and many other PCs I've dealt with from serious issues with drivers and security.
The only time I've ever ignored an update is on fresh OS install where WinUpdate offers graphics drivers etc. While their ones usually work I prefer to get the latest, most correct drivers from the manufacturer themselves. Except on my Surface Pro 3, you definitely want to prefer windows updates to Intels generic driver!
|
|
|
|
|
|
I do 3 once a week. If you do not do it, the update (download) size could become too huge to manage.
TOMZ_KV
|
|
|
|
|
For machines I maintain for others, such as my work machine, or the system the family at home uses, it's (3) all the way.
For my personal machines, I let it download, but I decide when to install. This helps me to avoid most of the broken updates until after MS has already fixed those they decide is worth their time to fix. I used to try to play the I'll-review-and-decide-if-I-want-it game, but I don't bother anymore because MS doesn't provide enough information to make informed decisions anyway.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
|
You know, the part about MS not providing enough information - this is what motivated me to post about this issue. I trailed along trying to determine exactly why they were patching. It was not possible.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
Used to 1 but it got to be a pain so I relaxed to 2 but then I never had any problems so these days it's a chilled out 3 ... age makes you wise (well, to be honest, age makes you lazy but that doesn't sound as good!)
|
|
|
|
|
I do 3 where allowed, 2 where required by group policy. Prefer 3, and haven't had a problem caused by WU in years (last time was a video or audio driver on NT 4). I may just be lucky though.
|
|
|
|
|
I'm on 1 & 3. I'm normally on 1 until I need to install a SP. As I'm not normally connected to the internet on dev machines, it doesn't really matter. It is not a security problem if it doesn't have an external network. I do 3 before I install the SP. Once that is done, the machine is off the network until it needs another SP.
|
|
|
|
|
Option 3 on live production servers. Seriously, how much time do you guys have to manually check everything?
We pay more for MS products so someone else does the checking right? Save me my time!!!
Also, for the last 4 years, never been a problem on win server 2008 r2 (yes, it needs upgrading...)
Yes, it reboots, but you can tell it what time of day to do that.
|
|
|
|
|
|
Are all children now named after cartoon characters, or just the ones to seriously under-age mothers? 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
As I was telling CListCtrl and Bacon last night, one should always avoid fleeting cultural references when naming your children.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
