Windows Update Error 0x800b0100

Page 1 of 2 12 LastLast

  1. Posts : 47
    Windows 7 Professional 64 Bit
       #1

    Windows Update Error 0x800b0100


    Can anyone help with this please ?
    Its actually got me beat !

    Noticed that MSE failed to start.
    Then a box appeared stating that it was repairing .Net 4.5 !

    The repair completed with no change.
    A restart starts the whole procedure again.

    I then noted that Windows Update will not run, reporting the error 0x800b0100

    I followed various fixes found online, with no change.
    I ran SFC and CHKDSK with no change.
    Malwarebytes gave a clean pass.

    Getting hung up on the .Net error, I attempted its own repair procedure with no change.
    I uninstalled the .Net, restarted, and installed again.
    This failed reporting:

    Returning IDOK. INSTALLMESSAGE_ERROR [Could not write value Version to key \SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client. Verify that you have sufficient access to that key, or contact your support personnel.]

    Do I concentrate on the .Net error, or the Windows update error code ?
    Any suggestions how to proceed ?
    System restore made no difference, and I even imaged back to my full backup from a couple of days ago, but the error must have been present prior to the backup !

    If I attempt to update MSE, I get the following error below:
    This is a genuine W7 installation, that has been active for about 5 years !



    Can anyone save my sanity please.

    Thanks,
    Andy
    Attached Thumbnails Attached Thumbnails Windows Update Error 0x800b0100-capture.jpg  
      My Computer


  2. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #2

    Noel are expert on such matters will need this tutorial completed.
    It should give him information to work with.

    Windows Update Posting Instructions

    Noel is busy or very busy so just hang in.
      My Computer


  3. Posts : 47
    Windows 7 Professional 64 Bit
    Thread Starter
       #3

    On it :)
    Thanks for the reply and heads up on what to provide.

    1) SURT.
    Hmm, bad start. Downloaded to desktop, but not able to launch the application.
    It fails stating the following:

    Windows Update Error 0x800b0100-srt-install.jpg


    2) SFC scan actually ran this time, stating the following:

    Windows Update Error 0x800b0100-sfc.jpg

    3) Windows Update Error Codes

    Windows Update Error 0x800b0100-windows-update.jpg

    This system was fully updated up to this issue, and I note it now states windows updates have never been checked or installed. Not so !


    4) Log Collection
    (Hope this is correct )

    Attachment 374144


    As an additional, every time I reboot the system I get the following come up:

    Windows Update Error 0x800b0100-.net.jpg

    Many thanks.
    Andy
      My Computer


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

    SFC Found the following unfixable problems...
    Code:
    	Line 4659: 2015-10-21 22:28:06, Info                  CSI    000003a7 [SR] Repairing 12 (0x000000000000000c) components
    	Line 4660: 2015-10-21 22:28:06, Info                  CSI    000003a8 [SR] Beginning Verify and Repair transaction
    	Line 4663: 2015-10-21 22:28:06, Info                  CSI    000003aa [SR] Cannot repair member file [l:18{9}]"GWXUI.dll" of Microsoft-Windows-GWX, Version = 6.1.7601.19020, 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 4668: 2015-10-21 22:28:06, Info                  CSI    000003ad [SR] Cannot verify component files for Microsoft-Windows-SystemRestore-Main, Version = 6.1.7601.18939, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
    	Line 4671: 2015-10-21 22:28:06, Info                  CSI    000003af [SR] Cannot repair member file [l:14{7}]"VAN.dll" of Microsoft-Windows-VAN, Version = 6.1.7601.17514, 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 4674: 2015-10-21 22:28:07, Info                  CSI    000003b1 [SR] Cannot repair member file [l:20{10}]"authui.dll" of Microsoft-Windows-Authentication-AuthUI, Version = 6.1.7601.18906, 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
    It managed to fix the others.

    I'll post a fix protocol for the above errors when I can find the time!
      My Computer


  5. Posts : 47
    Windows 7 Professional 64 Bit
    Thread Starter
       #5

    Thanks for taking a look.
    I'll wait till you have some more time. :)
      My Computer


  6. Posts : 47
    Windows 7 Professional 64 Bit
    Thread Starter
       #6

    Can I cheekily bump back up.
    Thanks.

    :)
      My Computer


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

    No prob - sorry about the wait (bad weekend)

    I've uploaded a file - a01aa.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:\a01aa
    hit the enter key - if you get a 'Not Found' error try
    DIR D:\a01aa
    or
    DIR E:\a01aa

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

    XCOPY <drive>:\a01aa <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


  8. Posts : 47
    Windows 7 Professional 64 Bit
    Thread Starter
       #8

    Many thanks Noel

    Will be a job for tomorrow evening now.
    Will post back with the results.

    Andy
      My Computer


  9. Posts : 47
    Windows 7 Professional 64 Bit
    Thread Starter
       #9

    Think it all went as you instructed
    Still a mess on re-boot.

    New log attached.

    Thanks as always.
    Andy

    Attachment 374586
      My Computer


  10. Posts : 47
    Windows 7 Professional 64 Bit
    Thread Starter
       #10

    Another cheeky bump
      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 18:19.
Find Us