Can't upgrade IE, KB2670838 returns error 800B0100

Page 2 of 2 FirstFirst 12

  1. Posts : 8
    Windows 7 Home Premium SP1, 64-bit
    Thread Starter
       #11

    Thank you so much!
    Everything is working great, and I've started going through the list of updates which suddenly became available - no errors so far :)


    I'm quite curious (and honestly a little annoyed that I couldn't fix this myself), and so I have a few questions regarding "the case" (which appear to be solved) :
    • How does errors like mine occur? Is it preventable, and could it be my own doing?
    • What does "SURT" actually do, and how does the SURlog-errors relate to the errors sfc finds?
    • How did you fix it? From here it all looked so simple ... Do you possess some kind of magic or would I be able to fix this myself, if something similar should appear in the future?
    • I see you all over these forums, helping others like me - do you do this professionally?
    I hope you can help me out with some of my questions
    /kjonas65
      My Computer


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

    I'll try to address your answers in order...

    • Most times, I reckon such errors result from problems during the shutdown/restart phase when the system rearranges the files. If for some reason the system shuts down too soon (e.g. batteries die, or power-out) then there may be work that doesn't get done. The only thing you can do to prevent it is to make sure that you allow the machine to shut off completely before unplugging it. Other causes are memory or HD problems.
    • The SURT/CheckSUR tool scans all the components of Windows - which are recorded in the registry - and checks that all references are present, and all control files present (it now also checks for 'payload' files - but makes no attempt to repair them) and attempts to correct any errors it finds. The reason that it's so large is that it contains a huge store of potential replacement files (I once tried to expand all the files, and it got to 6GB before I stopped it!)
    • The trick is to have a similarly large stock of files from which to draw - my current archive weighs in at about 60GB (mostly Win7 x64 or x86, with a few Vista) from which you can cherry-pick the relevant files and then use CheckSUR to do the necessary replacement.
    • Know anyone who wants to hire a 60year-old geek?
    • :)
    Good luck!
      My Computer


  3. Posts : 8
    Windows 7 Home Premium SP1, 64-bit
    Thread Starter
       #13

    That is quite the dedication, to keep such a large amount of "help files" in stock. I wonder if Microsoft is aware of the great supprt one can find on this forum
    I don't currently know anyone looking to expand their support-team, I'm afraid - but I will make sure to help others onto these forums if I see similar problems, if you don't mind.

    I just tried running sfc /scannow again, and it is still finding erros, which it can't repair. Is it safe to ignore these erros when nothing appears to be broken? :)
      My Computer


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

    Post the CBS.log - I'll see what it says and maybe fix it, but I have a suspicion that I know the errors it'll show.
      My Computer


  5. Posts : 8
    Windows 7 Home Premium SP1, 64-bit
    Thread Starter
       #15

    That's a rather large text-file
      My Computer


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

    Yup - as expected...
    Code:
     Line 5053: 2015-07-06 00:37:28, Info                  CSI    0000033c [SR] Repairing 1 components
     Line 5054: 2015-07-06 00:37:28, Info                  CSI    0000033d [SR] Beginning Verify and Repair transaction
     Line 5057: 2015-07-06 00:37:28, Info                  CSI    0000033f [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, 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 5060: 2015-07-06 00:37:28, Info                  CSI    00000341 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, 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
    MS says that these errors can be ignored, as the files concerned were accidentally tagged as static during build, rather than variable - and shouldn't even be scanned by SFC.
    If you don't want to ignore them, you'll have to uninstall KB3068707 (and possibly KB3022335) and hide it/them to prevent reinstall by Windows Update.

    Otherwise, the scan was clear.
      My Computer


  7. Posts : 8
    Windows 7 Home Premium SP1, 64-bit
    Thread Starter
       #17

    Thank you again, I don't think I have anymore questions now
    /kjonas65
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 17:54.
Find Us