Windows 7 can not update: Error code 800B0100

Page 3 of 7 FirstFirst 12345 ... LastLast

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

    Here's what appears to be the error from the CBS log...
    Code:
    2015-03-31 19:01:48, Info                  CBS    Startup: Processing advanced operation queue, startupPhase: 0
    2015-03-31 19:01:48, Info                  CSI    00000005 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 0000000a, progress = NULL, phase = 0, pdwDisposition = @0xf9f810
    2015-03-31 19:01:49, Info                  CSI    00000006 ResolvePendingTransactions called with primitive operations still pending (call 1)
    2015-03-31 19:01:49, Error                 CBS    Startup: Failed to process advanced operation queue, startupPhase: 0.  Primitives are still pending. [HRESULT = 0x80004005 - E_FAIL]
    2015-03-31 19:01:49, Info                  CBS    Setting ExecuteState key to: CbsExecuteStatePrimitives
    2015-03-31 19:01:49, Error                 CBS    Startup: POQ has not been processed yet, aborting startup processing.  Startup processing will be attempted again. [HRESULT = 0x80004004 - E_ABORT]
    2015-03-31 19:01:49, Info                  CBS    Current global progress. Current: 0, Limit: 1, ExecuteState: CbsExecuteStatePrimitives
    2015-03-31 19:01:49, Info                  CBS    Previous global progress. Current: 0, Limit: 1, ExecuteState: ExecuteStateNone
    2015-03-31 19:01:49, Info                  CBS    Clearing HangDetect value
    2015-03-31 19:01:49, Info                  CBS    Saved last global progress. Current: 0, Limit: 1, ExecuteState: CbsExecuteStatePrimitives
    2015-03-31 19:01:49, Info                  CBS    Startup: received notification that startup processing completed, allowing user to logon
    2015-03-31 19:01:49, Info                  CBS    Startup: Processing complete. [HRESULT = 0x80004004 - E_ABORT]
    2015-03-31 19:01:49, Info                  CBS    Restored system sleep block state: 0x80000000
    It's not an error I recall ever seeing before - but since it deals with pending operations. let's look at the possibilities.

    Please open an Elevated Command Prompt, and run the following commands...

    MD %userprofile%\desktop\pendlogs
    Copy C:\Windows\winsxs\pending*.* %userprofile%\desktop\pendlogs


    They'll create a folder on the desktop called 'pendlogs' - zip the folder up and post the zipped file.
      My Computer


  2. Posts : 33
    Windows 7 Home Premium x64
    Thread Starter
       #22

    Here you go, I attached the file.
    Windows 7 can not update: Error code 800B0100 Attached Files
      My Computer


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

    Hmm, that's rather older than I was expecting to see - 2013!
    Let's start again, with a new set of logs - please run CheckSUR and SFC /SCANNOW again, and post the new CBS folder - also post the C:\Windows\windowsupdate.log file.
      My Computer


  4. Posts : 33
    Windows 7 Home Premium x64
    Thread Starter
       #24

    So does dat mean that a file got corrupted back in 2013?

    Anyway, here are the log files.
      My Computer


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

    I don't think so - it's more likely to be a result of the errors I just found in the SFC log
    Code:
     Line 11826: 2015-04-30 18:25:56, Info                  CSI    0000034b [SR] Repairing 3 components
     Line 11827: 2015-04-30 18:25:56, Info                  CSI    0000034c [SR] Beginning Verify and Repair transaction
     Line 11830: 2015-04-30 18:25:56, Info                  CSI    0000034e [SR] Cannot repair member file [l:50{25}]"msmpeg2vdec-ppdlic.xrm-ms" of Microsoft-Windows-MSMPEG2VDEC, Version = 7.1.7601.18519, 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 11833: 2015-04-30 18:25:56, Info                  CSI    00000350 [SR] Cannot repair member file [l:30{15}]"msmpeg2vdec.dll" of Microsoft-Windows-MSMPEG2VDEC, Version = 7.1.7601.18519, 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 11837: 2015-04-30 18:25:56, Info                  CSI    00000352 [SR] Cannot repair member file [l:54{27}]"System.Design.resources.dll" of System.Design.resources, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"nl-nl", VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    I'll post a fix in the morning - t's past my bedtime now.
      My Computer


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

    Hmmm - it seems strange - the System.Design.resources.dll doesn't exist in my system winsxs folder.
    It seems it only exists 'in theory' in the en-us install. I managed to pull it from the update instead...


    I've uploaded a file - tt1ab.zip - to my OneDrive at Noel's OneDrive
    Please download and save it.

    Right-click on the saved file and select Extract all...
    Change the target to C:\ and click on Extract
    Close all windows (it would be a good idea to print these instructions!)

    Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
    Pick that
    You'll have to log in with your username and password.

    Pick the option to use a Command Prompt
    At the prompt type
    DIR C:\tt1ab
    hit the enter key - if you get a 'Not Found' error try
    DIR D:\tt1ab
    or
    DIR E:\tt1ab



    The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



    XCOPY <drive>:\tt1ab <drive>:\windows\winsxs /y /i /s /v /h



    (e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



    run the command (it should take almost no time) and when the prompt returns, type
    EXIT
    and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

    Now run SFC /SCANNOW in an Elevated Command Prompt
    then reboot and upload the new CBS.log file to your reply
      My Computer


  7. Posts : 33
    Windows 7 Home Premium x64
    Thread Starter
       #27

    I tried to follow the steps you listed.

    First of all, I had trouble finding the C:\ disk. apparently this was X:\ in the command prompt, but half of my maps and files in the C:\ directory were not listed in the command screen, which I thought was interesting. (the directory from the extracted ZIP was also not listed, so I moved it to another disk from were I could find it and tried to copy it)

    Anyway, I found the right disk and the directory, but when I gave the "XCOPY D:\\tt1ab X:\windows\winsxs /y /i /s /v /h" command, I received this in return:

    "Unvalid number of parameters"

    EDIT: nevermind, I worked it out. I added quotation marks and it worked. I attached the CBS.log file to this post. I zipped the log file because it exceeded the size limit.
    Last edited by toast01; 04 May 2015 at 15:14.
      My Computer


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

    Here's the errors from the latest SFC scan...
    Code:
     Line 26700: 2015-05-04 22:08:43, Info                  CSI    0000034b [SR] Repairing 3 components
     Line 26701: 2015-05-04 22:08:43, Info                  CSI    0000034c [SR] Beginning Verify and Repair transaction
     Line 26704: 2015-05-04 22:08:43, Info                  CSI    0000034e [SR] Cannot repair member file [l:50{25}]"msmpeg2vdec-ppdlic.xrm-ms" of Microsoft-Windows-MSMPEG2VDEC, Version = 7.1.7601.18519, 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 26707: 2015-05-04 22:08:43, Info                  CSI    00000350 [SR] Cannot repair member file [l:30{15}]"msmpeg2vdec.dll" of Microsoft-Windows-MSMPEG2VDEC, Version = 7.1.7601.18519, 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 26711: 2015-05-04 22:08:43, Info                  CSI    00000352 [SR] Cannot repair member file [l:54{27}]"System.Design.resources.dll" of System.Design.resources, Version = 6.1.7601.18523, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture = [l:10{5}]"nl-nl", VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    It looks like none of the earlier errors have been fixed

    I'll have to review this tomorrow - too late tonight!
      My Computer


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

    toast01 said:
    Anyway, I found the right disk and the directory, but when I gave the "XCOPY D:\\tt1ab X:\windows\winsxs /y /i /s /v /h" command, I received this in return:
    The problem there was that you appear to have inserted an extra backslash (\) into the command, and also used the wrong drive letter for the Windows\winsxs folder - it should have been simply

    XCOPY D:\tt1ab D:\windows\winsxs /y /i /s /v /h
      My Computer


  10. Posts : 33
    Windows 7 Home Premium x64
    Thread Starter
       #30

    mmh, I did read a confirmation about three files being copied, so I think I didn't insert the double slashback in the command prompt.

    Anyway, I copied the files again, making pictures so you can spot any mistake I may have made (It's been a while since I used commands in windows).

    First of all: I can't seem to locate the tt1ab directory, while I am sure this directory is positioned on my C:\ drive. (I just now realize there are a lot more directories missing in the command screen (figure 2 vs figure 1).. that was pretty stupid)

    Windows 7 can not update: Error code 800B0100-knipsel2.png
    [Figure 1: "tt1ab" directory on the C:\ drive]

    Windows 7 can not update: Error code 800B0100-knipsel1.png
    [Figure 2: "tt1ab" directory missing in which I assumed was the C:\ drive because of the "windows" directory (I did a DIR command on about every letter from A to Z, and none of the outputs were exactly like my C:\ drive)

    So, I moved the tt1ab directory to another harddisk, which I did find in the command prompt:

    Windows 7 can not update: Error code 800B0100-knipsel3.png
    [figure 3: "tt1ab" directory on the D:\ drive]

    Windows 7 can not update: Error code 800B0100-knipsel4.png
    [figure 4: "tt1ab" directory in the command prompt]

    I copied the files, and received a conformation:
    Windows 7 can not update: Error code 800B0100-knipsel5.png
    [figure 5: second-to-bottom line translates to: "3 file(s) copied"]

    However, one interesting thing I did nót notice yesterday was the output the SFC scan gave me:
    Windows 7 can not update: Error code 800B0100-knipsel6.png
    [figure 6: translation: "damaged/corrupt files were found, but these could not all be recovered. Details are given in CBS.Log windir\logs blabla..."]
    Yesterday I did not bother to read the feedback, so I think the SFC scan I did yesterday gave the same result. I attached the new CBS.Log file this reply

    If someone would ask me, I think something went wrong with copying, maybe I copied to the wrong disk? I assumed the C:\ drive would correspond with X:\, because there was a windows file, and the default path started in the X:\ drive (see top line figure 2).

    Sorry for the long and pic-heavy reply. And thanks again for your time and effort!
      My Computer


 
Page 3 of 7 FirstFirst 12345 ... LastLast

  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 18:07.
Find Us