Unable to update windows (even standalone)

Page 1 of 3 123 LastLast

  1. Posts : 14
    Windows 7 x64
       #1

    Unable to update windows (even standalone)


    Hello!

    I've never really had an issue with an update, that is until the KB3004394 issue. During that time, I fought with my system quite hard and eventually uninstalled that update. However, I appear to have damaged something else in the process, as I am now unable to install certain windows updates.

    Updates that will not install:
    KB2506143 fails with 800B0100
    KB3013126 fails with 800B0100
    KB3014406 fails with 800B0100

    The system update readiness checker does not complain. Windows resource protection spits out: Windows Resource Protection did not find any integrity violations.

    I zip'd the cab and the txt files separately as together it was over the limit.

    Please help!
      My Computer


  2. whs
    Posts : 26,210
    Vista, Windows7, Mint Mate, Zorin, Windows 8
       #2

    Maybe your AV program blocks them
      My Computer


  3. Posts : 14
    Windows 7 x64
    Thread Starter
       #3

    With AV completely disabled, I get the same error. I am redoing the SURT without AV, but will be honest that I don't have much faith that will change anything.

    I believe the offending line in the CheckSUR is

    (f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_111_for_KB3004394~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
    (f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_111_for_KB3004394~31bf3856ad364e35~amd64~~6.1.1.0.cat

    Off to reboot
      My Computer


  4. Posts : 14
    Windows 7 x64
    Thread Starter
       #4

    Still nothing, same error.
      My Computer


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

    Your CheckSUR report shows
    Code:
    Summary:
    Seconds executed: 359
     Found 38 errors
      CBS MUM Corrupt Total count: 19
      CBS Catalog Corrupt Total count: 19
    Unavailable repair files:
     servicing\packages\Package_111_for_KB3004394~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_111_for_KB3004394~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_112_for_KB3004394~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_112_for_KB3004394~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_113_for_KB3004394~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_113_for_KB3004394~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_114_for_KB3004394~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_114_for_KB3004394~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_2_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_2_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_2_for_KB3014406~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_2_for_KB3014406~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_39_for_KB3004394~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_39_for_KB3004394~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_3_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_3_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_40_for_KB3004394~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_40_for_KB3004394~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_4_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_4_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_6_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_6_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_75_for_KB3004394~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_75_for_KB3004394~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_76_for_KB3004394~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_76_for_KB3004394~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB3004394_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB3004394_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB3004394~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB3004394~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB3013126_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB3013126_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB3013126~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB3014406_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB3014406_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB3014406~31bf3856ad364e35~amd64~~6.1.1.1.mum
     servicing\packages\Package_for_KB3014406~31bf3856ad364e35~amd64~~6.1.1.1.mum
    Your SFC scan is clear.

    This is going to be an awkward one - because one of the affected patches is one withdrawn by MS soon after release because it caused major problems for a lot of people. As a result, I don't have access to the necessary files, so I'll have to take a guess as to the best way to deal with it.

    I'll post a fix protocol for the other files later - then we'll have to see what we can do with the awkward one.
      My Computer


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

    Thinking about it...
    DO you have a System Restore point to which you can restore, prior to the installation of KB3004394? (some time after 8th Dec)
    If so, try that - then do a fresh Check for Updates before doing anything else!

    Post back with your results - and a new set of SFC/CheckSUR results.
      My Computer


  7. Posts : 14
    Windows 7 x64
    Thread Starter
       #7

    I don't have a restore point...

    I was thinking along the lines of trying to clear what the update system thinks it needs to install, since that KB is uninstalled.
    Thoughts? Like this

    But if that is destined to be fruitless, rather not do it.
      My Computer


  8. Posts : 14
    Windows 7 x64
    Thread Starter
       #8

    Well, I went ahead and cleared it out, but am at the same result. Somehow the existence of all updates needs cleared, even those pending.
      My Computer


  9. Posts : 14
    Windows 7 x64
    Thread Starter
       #9

    Did the following:

    1. Reset windows update through link above
    2. On reboot, went in to the recovery console, started regedit, loaded my machine's software hive
    3. Deleted every occurrence of KB3014406
    4. Unloaded hive
    5. Booted machine
    6. Verified (successful) that the registry keys were still gone
    7. Ran Windows update

    It still picked it KB3014406, and even better (sarcasm) it still wants to install that update, and it replaced every single registry value I deleted.
      My Computer


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

    So what did you expect?
    The ONLY update there's been a significant problem with is KB3004394.

    Please run through the WU posting instructions again, and post the new logs, and we'll see where we are.
      My Computer


 
Page 1 of 3 123 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 01:07.
Find Us