Windows 7 Update error 800B0100, 9c47, 8024200D

Page 1 of 3 123 LastLast

  1. Nekozuki
    Posts : 12
    7
       New #1

    Windows 7 Update error 800B0100, 9c47, 8024200D


    Hello ive tried everything i could find about these errors, I had to split up the file because it was over 8MB (9.32)
    Im getting the following error messages

    800B0100

    9c47

    8024200D

    Here are the 2 CBS files
    Attachment 319334
    Attachment 319335

    Any help would be appreciated!

    Following files trying to be updated

    Microsoft .NET Framework 3.5 SP1 Update for Windows 7 and Windows Server 2008 R2 for x64-based Systems (KB982526)


    Security Update for Windows 7 for x64-based Systems (KB2032276)


    Security Update for Windows 7 for x64-based Systems (KB2347290)


    Security Update for Windows 7 for x64-based Systems (KB2655992)


    Security Update for Windows 7 for x64-based Systems (KB2658846)



    Security Update for Windows 7 for x64-based Systems (KB2667402)



    Security Update for Windows 7 for x64-based Systems (KB2807986)



    Security Update for Windows 7 for x64-based Systems (KB982799)


    Update for Windows 7 for x64-based Systems (KB2454826)


    Update for Windows 7 for x64-based Systems (KB2484033)



    Update for Windows 7 for x64-based Systems (KB2488113)




    Update for Windows 7 for x64-based Systems (KB2511250)




    Update for Windows 7 for x64-based Systems (KB2522422)




    Update for Windows 7 for x64-based Systems (KB974431)




    Windows 7 Service Pack 1 for x64-based Systems (KB976932)




    Windows Internet Explorer 9 for Windows 7 for x64-based Systems
    Last edited by Nekozuki; 26 May 2014 at 02:49. Reason: Added error code in title
      My Computer
    Quote Quote

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

    You have a fair number of errors in the CheckSUR...
    Code:
    Unavailable repair files:
 winsxs\manifests\amd64_wpf-presentationhostdll_31bf3856ad364e35_6.1.7600.16542_none_cc28a17e399280f3.manifest
 winsxs\manifests\x86_wpf-presentationhostdll_31bf3856ad364e35_6.1.7600.16542_none_700a05fa81350fbd.manifest
 winsxs\manifests\amd64_wpf-presentationhostexe_31bf3856ad364e35_6.1.7600.20658_none_cc96363152d1772a.manifest
 winsxs\manifests\x86_wpf-presentationhostexe_31bf3856ad364e35_6.1.7600.20658_none_70779aad9a7405f4.manifest
 winsxs\manifests\msil_presentationframework_31bf3856ad364e35_6.1.7600.16542_none_76b62ec655328f6e.manifest
 winsxs\manifests\msil_windowsbase_31bf3856ad364e35_6.1.7600.16542_none_971d833490d96bac.manifest
 winsxs\manifests\amd64_wpf-presentationhostproxy_31bf3856ad364e35_6.1.7600.16542_none_86a84af193626297.manifest
 winsxs\manifests\x86_wpf-presentationhostproxy_31bf3856ad364e35_6.1.7600.16542_none_2a89af6ddb04f161.manifest
 winsxs\manifests\amd64_wpf-presentationframework_31bf3856ad364e35_6.1.7600.16542_none_caa3904b6f89acd5.manifest
 winsxs\manifests\x86_wpf-presentationframework_31bf3856ad364e35_6.1.7600.16542_none_6e84f4c7b72c3b9f.manifest
 winsxs\manifests\amd64_presentationcore_31bf3856ad364e35_6.1.7600.16542_none_084e4684a9878ea8.manifest
 winsxs\manifests\x86_presentationcore_31bf3856ad364e35_6.1.7600.16542_none_ac2fab00f12a1d72.manifest
 winsxs\manifests\x86_presentationcore_31bf3856ad364e35_6.1.7600.20658_none_acb4799c0a4a7137.manifest
 winsxs\manifests\amd64_presentationcore_31bf3856ad364e35_6.1.7600.20658_none_08d3151fc2a7e26d.manifest
 winsxs\manifests\msil_windowsbase_31bf3856ad364e35_6.1.7600.20658_none_97a251cfa9f9bf71.manifest
 winsxs\manifests\amd64_wpf-presentationhostproxy_31bf3856ad364e35_6.1.7600.20658_none_872d198cac82b65c.manifest
 winsxs\manifests\x86_wpf-presentationhostproxy_31bf3856ad364e35_6.1.7600.20658_none_2b0e7e08f4254526.manifest
 winsxs\manifests\amd64_wpf-presentationframework_31bf3856ad364e35_6.1.7600.20658_none_cb285ee688aa009a.manifest
 winsxs\manifests\x86_wpf-presentationframework_31bf3856ad364e35_6.1.7600.20658_none_6f09c362d04c8f64.manifest
 winsxs\manifests\amd64_wpf-presentationhostexe_31bf3856ad364e35_6.1.7600.16542_none_cc11679639b12365.manifest
 winsxs\manifests\x86_wpf-presentationhostexe_31bf3856ad364e35_6.1.7600.16542_none_6ff2cc128153b22f.manifest
 winsxs\manifests\amd64_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7600.16748_none_07ebd26bfd1a9d00.manifest
 winsxs\manifests\msil_presentationframework_31bf3856ad364e35_6.1.7600.20658_none_773afd616e52e333.manifest
 winsxs\manifests\amd64_microsoft-windows-lddmcore_31bf3856ad364e35_6.1.7600.20888_none_084a2f871658ac8e.manifest
 winsxs\manifests\amd64_wpf-windowsbase_31bf3856ad364e35_6.1.7600.16542_none_b38a4129615964ab.manifest
 winsxs\manifests\x86_wpf-windowsbase_31bf3856ad364e35_6.1.7600.16542_none_576ba5a5a8fbf375.manifest
 winsxs\manifests\amd64_wpf-presentationhostdll_31bf3856ad364e35_6.1.7600.20658_none_ccad701952b2d4b8.manifest
 winsxs\manifests\x86_wpf-presentationhostdll_31bf3856ad364e35_6.1.7600.20658_none_708ed4959a556382.manifest
 winsxs\manifests\amd64_wpf-windowsbase_31bf3856ad364e35_6.1.7600.20658_none_b40f0fc47a79b870.manifest
 winsxs\manifests\x86_wpf-windowsbase_31bf3856ad364e35_6.1.7600.20658_none_57f07440c21c473a.manifest
 servicing\packages\Package_1_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_1_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_1_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_2_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_3_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_3_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_4_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_4_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_5_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_5_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_6_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_6_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_7_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_7_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.mum
 servicing\packages\Package_for_KB979900_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB979900_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_1_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_1_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_1_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_2_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_2_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_3_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_3_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_4_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_4_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_5_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_5_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_6_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_6_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_7_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_7_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_for_KB2454826_RTM~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_for_KB2454826~31bf3856ad364e35~amd64~~6.1.2.0.cat
 servicing\packages\Package_for_KB979900_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB979900_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB979900~31bf3856ad364e35~amd64~~6.1.1.0.cat
    Nothing shows in the SFC log - yet (it may do after we fix the CheckSUR errors, though)

    I'll post a fix protocol when I managed to find all the relevant files.
      My Computer
    Quote Quote

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

    I've uploaded a file - nkzaa.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 nkzaa 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

  6. Nekozuki
    Posts : 12
    7
    Thread Starter
       New #4

    Okay i did all that was advised, And several updates did go through and here is the error log now
    Errors : 8007372
    and 8024200D

    Attachment 319492

    Once again i really really do appreciate this!~
      My Computer
    Quote Quote

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

    Looks like I missed a file
    Code:
    Unavailable repair files:
 winsxs\manifests\msil_windowsbase_31bf3856ad364e35_6.1.7600.20658_none_97a251cfa9f9bf71.manifest
    I'll post a fix for that one a little later.
      My Computer
    Quote Quote

  8. Nekozuki
    Posts : 12
    7
    Thread Starter
       New #6

    Okay just let me know :)
      My Computer
    Quote Quote

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

    Oooops!
    Back soon ... I'm in the pub...
      My Computer
    Quote Quote

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

    (hic) :)

    I've uploaded a file - nkzab.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 nkzab in the same place.
    Open this folder - there should be ONE folders inside it (Manifest)

    Copy 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. Nekozuki
    Posts : 12
    7
    Thread Starter
       New #9

    error 8024200D

    CBS Logs

    Attachment 319706
      My Computer
    Quote Quote

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

    The manifest file was successfully replaced, and CheckSUR is now clear - SFC is also clear, but there are errors relating to your attempts to install the updates in the background CBS data.
    The error 8024200D
    error actually implies (and the CBS log agrees) that the updates haven't finished downloading. - but this was apparently run prior to the CheckSUR repairs.


    I suspect that the SoftwareDistribution folder is corrupt -



    Open an Elevated Command Prompt
    Run the following commands

    NET STOP WUAUSERV
    REN C:\WINDOWS\SoftwareDistribution SDOLD
    NET START WUAUSERV

    reboot
    then wait 10 minutes, and open Windows Updates, and run a Check for Updates.

    Install only the oldest update found - and reboot once installed
    then go back to Windows updates and install the others.
      My Computer
    Quote Quote

 
Page 1 of 3 123 LastLast

  Related Discussions
Windows Update error 800B0100 and 8024200D
in Windows Updates & Activation

Hi, on a new SSD hard disk, I reinstalled Windows 7. After the first 100 updates or so, updates could not longer be installed. I continuously get the error codes as in the title. Could you please help me to solve this ? Thanks in advance, Paul.
Windows Update error 800B0100 and 8024200D
in Windows Updates & Activation

Hello Im having trouble updating my windows 7 ultimate x64 I tired System Update Readiness Tool (SURT) and Sfc scan now They were all good but still having an issue. http://s10.postimg.org/cdyhz950p/Untitled.jpg
Windows Update error 800B0100 abd 8024200D
in Windows Updates & Activation

So after a clean install of Windows 7 on a new machine I have been having some bizzare problems (printers refusing to print with no errors and bluetooth devices failing to connect with no errors) and I'm hoping that the failure of these windows updates is at the root of it and hoping that I can...
Hello. I have tried my best to do everything recommended here to solve the issue of failed installments of windows updates: Fix: Windows Updates fail to install in Windows 7 | 8 Obviously, I haven't been successful. I am not very good with computers, so I would appreciate your patience as you...
Hi All, I rebuild my PC and did a clean install of Windows 7 64 Pro. I have been battling to get Windows update to work about half of the 54 important updates fail. I have tried: 1. Windows Update Readiness Tool - Didn't do anything as far as I could tell. 2. Microsoft Fix it in default and...
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 19:10.
Find Us