9C57 error updating on IE 10, now IE 11-- this one's a toughie

Page 2 of 3 FirstFirst 123 LastLast

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

    I would think twice about upgrading any system to Windows 8.1 without a functional system image to restore from in the first place - and conventional wisdom is that upgrade is more likely to make existing problems worse, than cure them.

    I need to review the thread - back later.
      My Computer


  2. Posts : 14
    Windows 7 Home Premium x64
    Thread Starter
       #12

    Are there no hidden flags to force a KB update?

    What has me confused is how a repair install fails. What would cause that? A registry item has unmodifiable read-only permissions maybe?
      My Computer


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

    No - one of the whole point about Windows update is that updates will NOT install on a system that's already corrupt
    since the chances are that such an installation is only going to make matters worse.

    Upgrades will attempt to take settings from the previous OS to the new one - and if they are corrupt, then all hell can be let loose!
      My Computer


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

    So I've a corrupt system, but no tools exist that can identify the corruption.
      My Computer


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

    even if they can identify the corruption, then the real problem is isolating the cause of the corruption - which may still be present, and so could cause further corruption (whatever we manage to do in the way of cleanup)

    In cases like this, then a repair install would be the initial 'solution' - and depending on the results of that, then a clean install may be necessary.
      My Computer


  6. Posts : 14
    Windows 7 Home Premium x64
    Thread Starter
       #16

    Yup, clean install seems to be the only sure thing. However, I'm going to give it one more try. CCleaner's registry scanner identifies a large number of errors, mostly ActiveX/COM and path issues.

    I'll go through, item by item, and manually fix the obvious path errors while leaving any unknown issue intact, and see if that makes a difference to the repair install.

    Otherwise, thank you and I appreciate the effort.
      My Computer


  7. Posts : 14
    Windows 7 Home Premium x64
    Thread Starter
       #17

    ...And I should note that the cause of the corruption was the failed June certificate updates. I didn't have a problem until then, however none of MS's published fixes for that error worked for me-- or if it worked, the WU corruption remained.
      My Computer


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

    NO registry 'cleaner' is reliable - most are very dangerous tools.
    CCLeaner is less dangerous than most - but will still manage to destroy a system given half a chance.
      My Computer


  9. Posts : 14
    Windows 7 Home Premium x64
    Thread Starter
       #19

    I agree. Which is why I'm doing it manually.

    But at this point, what have I got to lose? I'm left with needing a clean install anyway. If the manual edits don't work, I'll probably use some nuclear option.
      My Computer


  10. Posts : 14
    Windows 7 Home Premium x64
    Thread Starter
       #20

    I wanted to followup to close this off. (Many of these threads when found in a Google search just trail off, and I wanted to button this one up for that reason).

    I dove very deep into this, and spent several days uninstalling each of hundreds of updates since 2011 to return to as-close-to-SP1 as I could. You might think that's crazy, and maybe it was, but I had time and room to experiment, and my Windows Update subsystem was healthy, as far as all the tools could tell.

    Basically I got to the point of SP1 + a few non-un-installable updates. All of sfc, CheckSUR, chkdsk, and other scanners were happy. Windows Update was telling me that I had 30 required updates, which of course is nuts-- for a new SP1 machine it's more like 147 updates. And still, KB2834140 -- the lynchpin of it all, as the prerequisite for the 2670838 platform update, and thereby IE10 and IE11 -- simply refused to install, with the same CBS_INVALID_PACKAGE error as before. And even still a repair install failed at the 62% mark, even with all the necessary MIG_UPGRADE_IGNORE_PLUGINS tricks.

    Net, I went as far as I could to troubleshoot it. I ended up reinstalling Windows. I think that Windows is just destined fall to pieces after several years of installs and uninstalls. The update subsystem just isn't that robust and is far too complex and subject to error, so if you run across these issues, they may be intractable, leaving you with no option but to start over.

    Anyway, thanks very much for looking into this, Noel. VERY much appreciated, and I'm happy this forum is such a great resource.
      My Computer


 
Page 2 of 3 FirstFirst 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 18:33.
Find Us