Main Forum > General Computer Support

Windows Update error - BITS not starting - SOLVED

(1/7) > >>

LadyBird:
I’m really struggling here and desperately hoping you can help.

PC is a Dell Inspiron One, about 3.5 years old, running Windows 7 HP SP1.
Windows update checks and downloads updates but won’t install – error code 80246008 which boils down to BITS not started. Attempting to start BITS produces error code 2147024894.

So, run lots of MS fixits etc and not getting anywhere at all.
Machine currently running in clean boot mode ie. all non-MS services and scheduled tasks etc turned off including Avast.
Standard chkdsk produces ‘no errors found', the longer chkdsk c: /r made some changes but did not improve matters – log attached.

Several sfc scans over the last few days consistently produce the same two errorred items which I haven’t worked out what to do with:

2015-07-07 10:51:23, Info                  CSI    00000337 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-07 10:51:23, Info                  CSI    00000339 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-07 10:51:23, Info                  CSI    0000033b [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-07 10:51:23, Info                  CSI    0000033c [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2015-07-07 10:51:23, Info                  CSI    0000033e [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-07 10:51:23, Info                  CSI    0000033f [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"

Did a power reset, then booted in safe mode with networking, started a run of the latest 3.2.3 tweaking all-in-one.
Pre-scan produced a list of problems with Reparse Points and a couple of Environment Variables – see attached.

I guess my questions at this stage boil down to:
1.   Given my original problem of Windows Updates failing due to BITS not starting, is it likely that the Repair Tool may help?
2.   Do the SFC errors cause concern – I know some errors can be ignored, but are these of that nature?
3.   As the Reparse Points Repair and Environment Variables repair are both optional in the pre-scan, can I do any harm by running them at this stage?
Any help gratefully received.
Thank you!

Julian:
Have you tried running the windows repair tool in safe mode and run all the repairs? I believe repair number 17 should help on the bits try running the repairs and let me know what happens.
and don't forget to back up registry first lol
 :smiley:

Boggin:
I would go for creating a full external system image first.

Just to check if BITS Dependencies are started, can you go Start - type services.msc and press enter then scroll down to check that COM+ Event System and Remote Procedure Call are showing as Started and Automatic.

BITS should be showing as Auto - Delayed, although mine is showing as Demand but Started.

If yours is also showing as Demand then right click on it, select Properties and use the dropdown to change it to Auto (Delayed Start) then click on Start - Apply - OK.

Shane:
Make sure the system is clean of infections first, adwcleaner, malwarebytes and combofix will normally do well.

And yes, you can run my repairs even with the problems in the pre-scan, make sure to run them in safe mode and run them all, after you know the system is clean, make sure it does a registry backup first.

A lot of viruses remove the bits service, so while my repair will put it back, if it is still infected it will just be removed again, this is why we ned to make sure it is clean first :wink:

Shane

LadyBird:
Thanks for the comments, answers to these so far:

Julian - I'm running the repairs in safe mode (although it's taken 7 attempts with F8 this morning to hit the right spot to prevent normal startup). Not gone past the prescan yet, will be moving on shortly.

Boggin - All other services started ok and BITS is set for Auto Delayed but won't actually start

Shane - various scans already run with Avast, ADWcleaner, Kaspersky TDSSkiller and Malwarebytes, all clean (well apart from a couple of minor bits in ADWcleaner).
Done a manual reg export and created a restore point, but will also get the tool to do it's own as well.

Fingers crossed then, I'm going to carry on.
 :smiley:

Navigation

[0] Message Index

[#] Next page