KB2862335 error 80070057 causes other patches to fail

Page 1 of 4 123 ... LastLast

  1. Posts : 1,102
    OEM Windows 7 Ult (x64) SP1
       #1

    KB2862335 error 80070057 causes other patches to fail


    Hi:

    Followed instructions here: Windows Update Posting Instructions

    Older but fully patched* and otherwise stable Dell XPS 8100 Win7/64.
    (*I was waiting a while longer to update to IE10 because so many other users had 9C59 issues & my security suite initially had some compatibility issues, that are now resolved.)
    Has had issues with PnP USB devices in past, but none recent (USB flash drive & USB external HDD, as well as USB printer and mouse/keyboard, all work fine).

    KB2862335 appears to be the culprit, as the others seem to have failed because of it.
    I now suspect previous PnP/USB issues and the current update failures are related.

    Attempted first batch of patches this AM - looked OK until configuring after restart > failed > reverted.
    Here were the 7 patches & error codes:
    2862335: 80070057
    2879017: 800F0826
    2868038: 800F0826
    2864202: 800F0826
    2864256: 800F0826
    2865058: 800F0826
    2890788: Successful

    After a quick Google search of the error codes, I UNselected KB2862335 and tried the other 5 again.

    Same result: got to configuring after reboot > reverted.
    This time, a different patch generated the 80070057 error:
    2868038: 80070057
    2879017: 800F0826
    2864202: 800F0826
    2864256: 800F0826
    2854058: 800F0826

    So: I ran SURT (installation complete).
    SFC /scannow: Found corruption that it could not repair.

    CBS, CHECKSUR and SFC logs are attached, I hope.
    (The CBS log looks too small to be the right one???)

    Since I am the sole user of the computer & use only USB devices known to be clean, I am not particularly concerned about security if I could not update the USB drivers.

    However, the failed USB driver updates are preventing me from installing the other critical security patches, especially for IE, Windows and Office.

    Please advise.

    Thanks so very much for your expert help!

    EDIT:
    I also have 2 VERY large (18 MB & 14 MB) zipped CBS logs. One was generated BEFORE running SURT and sfc /scannow and the other one afterward.They appear to be too large to upload directly, as I get an error message each time.
    Last edited by MoxieMomma; 09 Oct 2013 at 09:29. Reason: typo
      My Computer


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

    There's only one error in the SFC log -
    Code:
     Line 4454: 2013-10-09 08:29:46, Info                  CSI    00000329 [SR] Repairing 1 components
     Line 4455: 2013-10-09 08:29:46, Info                  CSI    0000032a [SR] Beginning Verify and Repair transaction
     Line 4458: 2013-10-09 08:29:46, Info                  CSI    0000032c [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.1.7600.16385, 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
    (which shouldn't cause any major problems)

    ...and nothing in the CheckSUR log.

    There's only one minor error in the rest of the normal CBS.log file data - which we can usually ignore :) - but since it's
    Code:
    2013-10-09 08:15:35, Error                 CBS    Failed to shred identity: Microsoft-Windows-InternetExplorer-LanguagePack [HRESULT = 0x80070057 - E_INVALIDARG]
    maybe we should take a closer look


    I'd be VERY surprised if fixing the tcpmon error actually cures the problem, but we'd better make the effort first.

    I'll post the fix protocol for it later.

    Please post your c:\Windows\windowsupdate.log file - it may hold a clue.
      My Computer


  3. Posts : 1,102
    OEM Windows 7 Ult (x64) SP1
    Thread Starter
       #3

    Hi, NoelDP:

    Thanks for your prompt and expert reply.

    How odd!
    Given age of the system (purchased Feb 2010), I might have expected more errors, even though this is the 1st time I've had a serious problem with Windows Updates.

    My gut feeling is that the prior USB/PnP "issues" must be somehow related to what's happening now, as the coincidence is too striking.

    IIRC that tcpmon error has been around "forever", since some time shortly around the time of a factory restore in Aug 2010 after a McAfee major version update borked many users' computers.
    (I moved from McAfee to another security vendor for all my rigs at that time.)
    I don't know that it has posed any obvious functional issues since then, but I will defer to your expert opinion & it seems reasonable to try to fix it.

    As I mentioned, I'd be comfortable taking a pass on all these current USB driver updates, if there is no remote vulnerability with having the older drivers.
    Although I'd like to be able to install *all* critical/important updates, the patches to IE, Windows kernel & Office would seem to be more "important" for now???
    However, the USB driver errors are blocking my ability to install the other patches (at least nearly all of the ones I tried earlier.)

    Windowsupdate log is attached.
    I also still have both of the earlier, large zipped CBS logs, if you need them.

    THANK YOU SO VERY MUCH!!!

    MM
    Last edited by MoxieMomma; 09 Oct 2013 at 13:04. Reason: clarification
      My Computer


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

    I think the best thing to do, is to try clearing the SoftwareDistribution folder, and see if that clears the error that we are seeing..
    Code:
     Line 345: 2013-07-09 18:49:19:526 1060 79c Agent WARNING: Failed to evaluate Installed rule, updateId = {818701AF-1182-45C2-BD1E-17068AD171D6}.101, hr = 80242013

    Openan Elevated Command Prompt

    Runthe following commands



    NET STOP WUAUSERV

    REN C:\WINDOWS\SoftwareDistribution SDOLD

    NET START WUAUSERV



    wait15 minutes, and reboot

    thenwait 10 minutes, and open Windows Updates, and run a Check for Updates.



    Installonly the oldest update found - and reboot once installed (there's hopeful! :) )

    thengo back to Windows updates and install the others.
      My Computer


  5. Posts : 1,102
    OEM Windows 7 Ult (x64) SP1
    Thread Starter
       #5

    Hi, Noel:

    As you're probably heading off to bed soon, I need to clarify a couple of things before I try this.
    FWIW, system is behaving otherwise normally -- except Windows Updates -- since I posted early today.
    (Also, as you know, this is an OEM system. I do have the Windows disks & a repair disk created when I first booted it out of the box from Dell, but they are NOT SP1.)

    Questions:

    1. This isn't the same as resetting Windows Updates, that wipes out the Update History (just asking)?

    2. I have not yet rebooted the system since it reverted during the 2 earlier attempts (nor have I tried again to install ANY other updates). Should I reboot once before starting your procedure?

    3. When/if I get to the step of checking for the "oldest update found", I presume you mean the oldest "CRITICAL" or "IMPORTANT" update, or could it be something "optional" (such as Bing desktop)?

    Thanks!

    MM
      My Computer


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

    A full Windows Update reset usually also includes renaming/deleting the SoftwareDistribution folder.
    I'd avoid the optional updates until everything is OK - try the oldest Security update (they are usually pretty small so less likely cause a problem :)) - otherwise any Windows update (but not .NET ones, please!) will do.
    Check the release dates in the right-hand column of the WU listing.

    You should reboot (twice?) first - otherwise it could be that a 'pending' update will block the install.
      My Computer


  7. Posts : 1,102
    OEM Windows 7 Ult (x64) SP1
    Thread Starter
       #7

    NoelDP said:
    A full Windows Update reset usually also includes renaming/deleting the SoftwareDistribution folder.
    I'd avoid the optional updates until everything is OK - try the oldest Security update (they are usually pretty small so less likely cause a problem :)) - otherwise any Windows update (but not .NET ones, please!) will do.
    Check the release dates in the right-hand column of the WU listing.
    OK, thanks.
    I understand about finding the release date.:)
    I assume that if there are multiple patches with the same date, I should just pick any one (other than .NET)?
    Perhaps an Office security patch?
    Or any Windows security patch (except .NET)?
    Or an IE security patch?
    And it needs to be a **security** patch that will REQUIRE a reboot?
    Or can it be another (stability/performance) patch that might not otherwise require a reboot?



    You should reboot (twice?) first - otherwise it could be that a 'pending' update will block the install.
    Sorry, my nerves & brain are frazzled by all this.
    Just want to be sure I understand....
    The computer has not been shut down or rebooted since the failed updates (twice) yesterday morning.
    It is otherwise behaving normally.
    Are you saying that I should reboot once (or even twice) before I even attempt to start the procedure to clear the Software Distribution folder?

    I will be leaving for work in a little while, so unless there is something I must do BEFORE shutting it down now, I will need to start the process later today, when I get home (it should still be before UK pubtime/bedtime).

    Also, I located the attached log in that Software Distribution folder -- I don't know if it adds anything useful.
    Just thought I would save it before clearing the folder...?

    Thanks!

    MM
    Last edited by MoxieMomma; 10 Oct 2013 at 04:10. Reason: clarification
      My Computer


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

    I'd reboot (once) before starting the SoftwareDistribution change - there's a reboot as part of that anyhow, so that would count as a second one.
    If there are any signs of updates having installed in the meantime, then reboot again before attempting to go to WU
      My Computer


  9. Posts : 1,102
    OEM Windows 7 Ult (x64) SP1
    Thread Starter
       #9

    Just a quick update (from my other desktop rig) ---

    Late day at work for me today.
    Hope to get to your suggested fix tomorrow.

    Will update when I have tried it.

    Thanks for your patience,

    MM
      My Computer


  10. Posts : 2
    Belgium
       #10

    I had the same problem, and stumbled onto a somewhat strange solution after a number of failed attempts.

    First unchecked 2862335 and let it install all the other updates.
    At boot it *still* failed / reverted / rebooted again, but after the system came up, the updates appeared to have been installed after all. Only 2862335 was listed as available when windows update came up again.

    Then let it install 2862335, and this time it succeeded.
      My Computer


 
Page 1 of 4 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 19:06.
Find Us