Error 800B0100 trying to install KB2604114, KB2676562 & KB976932 (SP1)


  1. Posts : 13
    Windows 7 Professional 64 bit
       #1

    Error 800B0100 trying to install KB2604114, KB2676562 & KB976932 (SP1)


    This thread is a spinoff of my thread in the BOSD subforum. In short I was getting BSODs after a reinstall. The BSODs seem to have been fixed for the moment, but the crashes seemed to have screwed up the updating process. I am stuck on three upgrades right now which give me Error 800B0100. One of them happens to be SP1 (KB976932). Following the instructions given to me I tried to download SP1 directly and install it, but that gave error as wel (ERROR+INVALID_PARAMETER(0X80070057)).

    SURT and the update troubleshooter have run but have not solved the problem. I also ran /SFC scannow, which found some errors it was unable to fix.

    My apologies if I should have stuck to single thread, please delete this one in that case.
      My Computer


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

    Please follow the proper Windows Update Posting Instructions and post the full results.
      My Computer


  3. Posts : 13
    Windows 7 Professional 64 bit
    Thread Starter
       #3

    Sorry, I thought I did. Looking at it again I seem to have zipped only the CBS file instead of the entire folder. My apologies.

    I had some problems uploading the entire folder because it contains a few files called CbsPersist_[Date&time].cab which are several mbs, making the file too large for a single zip. Therefore I attached them separately. One was so large I had to use a stronger compression algorithm (7-zip) to get the filesize down below 8.30 mb
      My Computer


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

    You obviously never read the instructions....

    That said, the SFC scan found 3 problems....
    Code:
     Line 3312: 2013-04-11 21:41:31, Info                  CSI    00000300 [SR] Repairing 3 components
     Line 3313: 2013-04-11 21:41:31, Info                  CSI    00000301 [SR] Beginning Verify and Repair transaction
     Line 3316: 2013-04-11 21:41:31, Info                  CSI    00000303 [SR] Cannot repair member file [l:22{11}]"wcncsvc.dll" of Microsoft-Windows-WCN-Config-Registrar, Version = 6.1.7600.16675, 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
     Line 3319: 2013-04-11 21:41:31, Info                  CSI    00000305 [SR] Cannot repair member file [l:22{11}]"wcncsvc.dll" of Microsoft-Windows-WCN-Config-Registrar, Version = 6.1.7600.16675, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3322: 2013-04-11 21:41:31, Info                  CSI    00000307 [SR] Cannot repair member file [l:20{10}]"dmdlgs.dll" of Microsoft-Windows-DiskManagement, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    The results of such corruption are unpredictable....
    there'a also....
    Code:
    Line 2901: 2013-04-12 19:24:51, Error                 CBS    Failed to verify if catalog file \\?\C:\Windows\SoftwareDistribution\Download\48ffb769a0e6fdd59056da3fe7133cee\update.cat is valid. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
     Line 2903: 2013-04-12 19:24:51, Error                 CBS    Failed to create internal package [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
     Line 2907: 2013-04-12 19:24:53, Error                 CBS    Failed to verify if catalog file \\?\C:\Windows\SoftwareDistribution\Download\cf513228d02f73db32118e4b5e2edb92\update.cat is valid. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
     Line 2909: 2013-04-12 19:24:53, Error                 CBS    Failed to create internal package [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
    I'll see what I can do in terms of a repair protocol, and post it later.
      My Computer


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

    Don't bother, the situation has changed drastically. Earlier today my computer bluescreened suddenly and refused to boot windows after that. In light of the recent update problems I decided to reinstall with a windows 7 .iso with SP1 preinstalled, which I downloaded from the official Microsoft distribution system a couple days ago (if only I had know earlier that MS provides downloads of win 7 installation disks).

    Long story short, I now have windows 7 reinstalled and almost fully updated. However, I get an error (80070057) on two remaining updates. Following the posting instructions (like I did the first time ), I ran SURT. However, I got a bluescreen (SYSTEM SERVICE EXCEPTION) during the run. This was the first bluescreen since my reinstall. I ran SURT again, this time without crashing. I then ran SFC /SCANNOW, which told me at 47% "Windows Resource Protection could not perform the requested operation". I ran it again, only to have it give the same message at 62%.

    For size reasons I had to split off one of the CbsPersists files from the main zip again.
      My Computer


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

    That sounds lie you may have hardware problems
    RAM and HD problems are the most likely.

    The CheckSUR log contains only the 'expected' errors from the installation of IE10
    The SFC log chows the following errors
    Run 1
    Code:
     Line 3312: 2013-04-11 21:41:31, Info                  CSI    00000300 [SR] Repairing 3 components
     Line 3313: 2013-04-11 21:41:31, Info                  CSI    00000301 [SR] Beginning Verify and Repair transaction
     Line 3316: 2013-04-11 21:41:31, Info                  CSI    00000303 [SR] Cannot repair member file [l:22{11}]"wcncsvc.dll" of Microsoft-Windows-WCN-Config-Registrar, Version = 6.1.7600.16675, 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
     Line 3319: 2013-04-11 21:41:31, Info                  CSI    00000305 [SR] Cannot repair member file [l:22{11}]"wcncsvc.dll" of Microsoft-Windows-WCN-Config-Registrar, Version = 6.1.7600.16675, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
     Line 3322: 2013-04-11 21:41:31, Info                  CSI    00000307 [SR] Cannot repair member file [l:20{10}]"dmdlgs.dll" of Microsoft-Windows-DiskManagement, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    Run 2/3
    Code:
     Line 81782: 2013-04-15 01:00:46, Info                  CSI    000001c3 [SR] Beginning Verify and Repair transaction
     Line 81785: 2013-04-15 01:00:46, Info                  CSI    000001c5 [SR] Cannot repair member file [l:26{13}]"calibrili.ttf" of Microsoft-Windows-Font-TrueType-Calibri, Version = 6.1.7601.17959, 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
     Line 81788: 2013-04-15 01:00:50, Info                  CSI    000001c7 [SR] Cannot repair member file [l:26{13}]"calibrili.ttf" of Microsoft-Windows-Font-TrueType-Calibri, Version = 6.1.7601.17959, 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

    The remainder of the CBS log also shows the following problem (and a couple of other similar ones)
    Code:
     2013-04-15 00:54:20, Info                  CSI    00000004 Processing Namespace uninstall for [wcm://Microsoft-Windows-shell32?version=6.1.7601.17514&language=neutral&processorArchitecture=amd64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers]
    2013-04-15 00:54:21, Info                  CSI    00000005 done
    Line 1159: 2013-04-15 00:54:21, Error                 CSI    00000010@2013/4/14:22:54:21.186 (F) d:\win7sp1_gdr\base\xml\udom_microdom.cpp(4111): Error STATUS_INVALID_PARAMETER originated in function MicrodomImplementation::CStringpoolCache::FindString expression: StringId < m_Entries.Length
     Line 1161: 2013-04-15 00:54:22, Error                 CSI    00000011 (F) 80070057 [Warning,Facility=FACILITY_NTWIN32,Code=87] #316695# from CSettingsInstaller::ProcessComponentChange(...)[gle=0x90070057]
     Line 1162: 2013-04-15 00:54:22, Error                 CSI    00000012 (F) 80070057 [Warning,Facility=FACILITY_NTWIN32,Code=87] #315634# from PrimitiveInstaller::CCoordinator::ProcessChange(Change 6.1.7601.17514 -> 6.1.7601.17859 for Microsoft-Windows-shell32, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral)[gle=0x90070057]
     Line 1165: 2013-04-15 00:54:22, Error                 CSI    00000013 (F) 80070057 [Warning,Facility=FACILITY_NTWIN32,Code=87] #4123# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0x90070057]
     Line 1166: 2013-04-15 00:54:22, Error                 CSI    00000014 (F) 80070057 [Warning,Facility=FACILITY_NTWIN32,Code=87] #4122# from CCSDirectTransaction::PrepareForCommit(...)[gle=0x90070057]
     Line 1167: 2013-04-15 00:54:22, Error                 CSI    00000015 (F) 80070057 [Warning,Facility=FACILITY_NTWIN32,Code=87] #4121# from CCSDirectTransaction::ExamineTransaction(...)[gle=0x90070057]
     Line 1168: 2013-04-15 00:54:22, Error                 CSI    00000016 (F) 80070057 [Warning,Facility=FACILITY_NTWIN32,Code=87] #4120# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0x90070057]
     
    ...and finishes on the following couple of errors....
    
    Code:
     Line 82923: 2013-04-15 01:01:44, Error                 CSI    0000028f@2013/4/14:23:01:44.717 (F) d:\win7sp1_gdr\base\wcp\cdf\cdf_cdfapi.cpp(936): Error STATUS_SXS_INVALID_ACTCTXDATA_FORMAT originated in function RtlCreateCdfEx expression: (null)
     Line 84964: 2013-04-15 01:06:22, Error                 CSI    00000456@2013/4/14:23:06:22.271 (F) d:\win7sp1_gdr\base\xml\udom_microdom.cpp(4111): Error STATUS_INVALID_PARAMETER originated in function MicrodomImplementation::CStringpoolCache::FindString expression: StringId < m_Entries.Length
    I freely admit to having no idea how to deal with them :( I would suggest starting by checking the RAM and then the hard drive for problems. Download MemTest86+ from PassMark MemTest86 - Memory Diagnostic Tool - create the boot media, and run at least 6 passes, See what it reports.
      My Computer


  7. Posts : 13
    Windows 7 Professional 64 bit
    Thread Starter
       #7

    I ran Memtest 86+ (not Memtest86) a couple days ago (just before starting this thread), as instructed by Northernsoul555 in the other thread. It ran for 10 passes without finding any errors. I also ran the Intel SSD diagnostic tool and CKDSK slightly more than a week ago and I will run them again this evening/night.

    I assume your advice is to fix the underlying problem and then reinstall windows to deal with the update issues? Would it, with regards to finding the problem, be better to continue using the current installation or to reinstall the SP1 version and disable updates for the moment?
      My Computer


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

    Check the Hash values of the SP1 ISO you downloaded, then use that, assuming it's OK.
    Generally, I would tend to install drivers first, then updates (installing the updates in batches).
      My Computer


  9. Posts : 13
    Windows 7 Professional 64 bit
    Thread Starter
       #9

    I reinstalled with the SP1 iso and tried to install updates. Got several errors along the way, but windows reports all updates are succesfully installed after trying it a few times.

    I am gonna mark this as resolved and return to the original BSOD thread. Thank you very much for your help.
      My Computer


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

    You're welcome - good luck!
      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 11:28.
Find Us