mjdbb1 Posted September 4, 2013 Posted September 4, 2013 Been banging my head against the wall for a few days now, so I figured I might as well throw it out here for the experts. It's mainly to satisfy my curiosity because I can't quite figure out what's going on.I was given an old system (Dell Dimension 3000) that would be needed for a family who just needed a basic computer. I wiped the hard drive and installed a clean install of XP Pro SP3 (Dell OEM disk). Everything seemed to go fine, until I tried to access Windows Update for the newest updates. I went from having the site refuse to load at all to hanging at "Checking for the latest updates...". I followed all the usual MS troubleshooting, resetting updates, clearing update cache, etc. Even forcibly reinstalled the Windows Update Agent to no avail. I went as far as reinstalling with full retail media (again XP Pro SP3) and had the same problem.Finding this to be strange, I installed the same copy of Windows XP in a virtual machine on my main system and ran into exactly the same problem. I've installed XP with SP3 a hundred times and never had trouble with Windows Update.The best part is, I went ahead and downloaded Autopatcher and downloaded all the post-SP3 updates as of Aug. 28. After they install, with the exception of Windows Genuine Advantage Notifications (which hangs), they install just fine, and now Windows Update works.Looking through Autopatcher, there really are no updates relevant to Windows Update that would suddenly fix whatever problem is going on with Windows Update. In the past if there was an update needed to make the WU site work, it would explain that and offer the download. I've replicated this on two PCs and one virtual machine. I don't mind doing a clean install and then using Autopatcher, but it's killing me to know why that seems to be the only thing that fixes Windows Update. Anybody notice this behavior, or have any thoughts?
Guest Posted September 4, 2013 Posted September 4, 2013 (edited) Yeah, you need to install our unofficial WUA. http://www.mediafire.com/download/t1pvpp55v6aejpy/WindowsUpdateAgent7.6.7600.256-257.zip Why don't you use nLite and slipstream all the updates once you've downloaded them all with my UDC script? It includes the WUA. Edited April 7, 2014 by -X-
Guest Posted September 4, 2013 Posted September 4, 2013 Happens also in XPx64 when trying to install the Microsoft Update binaries from the website. Microsoft seems to have seriously messed something up on their servers. The only workaround I've found is to preinstall as -X- suggests.
mjdbb1 Posted September 4, 2013 Author Posted September 4, 2013 Thanks for all the info. Unfortunately, even when using the modified windows update agent you posted, the site still hangs at "Checking for the latest updates...". I think slipstreaming them like -X- mentioned is the way to go.I agree that something is definitely messed up on the MS side. However, something tells me that fixing Windows Update for XP before next April is far, far away from the front burner.
Guest Posted September 5, 2013 Posted September 5, 2013 (edited) Try running this Fix it. (Fix Its require .NET 2.0)If that doesn't work run this Fix it in aggressive mode. Edited September 5, 2013 by -X-
mjdbb1 Posted September 5, 2013 Author Posted September 5, 2013 I tried both of the fixes you suggessted (the first one I tried before) but unfortunately the site still hangs. The second one you sent (with the aggressive options) doesn't say if it found anything to fix, so I don't know exactly what it did.
Guest Posted September 5, 2013 Posted September 5, 2013 Check the version number of system32\wuweb.dll. It should be 7.6.7600.257.
mjdbb1 Posted September 6, 2013 Author Posted September 6, 2013 Just checked...it's the correct version, 7.6.7600.257.
Guest Posted September 6, 2013 Posted September 6, 2013 Hmm. Right before you go to bed. Run WU. When you wake up, see what transpired..I recently had the same problem in a VM test and added the .257 file then went to bed. When I woke up, the results where showing/
mjdbb1 Posted September 6, 2013 Author Posted September 6, 2013 Good idea. I'll let it run and see what happens. Maybe the trick will be to let it scan for update for at least 8 hours!!! I'll post back tomorrow with the results.
mjdbb1 Posted September 6, 2013 Author Posted September 6, 2013 Ok, I have an interesting result. I started the "Checking for updates..." process and let it run for about an hour. Still nothing. So I let it run overnight (about 8 hours or so) and when I came back I had this:http://i.imgur.com/wYHbN7N.jpgOn clicking yes, it prompted me to update:http://i.imgur.com/2azb8kR.jpgThis installed Genuine Advantage Validation Tool, and the package installer. Finally it took me to the update screen and offered all the expected updates. Thinking everything was now working great, I closed the window and tried again to get to Windows Update, and it's hanging at the checking for updates screen. I have some things to do so I'm planning to let it run for a few hours and see what happens. I just can't figure out what's going on now.
Guest Posted September 6, 2013 Posted September 6, 2013 (edited) I was just doing a test in a VM where I hadn't preloaded anything and it took 1 hour to complete scanning. I did load the WUA 256-257 before going to WU. Edited September 6, 2013 by -X-
mjdbb1 Posted September 7, 2013 Author Posted September 7, 2013 Wow, again if I let it sit for over an hour it works. Glad to see it's not just me, thanks for trying that out. I wonder why it takes so long just to scan.
Guest Posted September 30, 2013 Posted September 30, 2013 It should go away after the first scan on a fresh install.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now