Error Code 80246008 when trying to download MS Updates


  1. Posts : 2
    Win7x64 SP1
       #1

    Error Code 80246008 when trying to download MS Updates


    Running Win7x64 SP1 machine (last MS updates done in June); I ran Windows update, selected the patches to install (I usually do it incrementally: Windows, IE, Office, then any .Net) and clicked install. Dialog box said it was downloading but the percentage downloaded stayed at 0%. Noticed my modem light were not flickering; checked Task Manager which showed no network activity. I had to use Task Manager to kill the task. I rebooted and tried again; this time waiting until it errored out with code 80246008.

    Checking Event Viewer, I found the following entries:

    Log Name: System
    Source: DistributedCOM logged 7/24/2015 13:21:31
    Even ID: 10010 Task Category: None
    Level Error Keywords: Classic
    User: N/A Computer: Koln
    OpCode Info

    General: The server {4991D34B-80A1-4291-83B6-3328366B9097} did not register with DCOM within the required timeout.

    followed by

    Log Name: System
    Source: Bits-Client Logged: 7/24/2015 13:21:50
    Event ID: 16392 Task Category: None
    Levl: Error Keywords:
    User: System Computer: Koln
    OpCode: Info

    General: The BITS service failed to start. Error 0x80070002.


    followed by

    Log Name: System
    Source: Service Control Manager Logged: 7/24/2105 13:21:50
    Event ID: 7024 Task Category: None
    Level: Error Keywords: Classic
    User: N/A Computer: Koln
    OpCode: Info

    General: The Background Intelligent Transfer Service service terminated with service-specific error %%-2147024894.

    Both COM+ Event System and RPC are started (automatic), but BITS is not (Automatic/Delayed). I have tried starting it manually, but get the service-specific error code-2147024894. I have tried changing it to manual, rebooting, changing it to Auto(delayed), rebooting with no success.

    I've run sfc /scannow; searching on 'cannot' finds 8 unfixable errors:

    2015-07-24 12:28:59, Info CSI 00000109 [SR] Cannot repair member file [l:22{11}]"C_10010.NLS" of Microsoft-Windows-International-CodePage-10010, Version = 6.1.7600.16385, 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-24 12:29:00, Info CSI 0000010b [SR] Cannot repair member file [l:22{11}]"C_10010.NLS" of Microsoft-Windows-International-CodePage-10010, Version = 6.1.7600.16385, 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-24 12:30:15, Info CSI 0000015e [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, 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-24 12:30:16, Info CSI 00000160 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, 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-24 12:36:19, Info CSI 0000032e [SR] Cannot repair member file [l:22{11}]"C_10010.NLS" of Microsoft-Windows-International-CodePage-10010, Version = 6.1.7600.16385, 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-24 12:36:19, Info CSI 00000330 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, 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-24 12:36:19, Info CSI 00000332 [SR] Cannot repair member file [l:22{11}]"C_10010.NLS" of Microsoft-Windows-International-CodePage-10010, Version = 6.1.7600.16385, 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-24 12:36:19, Info CSI 00000338 [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, 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

    (which I've had for a long time and it never interfered with updates previously).

    I ran the System Update Readiness tool, with the following results:

    Checking System Update Readiness.
    Binary Version 6.1.7601.22471
    Package Version 26.0
    2015-07-24 12:44

    Checking Windows Servicing Packages

    Checking Package Manifests and Catalogs

    Checking Package Watchlist

    Checking Component Watchlist

    Checking Packages

    Checking Component Store

    Summary:
    Seconds executed: 402
    No errors detected

    (My CBS zip file is 57.6 MB small, which is I believe too big to attach<g>)

    I tried your Reset_reregister_Windows-Update_Components.bat and rebooted (twice) with no joy.

    C:\ProgramData\Microsoft\Network\Downloader exists.

    I've tried MS Fix 50202 which gives the following error:

    service 'Background Intelligent Transfer Service' (BITS) failed to start. Verify that you have sufficient privileges to start sytem services.
    (I am doing this in my admin profile).

    I tried running your BITSWin7.reg via psexec, but had no File> Import to run the .reg file (?).

    Running sc query bits at the commandline yields:

    SERVICE_NAME: bits
    TYPE : 20 WIN32_SHARE_PROCESS
    STATE : 1 STOPPED
    WIN32_EXIT_CODE : 1066 <0X42a>
    SERVICE_EXIT_CODE : -2147024894 <0x80070002>
    CHECKPOINT : 0x0
    Wait_HINT : 0x0

    I hope someone will be able to help me (because I'm plum out of ideas),

    TIA

    givors1973
      My Computer


  2. Posts : 1
    Windows 7 Home Premium 32bit
       #2

    Background Intelligent Transfer service won't start - 2147024894


    I think tried almost everything you did to no avail...but alas, I found this simple registry fix (by adding a subkey). It apparently applies to XP, but at this point I was willing to try anything and adding a subkey didn't seem too risky.
    As soon as I added the subkey, the BITS started and my updates proceeded to download.

    source https://support.microsoft.com/en-us/kb/910337

    Scroll down to Troubleshooting steps and then the third one here:

    Windows could not start the Background Intelligent Transfer service on the local computer. For more information review the system event log. If this is a non-Microsoft service contact the service vendor and refer to service-specific error code -2147024894. (0x80070002)

    If you receive this error message, follow these steps:

    1. Click Start, click Run, type regedit, and then click OK.

    2. Locate the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup

    3. If the registry subkey exists, go to step 4. If the registry subkey does not exist, create the registry subkey. To do this, follow these steps:

    A. Right-click Backup Restore, point to New, and then click Key.
    B. Type FilesNotToBackup, and then press ENTER.

    4. Quit Registry Editor.

    5. Click Start, click Run, type services.msc, and then click OK.

    6. Double-click Background Intelligent Transfer Service.

    7. In the General tab, click Start.
    Last edited by texistent; 26 Jul 2015 at 19:34. Reason: accidentally pressed enter
      My Computer


  3. Posts : 2
    Win7x64 SP1
    Thread Starter
       #3

    Oh my gosh -- for want of a nail; who would have thought the lack of one valueless registry key would create such havoc?

    Many, many thanks texistent; system all updated now.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 04:48.
Find Us