Have a few updates left that keeps failing, error 800B0100

Page 1 of 3 123 LastLast

  1. joestrummer
    Posts : 14
    Windows 7 Ultimate x64
       New #1

    Windows Update fails, error 800B0100


    Hello,

    I have recently managed to install Windows 7 on a new ssd in my Vaio laptop. I´ve had som problems on the way but have come this far now. I came across your site and I hope this is something you can help me with. :)

    It´s updates that I feel I have done everything to solve but they keeps failing all the time..

    Attachment 334210

    The updates in question are:
    Attachment 334342

    Swedish language pack (KB2483139)

    And 3 other optional updates
    (KB2574819)
    (KB2592687)
    (KB2830477)

    I have already download them all and tried to install them separately but that didn´t work.

    My zipped CBS folder is 44mb compressed so I zipped them separately.

    I hope you guys can help me!
    Thanks
    Last edited by joestrummer; 23 Sep 2014 at 06:24. Reason: Added Cbs log
      My Computer
    Quote Quote

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

    Sorry you've been left waiting so log! Real life gets in the way every now and then....
    Your Checksur would make very depressing reading - but luckily, all the problems seem to relate to a single failed update.
    Code:
    Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-ehome-mcplayer_31bf3856ad364e35_6.1.7601.22733_none_c22e46d4e7b0ab80.manifest
 winsxs\manifests\x86_microsoft-windows-c..ityclient.resources_31bf3856ad364e35_6.1.7601.22736_en-us_673ca97b1742f360.manifest
 winsxs\manifests\amd64_microsoft-windows-lsa.resources_31bf3856ad364e35_6.1.7601.22736_en-us_e543c265c667028a.manifest
 winsxs\manifests\amd64_microsoft-windows-c..ityclient.resources_31bf3856ad364e35_6.1.7601.22736_en-us_c35b44fecfa06496.manifest
 winsxs\manifests\amd64_microsoft-windows-w..ent-core.deployment_31bf3856ad364e35_7.6.7600.320_none_af4247f6d9404079.manifest
 winsxs\manifests\x86_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.22736_none_c9bfccdeefdbaee9.manifest
 winsxs\manifests\amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.18526_none_0467aa1173712ab7.manifest
 winsxs\manifests\wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.22736_none_4fc7759214f9fd56.manifest
 winsxs\manifests\x86_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.22736_none_c635840018fe3efe.manifest
 winsxs\manifests\amd64_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.22736_none_bc7a43a62167ba06.manifest
 winsxs\manifests\amd64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.22736_none_db4edae792566e7b.manifest
 winsxs\manifests\amd64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.22736_none_9969392bac80bf2c.manifest
 winsxs\manifests\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.22736_none_0f3b2328c0f7a594.manifest
 winsxs\manifests\amd64_microsoft-windows-security-credssp_31bf3856ad364e35_6.1.7601.22736_none_22541f83d15bb034.manifest
 winsxs\manifests\amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.22736_none_4572cb3fe0993b5b.manifest
 winsxs\manifests\amd64_microsoft-windows-ehome-mcplayer_31bf3856ad364e35_6.1.7601.18523_none_c1af780fce8af29e.manifest
 winsxs\manifests\x86_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.22736_none_d9fb080cb415c253.manifest
 winsxs\manifests\x86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.22736_none_605ba822690a48d0.manifest
 winsxs\manifests\wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.22736_none_8b06e374b96f441f.manifest
 winsxs\manifests\wow64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.22736_none_e5a38539c6b73076.manifest
 winsxs\manifests\wow64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.22736_none_a3bde37de0e18127.manifest
 winsxs\manifests\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.18526_none_0ebc5463a7d1ecb2.manifest
 winsxs\manifests\amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.18526_none_44f3fc7ac7738279.manifest
 winsxs\manifests\wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.1.7601.18526_none_4f48a6ccfbd44474.manifest
 winsxs\manifests\x86_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.22736_en-us_5c82f683d14aa0fa.manifest
 winsxs\manifests\amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7601.22736_none_80b23922850e8224.manifest
 winsxs\manifests\amd64_microsoft-windows-m..ditevtlog.resources_31bf3856ad364e35_6.1.7601.22736_en-us_b8a1920789a81230.manifest
 winsxs\manifests\amd64_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.22736_none_3619a3906c733389.manifest
 winsxs\manifests\amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.22736_none_04e678d68c96e399.manifest
 winsxs\manifests\amd64_microsoft-windows-msauditevtlog_31bf3856ad364e35_6.1.7601.22736_none_25de6862a839201f.manifest
 servicing\packages\Package_102_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_102_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_103_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_103_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_104_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_104_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_105_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_105_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_108_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_108_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_109_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_109_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_110_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_110_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_111_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_111_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2978742~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2978742~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_49_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_49_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_50_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_50_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_51_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_51_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_54_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_54_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_77_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_77_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2978742_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2978742_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2978742~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2978742~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2982378_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2982378_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_102_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_102_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_103_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_103_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_104_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_104_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_105_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_105_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_108_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_108_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_109_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_109_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_110_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_110_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_111_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_111_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_1_for_KB2978742~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_1_for_KB2978742~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_49_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_49_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_50_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_50_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_51_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_51_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_54_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_54_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_77_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_77_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2978742_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2978742_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2978742~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2978742~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2982378_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2982378_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2982378~31bf3856ad364e35~amd64~~6.1.1.0.cat
    I'll post a fix protocol when I can, so don't do anything hasty, yet!
      My Computer
    Quote Quote

  4. joestrummer
    Posts : 14
    Windows 7 Ultimate x64
    Thread Starter
       New #3

    Haha, I was just getting worried that I was forgotten

    Ah, that sounds great if its because of one single failed update! Dont worry, I´ll wait :)
      My Computer
    Quote Quote

  6. kma1717
    Posts : 105
    Windows 7 Enterprise 32 bit
       New #4

    Hi Joestrummer,

    I had a similar issue not too long ago. I went into Control Panel, Programs & Features, and View Installed Updates and looked to see if any of the updates in there were the same as the ones giving me an issue. It turned out that 2 of them were listed as already installed. I uninstalled them, rebooted, and was able to install all of my updates after that without any issues. I dont know if your issue could be the same, but it might be worth checking out. Hope this helps.

    Thanks,
    Kevin
      My Computer
    Quote Quote

  7. joestrummer
    Posts : 14
    Windows 7 Ultimate x64
    Thread Starter
       New #5

    Hello kma1717,

    I have already tried that too before I posted here.. but thanks anyway! :)
      My Computer
    Quote Quote

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

    Nothing is going to fix WU until the file errors that I posted earlier are corrected - and other errors are also corrected!

    Back when I can get to it
      My Computer
    Quote Quote

  10. joestrummer
    Posts : 14
    Windows 7 Ultimate x64
    Thread Starter
       New #7

    I look forward to it! :)
      My Computer
    Quote Quote

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

    You got lucky - I had a couple of minutes to spare...


    I've uploaded a file - jsraa.zip - to my OneDrive at Noel's OneDrive
    Please download and save it.
    Right-click on the downloaded file, and select Extract all…
    Extract to the default location - which will create a new folder jsraa in the same place.
    Open this folder - there should be two folders inside it (Manifests, and Packages)

    Copy the content of the Packages folder to the folder
    C:\Windows\Temp\CheckSur\Servicing\Packages

    And the content of the manifests folder (.manifest files) into this folder:

    C:\Windows\Temp\CheckSur\Winsxs\Manifests

    Now run the CheckSUR tool again (it may take a while)

    Post the new CheckSUR.log file, and the CheckSUR.persist.log file.
      My Computer
    Quote Quote

  12. joestrummer
    Posts : 14
    Windows 7 Ultimate x64
    Thread Starter
       New #9

    My "Servicing" and "Winsxs" folders are here:

    C:\Windows\Temp\Servicing


    C:\Windows\Temp\Winsxs

    Not in the "Checksur" folder as you mentioned... Should I still copy the content where my folders is?
    Or maybe I should move the two folders from "Temp" into the "Checksur" folder and then copy the content?
    Last edited by joestrummer; 26 Sep 2014 at 07:22.
      My Computer
    Quote Quote

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

    No- the system may not let you do it, and it could have nasty consequences.

    If the folders don't exist in the C:\Windows\TEMP\CheckSUR folder, then create that folder then just copy both folders into it and run the CheckSUR tool
      My Computer
    Quote Quote

 
Page 1 of 3 123 LastLast

  Related Discussions
Hi, I have six updates from February that I cannot get to install and I would like some help please as I haven't been able to resolve the problems after a few days of trying. I have run the SURT and SFC /scannow as per the instructions and attached them as files to this post along with the...
Updates failing error 800B0100
in Windows Updates & Activation

Hello, I've been trying to fix the error, but need some help. I tried following Microsoft's instruction on replacing the corrupt files, etc. but having a tough time. I have another computer that I can copy the files from, but I'm not even sure where and what files. I ran the system...
I'm trying to play certain Steam games, but there's an issue, and it says one way to fix it is to get the .NET Framework up to date. I just recently formatted my hard drive, and I had many updates to take care of. I've been able to fix the errors for all but 3 of the updates. Updates KB2862335 and...
I keep getting error that these updates keep failing. i have already tried the windows troubleshooting and it didnt help. i also have tried the windows update reset. i should also note that yesterday 36 failed but for some reason today when i ran the update again it accepted some of them. i have...
Hi Guys, Thought i would try my luck here again to solve yet a new issue, after having a positive experience last time i knew that this would be the place to return too. (https://www.sevenforums.com/windows-updates-activation/192471-windows-7-home-premium-x64-updates-all-failing-8007007e.html) ...
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 20:16.
Find Us