windows update error code

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 7 Ultimate 32 bit
       #1

    windows update error code


    hi i have got a windows 7 32 bit pc that had a virus on a few months ago managed to get rid of the virus but now i am getting error codes 800b0100 the updates are security updates i have check the log that i have uploaded here and there are 30 corrupt files on my system and i have no idea how to fix them any help would be great thanks in advance

    heres log Attachment 252207

    i have tried many other fixes but none have worked am at a loss
      My Computer


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

    You appear to be using AVG? what other security software do you have installed?
    here are a number of problems showing in the CheckSUR report....
    Code:
    Unavailable repair files:
     servicing\packages\Package_1_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_1_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_2_for_KB2753842~31bf3856ad364e35~x86~~6.1.1.2.mum
     servicing\packages\Package_2_for_KB2753842~31bf3856ad364e35~x86~~6.1.1.2.mum
     servicing\packages\Package_37_for_KB2758857~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_37_for_KB2758857~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_37_for_KB2779562~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_37_for_KB2779562~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_38_for_KB2758857~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_38_for_KB2758857~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_38_for_KB2779562~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_38_for_KB2779562~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_39_for_KB2758857~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_39_for_KB2758857~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_for_KB2753842_SP1~31bf3856ad364e35~x86~~6.1.1.2.mum
     servicing\packages\Package_for_KB2753842_SP1~31bf3856ad364e35~x86~~6.1.1.2.mum
     servicing\packages\Package_for_KB2753842~31bf3856ad364e35~x86~~6.1.1.2.mum
     servicing\packages\Package_for_KB2753842~31bf3856ad364e35~x86~~6.1.1.2.mum
     servicing\packages\Package_for_KB2758857_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_for_KB2758857_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_for_KB2758857~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_for_KB2758857~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_for_KB2770660_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_for_KB2770660_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.mum
     servicing\packages\Package_for_KB2779562_SP1~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_for_KB2779562_SP1~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_for_KB2779562~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_for_KB2779562~31bf3856ad364e35~x86~~6.1.1.1.mum
     servicing\packages\Package_1_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_1_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_2_for_KB2753842~31bf3856ad364e35~x86~~6.1.1.2.cat
     servicing\packages\Package_2_for_KB2753842~31bf3856ad364e35~x86~~6.1.1.2.cat
     servicing\packages\Package_37_for_KB2758857~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_37_for_KB2758857~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_37_for_KB2779562~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_37_for_KB2779562~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_38_for_KB2758857~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_38_for_KB2758857~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_38_for_KB2779562~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_38_for_KB2779562~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_39_for_KB2758857~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_39_for_KB2758857~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_for_KB2753842_SP1~31bf3856ad364e35~x86~~6.1.1.2.cat
     servicing\packages\Package_for_KB2753842_SP1~31bf3856ad364e35~x86~~6.1.1.2.cat
     servicing\packages\Package_for_KB2753842~31bf3856ad364e35~x86~~6.1.1.2.cat
     servicing\packages\Package_for_KB2753842~31bf3856ad364e35~x86~~6.1.1.2.cat
     servicing\packages\Package_for_KB2758857_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_for_KB2758857_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_for_KB2758857~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_for_KB2758857~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_for_KB2770660_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_for_KB2770660_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.cat
     servicing\packages\Package_for_KB2779562_SP1~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_for_KB2779562_SP1~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_for_KB2779562~31bf3856ad364e35~x86~~6.1.1.1.cat
     servicing\packages\Package_for_KB2779562~31bf3856ad364e35~x86~~6.1.1.1.cat
    The CBS log isn't complete - it cuts off before the end of the scan (what is there looks OK). Please reboot and post just the CBS.log file while I sort out a fix protocol for the CheckSUR errors.
      My Computer


  3. Posts : 7
    Windows 7 Ultimate 32 bit
    Thread Starter
       #3

    ok am running scan now will post when done thanks for the fast replies i am only running avg i dont have any other security programs
      My Computer


  4. Posts : 7
    Windows 7 Ultimate 32 bit
    Thread Starter
       #4

    heres the new log i cant open the log on my computer dont know if that means any thing Attachment 252214
      My Computer


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

    That's normal - the file is permanently in use.
    The CBS/SFC log is clear - so we can replace the 'bad' files from the CheckSUR report.....


    I've uploaded a file - likaa.zip - to my SkyDrive at Noel's SkyDrive
    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 likaa in the same place.
    Open this folder - there should be one folders inside it ( Packages)

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


    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


  6. Posts : 7
    Windows 7 Ultimate 32 bit
    Thread Starter
       #6

    NoelDP said:
    That's normal - the file is permanently in use.
    The CBS/SFC log is clear - so we can replace the 'bad' files from the CheckSUR report.....


    I've uploaded a file - likaa.zip - to my SkyDrive at Noel's SkyDrive
    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 likaa in the same place.
    Open this folder - there should be one folders inside it ( Packages)

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


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

    Post the new CheckSUR.log file, and the CheckSUR.persist.log file.
    thanks do you mean run the surt and scf scan now option or just scf scan now thanks for reply
      My Computer


  7. Posts : 7
    Windows 7 Ultimate 32 bit
    Thread Starter
       #7

    ran surt ageing here is the log it left Attachment 252226 am off to bed now have work in morning till 4 will be on just after that thanks for reply and all the help you are giving me
      My Computer


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

    - I missed all the errors from one of the patches.... back in a jiffy :)
      My Computer


  9. Posts : 7
    Windows 7 Ultimate 32 bit
    Thread Starter
       #9

    NoelDP said:
    - I missed all the errors from one of the patches.... back in a jiffy :)
    thank you so much for your help you guys are amazing
      My Computer


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

    It's fun, most of the time :)
    The problem with the missing files isn't actually all my fault - I did include the files for that patch, but the wrong version. I'm having to ask someone else if they have the correct version, as that one was withdrawn by MS soon after release (it caused a few problems in some machines)
    I probably won't be able to post a new fix until Sunday afternoon.
      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 14:26.
Find Us