Windows xp automatic updates high cpu

->>>> Click Here to Download <<<<<<<-

For fun i just let the computer sit to see how long it would take. So finally I just killed it and shut the computer off because he was going to get a new one anyway. This was an old Celeron from or earlier. Food for though, imagine how many XP machines are out there are having this exact problem, rendering the computer unusable.

To warwagon, my Dell computer is over 9 years old July and the XP update workaround worked successfully for me. I had this problem for a while, but not on XP on Windows 7. All fixed now, i just disabled a service in the Task Manager Unable to think which one sorry. Hi I just wanted to say, at our factory we have a bunch of machines using XP. We will continue to be using XP after April '14 and I have been repairing some of our old machines just to be used for basic terminals.

Anyway this bug was driving me crazy to be honest. I had all the updates but this one I almost gave up until I found something that solved it. By clicking wganotifypackageinner.

Not by using wgasetup. Can you maybe detail this a bit more? My WU is now also stuck at trying to finalize the installation of WGA - right at "running processes after install" it just hangs there. Are you saying you let it hang there and ran wganotifypackageinner. Or did you reboot, ran wganotifypackageinner. I did not use the windows update method otherwise you will be hung. You will also hang if you run the above KB manually and click next to continue. When you first run it, it will extract the installation into the temporary directory.

So do it on a reboot, if you are hung you have to kill a few tasks in your task manager including the KB install executable. So yes I ran the wganotifypackaginner manually do not use the other one or it will get stuck on the 'running processes after install'.

When I ran the wganotifypackaginner it does the installation without hanging, you do not need to use the windows update at all for this method. I noticed almost immediately the installer got by the hang part and began doing the proper installation right away. This has been happening for years, I'm not surprised. I tried updating Server with SP2 to the latest updates with IE6 installed and it took over 52 hours for it to find the updates to install For IE6 go here. IE7 is here. And IE8 is here. You would think that simply upgrading to the latest version of IE would solve the problem, but it doesn't.

You have to manually download and apply the patch for your version of IE. Will Microsoft go in and fix wuauclt. I wouldn't bet on it. Get the first word on what the important tech news really means with the InfoWorld Tech Watch blog. Here's a pix of what it looks like. If it's not listed, please proceed as follows to register the BITS service.

Double click it and then on the General tab, click the Start button to try and start the service manually. This is just a test to ensure that it's working correctly. In reply to Xircal's post on November 21, I am leaving Microsoft Automatic Updating turned off until Microsoft gets its act together.

In reply to RogerCowley's post on November 21, I am leaving Microsoft Automatic Updating turned off until Microsoft gets its act together Hi Roger, There are only four posts in this thread and your name doesn't appear in any of them.

Perhaps you responded in the the wrong thread? You got an answer that is a confirmed correct solution verified by many people. It is definitely not any joke at all. For the part about Microsoft needing to get its act together yeah there's that too could be a more lasting solution, but it would be a surprise if there is any upgrade of IE8 to something having functionality like Firefox.

That would be giving XP a new lease on life when it is absolutely clear that the Microsoft agenda is forcing early retirement of XP through scripting induced freezes or blocking of IE8 at every website globally which is part of the IT "microsoft partners" conglomerate implementation of a "kill XP via non support of IE8" nearly unanimous internet protocol.

Well, I have another fresh install doing the same thing. The user has been "Administrator" since installation. The changing the Automatic updates did not help. Disabling the services did not help either. The file causing the problem is "ntdll. The problem item in Widows is ntdll. I have some screen shots of Process Explorers findings however, I do not know how or even if we can post them. If anyone cares I can post them to my web site. Hello All! I finally "corrected?

I am embarrassed to say it but, I can't for the life of me figure out why that worked! I do not know if that will work for any of you either but, it is worth the try!

I have experienced no problems since stopping that service! Good Luck and Happy New Year! I'll be giving this a try tomorrow. Did it help with the Outlook issue too? I have not resolved this issue and had one client call today with the same problem and a fellow tech in a nearby town call this evening Jan 3rd with the same issue.

I too had the same problem with svchost consuming all my cpu cycles. Through a process of trial and error, I appear to have fixed it by disabling Automatic Updates. Changing to "Just notify me" did not work.

I suggest anyone experiencing this problem stop the Windows Update service I immediately saw the svchost process disappear and an increase in CPU idle time.

If the machine is part of a network,log on as admin,delete the users profile and then get the user to log in as this refresh's the profile and the system.