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 After installing all those updates it is much faster, it had to create the database of what it had versus the windows update location similar to what SCCM Server does but much slower of course.
Is there a program similar to nlite that downloads all patches and integrates them with your installation media? After wasting even more time on this nag I have discovered a solution that has cured the CPU usage and the massive delay waiting to access the updates at MS,I didn't take time out to see if this method has been mentioned previously on the thread,if it has my apologies in advance.
Every single "solution" that has been listed here by others -- have all failed. I can also confirm that while the computer does appear to be locked up, in fact it is not! It is unknown which update clears this up! After several updates about some installed, the issue no longer presented itself.
I for one, will not be holding my breath on Microsoft on this one. Seeing as how support ends April , they most likely will not be putting any man-hours into a fix. Until then, I'm afraid the only thing you can do is let the computer run until updates come through. The only solid solution I can offer you -- is to use some type of cloning software.
MSUpdate opens several files in this folder to check something, but I don't have any idea what the updater checks in this folder. It checks for external applications, for example office and windows desktop search. My pc is a amd On a amd and p3 its much worse taking about minutes. The current workarounds are to switch from Microsoft Update back to Windows Update, or to move the. The current workarounds are to switch from Microsoft Update back to Windows Update, or to clear the.
If you clear the MSI files you can't uninstall anything without the installer. I switched back to WindowsUpdate und searched for Office-Hotfixes seperately. With the latest office 0day exploits you can get infected by worms just by opening a word file this is why downloading all the office hotfixes by hand is not a good idea. I install every Hotfix for Office and Windows on every patchday. You need to be a member in order to leave a comment.
Sign up for a new account in our community. It's easy! Already have an account? Sign in here. Windows XP Existing user? MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Share More sharing options Followers 0. In September, reader warwagon on the Neowin support forum described the same problem -- and drew more than comments, many of which repeated the same story.
Jeff Duntemann talked about the problem in October -- and he traces its origins back to Now the November Black Tuesday patches are bringing back the same litany, and Microsoft hasn't made any moves to fix it. The source of the problem isn't hard to track down. In every instance I've seen, wuauclt. Whether Microsoft will ever deign to fix it remains a sore point.
Some people advise that you turn off Automatic Update -- I do, too, for reasons painfully obvious in the 17 epic Windows Auto Update meltdowns slideshow -- but turning off Automatic Update doesn't solve the problem. The best solution appears to be a manual update to Internet Explorer. Yes, Microsoft has messed up wuauclt. If you manually download and install the October cumulative patch, then you should be able to use Windows Update with no problems.
The precise download location varies depending on which version of IE you're using.
0コメント