Windows 7 could not search for new update code 800b0100


  1. Posts : 9
    windows home premium x64
       #1

    Windows 7 could not search for new update code 800b0100


    I had this error for months now,and i cant update my windows properly and i had try the windows update readiness tools and the fix it. and both had some weird error.
    the screenshot is below.

    I am using the Windows 7 HP 64bit


    http://www.**************/?omrg8cabto05rct
    Last edited by blitzshockz; 15 Apr 2013 at 00:56.
      My Computer


  2. Posts : 2,663
    Windows 8.1 Pro x64
       #2

    Hello blitzshockz and welcome to the forums

    Can you post the requested information please?

    Windows Update Posting Instructions

    Tom
      My Computer


  3. Posts : 9
    windows home premium x64
    Thread Starter
       #3

    i had post the attachment
      My Computer


  4. Posts : 2,663
    Windows 8.1 Pro x64
       #4

    Hi blitzshockz,

    You clearly haven't done steps one and two. I can't help you without this information. Can you do all of the steps, as previously instructed, and post the requested information:

    Windows Update Posting Instructions

    Tom
      My Computer


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

    30+MB of zipped log files??
    One of the .persist files is 250MB on its own - and was produced in less than 70 minutes!
    ... and there's still no CheckSUR results.
    Also - there's no data from 20th March to 15th April

    There's something very odd going on.
      My Computer


  6. Posts : 9
    windows home premium x64
    Thread Starter
       #6

    i cant use the system update readiness tools its says installed encounter an error
    i also do the sfc scan and i reupload the cbs.zip
    and i also tried the fixit and this happen.
    Last edited by blitzshockz; 20 Apr 2013 at 00:11.
      My Computer


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

    There's only the one error in the SFC log.
    Code:
     Line 3419: 2013-04-20 12:15:13, Info                  CSI    000002fd [SR] Repairing 1 components
     Line 3420: 2013-04-20 12:15:13, Info                  CSI    000002fe [SR] Beginning Verify and Repair transaction
     Line 3423: 2013-04-20 12:15:57, Info                  CSI    00000300 [SR] Cannot repair member file [l:38{19}]"NlsLexicons0026.dll" of Microsoft-Windows-NaturalLanguage6, 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
    I'll post a fix protocol later.
      My Computer


  8. Posts : 9
    windows home premium x64
    Thread Starter
       #8

    NoelDP said:
    There's only the one error in the SFC log.
    Code:
     Line 3419: 2013-04-20 12:15:13, Info                  CSI    000002fd [SR] Repairing 1 components
     Line 3420: 2013-04-20 12:15:13, Info                  CSI    000002fe [SR] Beginning Verify and Repair transaction
     Line 3423: 2013-04-20 12:15:57, Info                  CSI    00000300 [SR] Cannot repair member file [l:38{19}]"NlsLexicons0026.dll" of Microsoft-Windows-NaturalLanguage6, 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
    I'll post a fix protocol later.
    thanks man , i appreciate your help.
      My Computer


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

    I've uploaded a file - bszaa.zip - to my SkyDrive at Noel's SkyDrive
    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:\bszaa
    hit the enter key - if you get a 'Not Found' error try
    DIR D:\bszaa
    or
    DIR E:\bszaa


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

    XCOPY <drive>:\bszaa <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 SkyDrive Public folder, and post a new link

    Also run a new MGADiag report, and post the result.
      My Computer


 

  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 01:23.
Find Us