[SOLVED] Win7SP1 Windows Update troubleshooter says error 0x80080005 & WU hangs

[njb]

My Windows update was hanging for about a day downloading selected updates, a few MB and browsing etc was fine the whole time. I ran Windows Update troubleshooter and it said it could not fix error 0x80080005 & some 'components not registered'. IO did some searching and set background intelligent transfer service to auto, started it, and re ran the trouble shooter - it then only complained about 80080005 error. I reset update components (another MS fixit) and that emptied out all the 'available updates', so I hit 'check for updates' and that has been stuck for maybe 12 hours so far.

SFCFixit log is below (all clean). I ran SURT (too ages also - significant?) and coped the CBS dir, it's 20 MB compressed but most of it is .cab files - do you need those? I can attach / upload somewhere with or without the .cabs

I hope you can help with this.

 

[Aura]

Hi again njb :)

Let's start by getting a CheckSUR.log.

System Update Readiness Tool (SURT) - Scan
Follow the instructions below to run a scan with the System Update Readiness Tool (SURT) and provide a log;

• Download the right version of SURT for your system;
  • Your version of Windows is: Windows 7 SP1 x64
• Once downloaded, execute the installer, and go throught the installation (this process can take around 15-20 minutes);
• On completion, a log will be created in C:\Windows\Logs\CBS\CheckSUR.log;
• Attach this log in your next reply;

Alternatively, if these instructions are unclear for you, you can follow the tutorial below.

System Update Readiness Tool (SURT)

 

[njb]

Sorry for the delay getting back to you. After running SURT I tried again just a couple of updates, on a whim/desperation - they succeeded after a long time. So I tried a few more, they succeeded also. I kept going, the more I did/fewer in the list of available updates the faster the process went. There were a few isolated update failures, I ignored them and kept checking other items in the next cycle. Eventually they all seemed to succeed, at least I'm down to just a few very recent outstanding updates, most if which I don't want (e.g. W10 nagware update).

So for me the issue is 'solved' in that it seems the problem is worked around / spontaneously fixed.

Thanks for your help and attention though!

 

[Aura]

Glad to see that your issue has been solved njb! And no problem, you're welcome :)