Microsoft Windows Updates - Don't Do Em
 

I don't think this is being reactionary but for the moment Microsoft Windows Updates - Don't Do Em -- there are a lot of people around, more so with Windows 2000, but a few with XP are also experiencing corrupted machines...

Another network I work with occasionally has experienced this with near 100 computers in their network. I have seen a few instances on XP as well...

Chalk up another goody to M$

Recheck in a weeks time before doing any...

ya THANKS

NOW YA TELL MEEEEEEEEEEE

:wall::wall::wall::wall::wall::wall::wall::wall::w all::wall::wall::wall::wall::wall::wall:

Scott - if it's any consolation - you were patient zero, case numero uno, infection emmeniance, at least out of the people I know ;)

But I do think it is the same thing that happened to your machine..

So what your telling me is I get the booby prize :hee:

Crushed me Tuesday night. All 6 home machines when belly up

whats recovery look like?

any idea which update it is?

i quick google search comes up empty so its not widespread panic yet. but man if i pushed out a bad update to 1000 machines that, makes for one bad week.
don't forget
Disable WUS and the corresponding gp if you have that set up.
I believe its just the BITS service you need to stop for wus to stop.

I have 2 affected machines at the moment (they belong to the other entity but I getsta fix 'em because the other entity might take 2 weeks)... Keep in mind, this will hose 2K servers as well. I'm told the other "entity" has lost a couple as a result...

I'm doing a 2K repair now (haven't had an XP one go down - yet)... 2K CD, Repair..... Just one of the threads I've found so far:

http://groups.google.com/group/micro...92d63167fbd1cc

we are all XP here and no issues reported so far

$5 says it bit me because of the 2k-xp issue a few weeks ago...

So it makes me wonder if that motherboard is indeed bad and it's not just a problem with the system not being able to access anything over 512mb of memory... There was 3 500gb sticks in there and no combination of any two would work but they'd all work by themselves...

kb931765
kb819699

i wonder if you uninstall them before you reboot..man how the h e double hockey sticks did M$ let this one get by!

i bet its part of their plan to move everyone to vista.

never mind KB #s already posted

no.

ps: i bet you all have norton/symantec on your systems.
If you do, then don't download the new updates, if you don't, do whatever you want. :D

norton = worst crap ever.

yes. marketing ploy.

think of the average person who uses their pc for email, basic web surfing. you know has updates set to automatic. Machines poops they go get a new one, whats on the new one.. vista.. tada.. Now not everyone will run out an do that, but theyve got enough of a market share where they dont CARE how many user (savy users) are affected. That doesnt matter, what matters is that they just got some new folks moved to vista. :uhuh:

Never run any update automatically. Yes, it takes time to read the specs etc, but read 'em before you install :jump: Keeping an eye on things via network security focus helps too :)

I am one of the unfortunate vista pioneers- the guys in the shop assured the boss that my laptop had XP but they lied and so I am a captive vista drone.

Win 2003 Server & 7 XP machines still tickin' O.K.

At least as of today !

Let's see do I wisk I had M$ 2000, XP 0or Vista.

I think the answer might be Linux :jump: :jump:

Got on the computer tonite (after a long drive to NY to get my kid home from college), came home, turned on the 'puter, ran the requested update from MS, then logged on to S-B.com So far so good....wish I'd known first.

no kiddin ?
my pooter is F($*$& up for DAYS now.
My bro Norb had to manually removed the installation updates to get his server running again, took HOURS. Someone at microsoft needs a good swift kick in the nuts. This is just nuts.

I celebrated the Vista release with a Linux book and a fedora download, glad i did!

My server 2000 boxes are OK, as well as the dozen workstations I have in the building, I'll consider myself lucky!

The infected PC's boot fine and permit you to login. But when u do, it runs CPU usage up to 100% on one of the svchost.exe which renders the machine pratically useless. Ending this process (if you can manage to get to the task manager, list by CPU usage and select it before cpu usages pegs 100) will enable you to use the pc until Microsoft gets a fix albeit some things may not work as they should.

Just another reason why you SHOULD NOT have your computer do automatic updates. You can have it turned on, and even download them if you want but do NOT have them auto-install until you know they are usable. Just my 2 cents.

Hope this helps....

ND

Microsoft=crap

Jeeze, atleast give a solid fix.

Turn off automatic updates in the control panel, then:

Control Panel -> Administrative Tools -> Services -> right click automatic updates -> properties -> set the service to disabled.

find patches in add/remove programs, remove them, rejoice.

how is this related to the reboot loop symptoms im reading about/?

Prize
 

Scott, no prize just the booby.:)

It is somewhat related as that is another symptom I've been seeing on XP machines. Most XP machines afflicted with this have been acting this way instead of the constant reboot which is more prevalent on the W2K boxes...

Same issue, different symptoms...

Anyone hear of an official M$ fix yet?

havent heard anything yet, been digging all morning. We do not have a contract with m$ so a call would cost some bucks...

basically we just denied updates at the firewall until this gets sorted out.

Excellent job! You get a cookie!

Does auto update have its own IP port it uses?

not that i could find, i blocked
"update.microsoft.com/*" on both 80 and 443
as well as
65.55.192.29, 65.55.192.61 (nslookup)

http://forums.microsoft.com/WindowsO...19628&SiteID=2

Did some more digging. Seems to be an issue with a certain version of Windows update and Office update. Since its version specific this may explain why it affects only certain PC depending on which Autoupdate is installed along with MS Office.

Best thing to do is to disable Autoupdate as Likwid described above.