http://www.canadiantech.info/for-techies/windows-update-not-working/
I have been going through this a lot lately. The most common feature I have found is BITS is either not started or corrupted. If is corrupted, all of my searching has not found a solution other than restore.
Check this:
- Start, All Programs
- Accessories
- Right-click on Command prompt
- Choose Run as administrator
- Y
- type net start bits
If you get a response with an error message, BITS is corrupted.
If you get a response that says starting bits or it already is, you know it is not corrupted, but WU may not be set up properly.
If the latter (not corrupted), I found the steps in this thread by Karthik Vengaloor, extremely useful
This thread essentially lists a series of commands the I have found frequently fixes WU.
- net stop wuauserv
- net stop cryptSvc
- net stop bits
- net stop msiserver
- ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
- ren C:\Windows\System32\catroot2 catroot2.old
- net start wuauserv
- net start cryptSvc
- net start bits
- net start msiserver
- pause
- Exit
This worked perfectly in 5 of the 11 cases. In the other 6, I had no choice but to do a restore to a prior date. That worked in all cases. Hint, once you restore check that net start bits command again. If it works, then proceed to update, but check that net start bits thing frequently. If you can, you need to pin down what event causes it to be corrupted.
In one case, I downloaded Microsoft’s “System Readiness tool” https://www.microsoft.com/en-ca/download/details.aspx?id=20858
In your case you need the 32 bit version. This worked in this case. https://www.microsoft.com/en-us/download/details.aspx?id=3132