Windows Update, error code 800736B3

Page 2 of 2 FirstFirst 12

  1. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #11

    There's a few more files referenced now...
    Code:
    Line 22610: 2014-06-16 14:19:42, Info                  CSI    00000244 [SR] Repairing 10 (0x000000000000000a) components
     Line 22611: 2014-06-16 14:19:42, Info                  CSI    00000245 [SR] Beginning Verify and Repair transaction
     Line 22612: 2014-06-16 14:19:44, Info                  CSI    00000246 [SR] Cannot repair member file [l:102{51}]"Microsoft-Windows-IIS-HTTPLogging-Deployment-DL.man" of Microsoft-Windows-Migration-DownlevelManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
     Line 22613: 2014-06-16 14:19:44, Info                  CSI    00000247 [SR] Cannot repair member file [l:76{38}]"MediaServer-Multicast-Migration-DL.man" of Microsoft-Windows-Migration-DownlevelManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
     Line 22614: 2014-06-16 14:19:44, Info                  CSI    00000248 [SR] Cannot repair member file [l:100{50}]"Microsoft-Windows-IIS-IPSecurity-Deployment-DL.man" of Microsoft-Windows-Migration-DownlevelManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
     Line 22615: 2014-06-16 14:19:44, Info                  CSI    00000249 [SR] Cannot repair member file [l:30{15}]"winlogon-DL.man" of Microsoft-Windows-Migration-DownlevelManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
     Line 22616: 2014-06-16 14:19:44, Info                  CSI    0000024a [SR] Cannot repair member file [l:24{12}]"msdtcstp.dll" of Microsoft-Windows-Migration-DownlevelManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
     Line 22617: 2014-06-16 14:19:44, Info                  CSI    0000024b [SR] Cannot repair member file [l:44{22}]"TabletPCJournal-DL.man" of Microsoft-Windows-Migration-DownlevelManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
     Line 22618: 2014-06-16 14:19:44, Info                  CSI    0000024c [SR] Cannot repair member file [l:32{16}]"odbc32dll-DL.man" of Microsoft-Windows-Migration-DownlevelManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
     Line 22619: 2014-06-16 14:19:44, Info                  CSI    0000024d [SR] Cannot repair member file [l:122{61}]"Microsoft-Windows-IIS-WindowsAuthentication-Deployment-DL.man" of Microsoft-Windows-Migration-DownlevelManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
     Line 22620: 2014-06-16 14:19:44, Info                  CSI    0000024e [SR] Cannot repair member file [l:50{25}]"ADSI-LDAP-Provider-DL.man" of Microsoft-Windows-Migration-DownlevelManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
     Line 22621: 2014-06-16 14:19:44, Info                  CSI    0000024f [SR] Cannot repair member file [l:22{11}]"bitsmig.dll" of Microsoft-Windows-Migration-DownlevelManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
     Line 22622: 2014-06-16 14:19:44, Info                  CSI    00000250 [SR] Cannot repair member file [l:22{11}]"HTTP-DL.man" of Microsoft-Windows-Migration-DownlevelManifests, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
     Line 22625: 2014-06-16 14:19:46, Info                  CSI    00000252 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBP_303.DLL" of prnca00b.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 22628: 2014-06-16 14:19:46, Info                  CSI    00000254 [SR] Cannot repair member file [l:24{12}]"CNFMP8RR.ICC" of wiaca00f.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
    This is worrying, as we not only haven't fixed anything apart from two of the files, but new corruptions are appearing.
    This usually means one of three things.
    1) you have a hardware error - either RAM or Hard drive are the favourites here
    2) You have malware which is attacking the system
    3) something else (!) - including any error from me...


    As far as I can tell, I didn't make any cockups.

    Let's check the disk integrity first...


    Please run a full CHKDSK scan....
    Click on Start > All Programs > Accessories
    Right-click on the Command Prompt entry
    Select Run as Administrator and accept the UAC prompt - the Elevated Command Prompt window should pop up.
    At the Command prompt, type
    CHKDSK C: /R
    and hit the Enter key.
    You will be told that the drive is locked, and the CHKDSK will run at the next boot - hit the Y key, and then reboot.
    The CHKDSK will take a few hours depending on the size of the drive, so be patient!
    After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot).

    Then I need to see your Event logs...


    Open Event Viewer
    click on the Windows logs entry in the left pane to expand it.
    Now click on the Application entry - wait while it loads.
    Click on 'File' in the menu bar and select Save...
    Save the file as Appevt.evtx
    Repeat for the System log
    then zip both, and upload them.
      My Computer


  2. Posts : 10
    Windows 7 Professional 64bit
    Thread Starter
       #12

    here it is.
      My Computer


  3. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #13

    I can see no sign of the CHKDSK I asked you to run?

    There are a LOT of errors in both logs - and a number of crashes.
    I'm going to ask for help with the crashes, as I don't think there's much point attempting to fix the Update problems while the system is unstable.

    Please follow the Blue Screen of Death (BSOD) Posting Instructions and upload all the requested data so they have something to work with.
      My Computer


  4. Posts : 10
    Windows 7 Professional 64bit
    Thread Starter
       #14

    So i am going to try to solve BSOD problem first and then if that problem was solved then i will comminicate with you for windows update problem, right?
      My Computer


  5. Posts : 10
    Windows 7 Professional 64bit
    Thread Starter
       #15

    I did CHKDSK thing and i tought CHKDSK log file in what i sent to you.
      My Computer


  6. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #16

    It should have been in the Applications log - but there's no entry that I can find
      My Computer


  7. Posts : 10
    Windows 7 Professional 64bit
    Thread Starter
       #17

    should i do that procedure again?
      My Computer


  8. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #18

    Yep - The ones in post #11 are the relevant ones - take note of any error messages you get!
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 21:44.
Find Us