Update error codes 800B0100 and 80073712... Tried EVERYTHING, HELP!

Page 1 of 2 12 LastLast

  1. Posts : 24
    windows 7 Home 64-bit
       #1

    Update error codes 800B0100 and 80073712... Tried EVERYTHING, HELP!


    Ok so I have been trying to fix these error codes 80073712 and 800B0100 for days and days on end now... I have tried pretty much everything I can think of and everything that I have read on numerous different forums and nothing at all seems to work for me...

    I have deleted all anti virus software and disabled all firewalls including windows...

    I have used Microsoft Fix it in agressive mode and normal mode...

    I have used Windowsupdate agent, Sysytem readiness update tool etc...

    I have tried manually installing these updates as well and they still fail...

    I am thinking my only option left is to upgrade windows all over again...

    I am running Windows 7 64 bit Home Premium on an Asus P5Q Pro Turbo that I have built....

    Someone pleeeeaaaaasssse heeeelllppp!!! :)
      My Computer


  2. Posts : 8,608
    Windows 7 Ultimate 32bit SP1
       #2

    See this link for error code 80073712
    Error number 80073712 - Windows Update

    800B0100
    Unable to Update error 800b0100
      My Computer


  3. Posts : 24
    windows 7 Home 64-bit
    Thread Starter
       #3

    I have tried all of those fixes and most of them only apply to Vista but I have tried them anyways and still to no avail...

    Someone please help...
      My Computer


  4. Posts : 24
    windows 7 Home 64-bit
    Thread Starter
       #4

    Here are my log files...
    Update error codes 800B0100 and 80073712...  Tried EVERYTHING, HELP! Attached Files
      My Computer


  5. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #5

    Hello and Welcome !

    Try this article and see if that works Windows Update - Reset if that fails then I'd run a Repair Install

    - Captain
      My Computer


  6. Posts : 748
    Windows 7 Professional x64 PL
       #6

    Capt.Jack Sparrow said:
    Hello and Welcome !

    Try this article and see if that works Windows Update - Reset if that fails then I'd run a Repair Install
    Resetting WU will never work if you damages in WinSxS or Packages folder and repair install is solution for cannibals,although I admitt you have seriously damages:

    Unavailable repair files:
    winsxs\manifests\amd64_mscorlib_b77a5c561934e089_6.1.7600.20717_none_3dbbc63282d93e16.manifest
    winsxs\manifests\amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.16612_none_7e53f0fd6ebdc541.manifest
    winsxs\manifests\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.20740_none_607b009642d9c626.manifest
    winsxs\manifests\wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.16612_none_88a89b4fa31e873c.manifest
    winsxs\manifests\amd64_netfx-mscordacwks_b03f5f7f11d50a3a_6.1.7600.20717_none_a126b806c861ae6e.manifest
    winsxs\manifests\amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.16619_none_363c11500fe837b6.manifest
    winsxs\manifests\msil_mscorlib.resources_b77a5c561934e089_6.1.7600.16597_en-us_66b0e132757333e5.manifest
    winsxs\manifests\amd64_netfx-sos_dll_b03f5f7f11d50a3a_6.1.7600.20717_none_89f4ffc7bc568a83.manifest
    winsxs\manifests\amd64_netfx-sos_dll_b03f5f7f11d50a3a_6.1.7600.16597_none_a0caa8fba2a7f4e4.manifest
    winsxs\manifests\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_6.1.7600.16619_none_601ad629299bb698.manifest
    winsxs\manifests\wow64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.20735_none_891f9920bc49aaed.manifest
    winsxs\manifests\amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.1.7600.16597_none_bf383e53d6b20cfc.manifest
    winsxs\manifests\amd64_microsoft-windows-security-schannel_31bf3856ad364e35_6.1.7600.20735_none_7ecaeece87e8e8f2.manifest
    winsxs\manifests\msil_mscorlib.resources_b77a5c561934e089_6.1.7600.20717_en-us_4fdb37fe8f21c984.manifest
    winsxs\manifests\amd64_microsoft-windows-smbserver-v1_31bf3856ad364e35_6.1.7600.20740_none_369c3bbd29264744.manifest
    winsxs\manifests\amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7600.20740_none_36916bd1292e6335.manifest
    winsxs\manifests\amd64_microsoft-windows-smbserver-v2_31bf3856ad364e35_6.1.7600.16619_none_363141640ff053a7.manifest
    winsxs\manifests\amd64_netfx-mscorwks_dll_b03f5f7f11d50a3a_6.1.7600.20717_none_a862951ff060a29b.manifest
    winsxs\manifests\amd64_netfx-mscordacwks_b03f5f7f11d50a3a_6.1.7600.16597_none_b7fc613aaeb318cf.manifest
    servicing\packages\Package_1_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.mum
    servicing\packages\Package_1_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.mum
    servicing\packages\Package_1_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_1_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_2_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum
    servicing\packages\Package_2_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum
    servicing\packages\Package_2_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_2_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_3_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum
    servicing\packages\Package_3_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum
    servicing\packages\Package_4_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_4_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB980436_RTM~31bf3856ad364e35~amd64~~6.1.1.2.mum
    servicing\packages\Package_for_KB980436_RTM~31bf3856ad364e35~amd64~~6.1.1.2.mum
    servicing\packages\Package_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum
    servicing\packages\Package_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.mum
    servicing\packages\Package_for_KB982214_RTM~31bf3856ad364e35~amd64~~6.1.1.3.mum
    servicing\packages\Package_for_KB982214_RTM~31bf3856ad364e35~amd64~~6.1.1.3.mum
    servicing\packages\Package_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.mum
    servicing\packages\Package_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.mum
    servicing\packages\Package_for_KB983590_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB983590_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.mum
    servicing\packages\Package_1_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.cat
    servicing\packages\Package_1_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.cat
    servicing\packages\Package_1_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_1_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_2_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat
    servicing\packages\Package_2_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat
    servicing\packages\Package_2_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_2_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_3_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat
    servicing\packages\Package_3_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat
    servicing\packages\Package_4_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_4_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB980436_RTM~31bf3856ad364e35~amd64~~6.1.1.2.cat
    servicing\packages\Package_for_KB980436_RTM~31bf3856ad364e35~amd64~~6.1.1.2.cat
    servicing\packages\Package_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat
    servicing\packages\Package_for_KB980436~31bf3856ad364e35~amd64~~6.1.1.2.cat
    servicing\packages\Package_for_KB982214_RTM~31bf3856ad364e35~amd64~~6.1.1.3.cat
    servicing\packages\Package_for_KB982214_RTM~31bf3856ad364e35~amd64~~6.1.1.3.cat
    servicing\packages\Package_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.cat
    servicing\packages\Package_for_KB982214~31bf3856ad364e35~amd64~~6.1.1.3.cat
    servicing\packages\Package_for_KB983590_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB983590_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.cat
    servicing\packages\Package_for_KB983590~31bf3856ad364e35~amd64~~6.1.1.0.cat
    I'll prepare files to replace,untill now don't do that anything.

    EDIT
    Your damages are very similar to this guy -interesting Unable to install updates because of 800B0100
    Here is instruction for you:
    I attached to post files to replace,download & unpack them anythere

    Two methods to replace these corrupted files:

    METHOD I
    1.Download attached to post Packs.zip file -in zip file is packed Packs folder -you have to unpack it and place directly on C: exactly as I show below:

    Click this bar to view the full image.Click this bar to view the full image.
    2.Boot your Windows install disk (if you don't have Windows 7 install disk instead use special recovery disk)
    Choose language>>Repair Computer>>WinRE>>command prompt

    and type:

    robocopy C:\Packs C:\ /E /IS

    press ENTER

    del C:\Windows\Logs\CBS\*.*

    press ENTER

    METHOD II (recomended if you have any another OS on your hdd)

    1.Download & unpack attached to post file anythere
    2.Run your second OS,from unpacked files choose only Windows folder and it's subfolders and copy to partition where you have corrupted system,during copying the second OS ask you "do you want to merge folders?" or likely,apply procedure.
    3.Empty C:\Windows\Logs\CBS folder

    When procedure is done run your system again and run again Readiness Tool -if log is empty that means WU should work now,if not present here new CheckSur.log file -above fix may not fix all issues at once
    Last edited by Flavius; 26 Aug 2010 at 00:00.
      My Computer


  7. Posts : 24
    windows 7 Home 64-bit
    Thread Starter
       #7

    I extracted the attatched files directly to my C: but I am not fully understanding step 2 of Method I... Everytime I boot my windows 7 disc it just says install... Im a little confused right here and now im feeling "n00bish" I appreciate everything though...
      My Computer


  8. Posts : 748
    Windows 7 Professional x64 PL
       #8

    ramrod said:
    I extracted the attatched files directly to my C: but I am not fully understanding step 2 of Method I... Everytime I boot my windows 7 disc it just says install... Im a little confused right here and now im feeling "n00bish" I appreciate everything though...
    Probably you have install disk with stripped "repair computer" option -it's possible.

    Two methods to workaround it -
    1.Burn special recovery and use it Download Windows 7 System Recovery Discs — The NeoSmart Files
    2.Harder method You cannot start Windows Recovery Environment after you start a computer by using the installation DVD that has been provided by the computer manufacturer
      My Computer


  9. Posts : 24
    windows 7 Home 64-bit
    Thread Starter
       #9

    Ok ok nevermind im sorry I did get into the repair mode command prompt but the commands would not work... Im going to try one more thing real quick....
      My Computer


  10. Posts : 24
    windows 7 Home 64-bit
    Thread Starter
       #10

    Ok when I enter robocopy C:\Packs C:\ /E /IS at prompt it says error2 0x00000002 Can't find file specified...

    That is exactly where the files are C:\Packs I dont understand....
      My Computer


 
Page 1 of 2 12 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 05:18.
Find Us