Automatic Updates runs every day with up to 16 "new" updates - what gives?

[bobbiev]

I just upgraded my computer. It now has Windows XP Pro, sp3, Ver. 2002, Intel Core 2 Duo CP, E6400 @ 2.40 GHz, 2.39 Ghz, 3.25 GB of RAM, a 500 gb hard drive divided into 80 gb and 420 gb.

I had turned on Automatic Updates and my computer was spending up to an hour installing these updates, anywhere from 5-16 a day, upon shutdown.

Any suggestions as to why this might be happening?

I have turned off Automatic Updates and check weekly for new updates. This seems to work but I really would rather use automatic updates.

I read another post from 2002 which has an response of "XP Pro" does not need all of the updates that MS wants to send. The poster suggested removing some of the updates. If that is a good idea, how does anyone know exactly what updates are necessary and which ones are not necessary?

Thanks, Bobbie

[Nude_Lewd_Man]

It could be that you have selected to have M$ check for all updates - including software updates - which might be why there are so many updates...

Once your computer is up-to-date, then it normally slows down to only appearing once or twice a month.

Personally, I don't want any of my computers (home or work) to automatically install and restart. I always set them to download and notify, then I can choose which I want to install.

It may be true that you don't need all of the updates, but often it is down to M$ realising that there is a flaw (or a security loophole) in something, and eventually they get round to working out how to fix it and publishing it. While you may not "need" it, it might well stop/close the errors from happening.

Having said that, I don't normally have M$ check for things like driver updates, as I have (on occasion) had issues where the M$ version didn't play nicely with something else and I had to roll it back.

It is fairly difficult to give you a list of what you should, and what you should not, install when it boils down to updates... There is too much scope, too many variables, and the 'list' would be out of date in a month or two anyway...