Microsoft Windows Updates - Don't Do Em - Striper Talk Striped Bass Fishing, Surfcasting, Boating

JohnR · 05-10-2007, 01:17 PM

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...

UserRemoved1 · 05-10-2007, 01:21 PM

ya THANKS

NOW YA TELL MEEEEEEEEEEE

:w all:

JohnR · 05-10-2007, 01:28 PM

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..

striperman36 · 05-10-2007, 01:37 PM

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

MrHunters · 05-10-2007, 01:48 PM

Quote:

Originally Posted by striperman36

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

whats recovery look like?

any idea which update it is?

JohnR · 05-10-2007, 02:57 PM

Quote:

Originally Posted by MrHunters

whats recovery look like?

any idea which update it is?

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

UserRemoved1 · 05-10-2007, 01:36 PM

So what your telling me is I get the booby prize

MrHunters · 05-10-2007, 02:00 PM

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.

MrHunters · 05-10-2007, 03:16 PM

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.

RImike · 05-10-2007, 03:19 PM

never mind KB #s already posted

EricM · 05-10-2007, 03:50 PM

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.

Megabyte · 05-10-2007, 08:40 PM

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

Sweetwater · 05-10-2007, 08:41 PM

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.

Diamond Tackle · 05-10-2007, 08:43 PM

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.

crash · 05-10-2007, 08:50 PM

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!

NJTackle · 05-10-2007, 09:12 PM

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

Striperknight · 05-10-2007, 09:41 PM

Microsoft=crap

likwid · 05-10-2007, 10:02 PM

Quote:

Originally Posted by NJTackle

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.

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.

NJTackle · 05-11-2007, 08:56 AM

Quote:

Originally Posted by likwid

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.

Excellent job! You get a cookie!

MrHunters · 05-11-2007, 06:32 AM

Quote:

Originally Posted by NJTackle

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

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

JohnR · 05-11-2007, 07:43 AM

Quote:

Originally Posted by MrHunters

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

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?

Swimmer · 05-11-2007, 06:53 AM

Scott, no prize just the booby.

MrHunters · 05-11-2007, 08:16 AM

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.

JohnR · 05-11-2007, 09:26 AM

Quote:

Originally Posted by MrHunters

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.

Does auto update have its own IP port it uses?

NJTackle · 05-11-2007, 09:31 AM

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.

ThrowingTimber · 05-11-2007, 09:35 AM

why would anyone even bother having auto update or auto install enabled?

Dont you want to know whats going into your boxes?

MrHunters · 05-11-2007, 09:36 AM

Quote:

Originally Posted by ThrowingTimber

why would anyone even bother having auto update or auto install enabled?

Dont you want to know whats going into your boxes?

no i like to live in ignorance... always trust microsoft.. they know whats best for us

JohnR · 05-11-2007, 11:10 AM

Quote:

Originally Posted by ThrowingTimber

why would anyone even bother having auto update or auto install enabled?

Dont you want to know whats going into your boxes?

Try running 2000 nodes, 3000 users, across 8 buildings with 3 techs (including net admin). You are forced to take a few extra risks... (though the funny thing is that my machines have not had this problem - just the ones I manage for the other entity)...

JohnR · 05-11-2007, 09:36 AM

Quote:

Originally Posted by NJTackle

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.

I'll try this at some point if it applies to the high utilization XP boxes but there repair is different for the rebouncing W2K boxes...

likwid · 05-11-2007, 11:20 AM

Quote:

Originally Posted by JohnR

I'll try this at some point if it applies to the high utilization XP boxes but there repair is different for the rebouncing W2K boxes...

John, its "Microsoft Update" thats the issue, not Windows Update apparently.

Just fixed it on another box.