Author Topic: Fixed - Need help repairing BITS in Windows 7 SP1 (Read 5726 times)

southieguy · « **on:** September 07, 2015, 01:08:49 pm »

Can someone please tell me how to repair BITS on my W7 SP1 system?
My symptom for needing to do so:
When trying to run Windows update, assume I have 21 to install.
I run WU on 1 selected update, and it runs successfully.
If I go back to try 1 more, the update gets in what seems to be an infinite loop.
One of the svchost.exe's (the host process for windows services) uses up to 99% of my cpu.
With taskmgr, if I kill that process I get an 800706BE error.

I have run the M'soft fixit to fix WU and Bits. No joy.
I have run the tweaking.com tool to fix windows, including the step to fix wu.

When I reboot, I can do 1 install, and then the same thing happens as described above when I try to do another update.

Any help would be much appreciated.
Dick

Shane · « **Reply #1 on:** September 12, 2015, 08:21:57 pm »

When you run my Windows Repair tool you need to make sure to run all the repairs, a lot of times things are tied together. You also need to make sure to run them in safe mode.

My Windows Repair program does put back the registry keys for the bits service and such.

There is a LOT of viruses that attack Windows update and remove services or try to break it so that any security holes cant be fixed from an update. What tools have you ran to scan your system? If you havnt ran ADWCleaner yet then give it a try as well.

Shane

southieguy · « **Reply #2 on:** September 13, 2015, 05:23:36 am »

Thank you Shane for moving this question, and for your response.
On my W7 SP1 system I run Malware Bytes Pro and BitDefender.
I have run ADWCleaner from time to time.
All 3 come up clean when I run scans.

The 1st few times I ran your tool I did run all the steps, and always in Safe Mode with Networking.

What I noticed was that I would run your tool, do a Windows Update on one sub-set of updates, and have the updates run successfully.

Then, the symptom I described (svc.exe running at 99% of my cpu) would start again.

So, I did the following: run your tool (steps 1,2, and 17); apply a subset of WU patches; run your tool (same 3 steps); and repeat these steps until all WU patches had been applied.

It was a "brute force" method; but my system runs fine now.

So, from that point of view, I think you can call this problem "fixed."

Thank you,
Dick

Shane · « **Reply #3 on:** September 14, 2015, 10:20:52 pm »

Glad you got it working, one hell of a way to go about it though lol

Shane