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

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.

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/microsoft.public.win2000.general/browse_thread/thread/3ba9f669462174a/3392d63167fbd1cc?lnk=st&q=windows+2000+patch&rnum=8#3392d63167fbd1cc

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

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/microsoft.public.win2000.general/browse_thread/thread/3ba9f669462174a/3392d63167fbd1cc?lnk=st&q=windows+2000+patch&rnum=8#3392d63167fbd1cc

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

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

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

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.

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/?

Scott, no prize just the booby.:)

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?

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.

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!

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?

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/WindowsOneCare/ShowPost.aspx?PostID=1319628&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.

why would anyone even bother having auto update or auto install enabled?:confused: Dont you want to know whats going into your boxes? :vamp:

you more than likely already know this but i use this site all the time to find known ports
http://www.iana.org/assignments/port-numbers

http://forums.microsoft.com/WindowsOneCare/ShowPost.aspx?PostID=1319628&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...

why would anyone even bother having auto update or auto install enabled?:confused: Dont you want to know whats going into your boxes? :vamp:

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

why would anyone even bother having auto update or auto install enabled?:confused: Dont you want to know whats going into your boxes? :vamp:


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

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.

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

Just fixed it on another box.

I think you are right - as I am seeing that on machines that use that ms update instead of auto update. The machines I am seeing this on are not "my" machines, but another entities machines inside my building so I am far less familiar with their setup than my setup ;)

BTW - fix for the W2K machines I'll type up in a little bit...

Ummm... my computers have problems. One is a pc the other a laptop, both xp. The pc, in particular, has issues. It will sometimes not shutoff, then sometimes when I start it freezes before loading windows. Then sometimes it will open and do the really slow super high pc usage business. Sometimes it works ok. It also has norton on it.

Should I do what likwid said on the first page of the thread? I also gotta get rid of Norton I think cause it seems to be a bugga. I am not computer illiterate, but not very literate either when it comes to this stuff.

How come the baloney sandwich doesn't fit in the slot anymore?

How come the baloney sandwich doesn't fit in the slot anymore?
cause ,Thats the cup holder, even I know that.
ijut.

I disabled the auto update and seem to be running fine now, cpu usage is not maxing out anymore.

Uninstall "microsoft update" and let us know if it all goes away.

I turned off my suto updates 3 weeks ago because an update last year screwed up my mail and had to keep doing restores at least once a week. Microsoft had been working with me but nothing works.

On 2K machines what I have done to get 'em fixed... Steps off the top of my head... If the machine has vital local info dupe the hard drive with Ghost, GPARTED (great utility), or some other imaging software in case this doesn't work

Boot of a 2K SP4 install disk (if you don't have a SP4 version you could slipstream one).

Go into Repair the W2K installation to recovery console

Log in (need to know local administrator account or you'll need other tools to go in :wall: )

at the prompt type fixboot to repair the MBR

Bounce the machine

Boot again off the CD

Choose to repair the Win2K - it will ask you a couple times to make sure. If you don't have an ERD it will usually find the C:\WINNT default folder. Or you can make an ERD off an identical operating machine (didn't need to but should work)

When offered to Auto or Manual repair, chose M and hit enter (with all options selected)

You'll be prompted to overwite files - choose A to overwrite all. This will overwrite the files - all except some which error which are the IE6 files which you will skip.

Essentially you are reloading ALL of the system files on the machine - with IE5 installed. Once done, reboot into the logon

Sometimes you may need to run the file repair process twice (happened one out of three times)

So now you have a vanilla reinstall of SP4 with IE5 and no hotfixes. Run the IE6.1 install from MS or break out your technet discs and fine the IE6 network install - run it..

Go and start the Windows Update and download the newer Window BITS tool (it will walk you through) but do not install the Microsoft Update. Those of you with WUSs servers or doing things through a GPO can alter accordingly :hee:

Run all of the updates except for the 931786 (it's 9317xx - I remember that much).

I had 3 computers to do this to today and was able to recover two of them. One machine lost all of its fonts and IE/Outlook as well as a terminal emulation app are fubared. I would consider running the process again but I started a little vacation today so one of the other guys will do it Monday :tooth:

Unfortunately, limping some old machines through is necessary for specific application computability - otherwise they would be XP...

I have not heard of this impacting any of the 800 or so PCs (mostly XP) or servers 2K under my control :alien: knock on wood

Anyone hear anything official from MS?

NERD

chrome dome

and the term is geek, as in "It is Fashionable to be a Geek, women find us sexy today, as they did a man that could fix cars 30 years ago", YOU, Mr Radio Man, were a card carrying member of the A/V team :tooth:

geek

yes

new machine is the nads so far. 3 hard drives and two ghost. Good for now. I'm going to play with this other machine and see if I can get it working again. Maybe new disc will make it easier to fix the boot stuff.

chrome dome...it's all falling out nowadays :hee:

Do you have any idea how mean that was to a senial, ADD, old guy?:shocked: :huh:

oh so thats what you do on your Friday nights.

:cheers:

i found a great free program to slip stream and add a whole bunch of other stuff. The name escapes me right now but ill post when i go to my laptop.

oh so thats what you do on your Friday nights.

:cheers:

i found a great free program to slip stream and add a whole bunch of other stuff. The name escapes me right now but ill post when i go to my laptop.


Go to msfn forums - all kinds of great resources & tutorials... You probably thinking of NLITE ,,, Good Stuff - Get GPARTED too :hee:

Sorry Fred :tooth:

Microsoft Update Feature Locks Up User PCs

May 11, 2007 7:51 p.m. EST


Geoffrey Ramos - AHN Staff Writer
Redmond, WA (AHN) - A Microsoft update that was intended to fix flaws in the software company's products kept users from using their computers because of a long-standing bug in the update system itself.

Shortly after releasing seven security updates on Tuesday, Microsoft support boards was flooded by angry users complaining that their computers had locked up because of a bug in the Windows Server Update Services (WSUS). Until Friday, some users were still having problems.

The problem, which has plagued Microsoft users for months, causes the Windows Automatic Update feature to lock up. A component of the software, svchost.exe, eats up 100% of the computer's resources, during the update and renders the entire system unusable. Users need to reboot to get their computers running again.

A fix was released by Microsoft on Thursday. The hotfix can be downloaded and installed manually on Windows XP and Windows Server 2003 systems. The patch will be available as part of the Microsoft Update bulletin late this month or in June.

To completely fix the bug, users are urged to download and install a new stand-alone WSUS version 3.0 client.

"It's important to keep in mind that the new WSUS client is only a partial solution and clients must have both KB927891 and the new 3.0 client installed for a full solution," the WSUS team said in its blog.

Go to msfn forums - all kinds of great resources & tutorials... You probably thinking of NLITE ,,, Good Stuff - Get GPARTED too :hee:

Sorry Fred :tooth:

nlite it is :) :uhuh: