KB2862335 error 80070057 causes other patches to fail

[MoxieMomma]

Hi:

Followed instructions here: http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html

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.

 

[NoelDP]

There's only one error in the SFC log -

 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

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.

 

[MoxieMomma]

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

 

[NoelDP]

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..

 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.

 

[MoxieMomma]

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

 

[NoelDP]

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.

 

[MoxieMomma]

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

 

[NoelDP]

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

 

[MoxieMomma]

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

 

[lucvdv]

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.

 

[LudeBob89]

I'm also having the same issues with this kb2862335 patch.
As above have resorted to manually selecting all other updates to get them updated.
The kb2862335 patch still refuses to load and continually fails. Many lost hours on retries. Did not enjoy the result listed above.

Laptop is a Dell Studio 1555, running Win 7 Home Prem 32 bit.

 

[lucvdv]

It looks like the real culprit was not KB2862335 in my case, but KB2862330.
Even though only KB2862335 was listed as available at some point, four out of the original twenty-something updates reappeared after installing it.
Among those was KB2862330, and that kept failing and causing the others to fail too as long as I included it.

Currently, everything is installed except for 2862330, which still fails with 80070005.
Dissecting that code, the error number part (the lowest 32 bits) is a simple "access denied", facility 7 = Win32, while the 8 up front means it's an error (as opposed to a warning or success status).

Also noteworthy: I have another system with identical hardware, also Win7-64 fully patched, and with the same major software packages installed (Office 2010 upgraded to 2013 and Visual Studio 2010), that didn't exhibit this problem.

 

[MoxieMomma]

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

Hi, Noel:

Sorry again for delay (have been offline for work & "life").
I just realized that I need one further tidbit from you before proceeding.
I am online from my other desktop at the moment.

Windows Updates on the rig in question is currently configured (as always) to "notify only" (but not d/l or install updates).
It has been powered off for 2 days.
When I cold start it this morning, Windows Updates will undoubtedly phone home shortly after reboot to check for updates, BEFORE I have a chance to start your suggested fix of clearing the SD folder, etc.

SO, assuming that it **will** do just that:
1. Do I need to temporarily change the Windows Updates settings to "never check for updates/not recommended" and then reboot again before starting the SD folder clearing procedure, so that "check for updates" will be only manual, not automatic (until we get things fixed), OR

2. Is it OK to boot up, & let Windows Updates phone home to check for updates (but not install anything) first?
If this is OK, and I start your process from this post of clearing the folder, rebooting, checking for & installing updates, do I need to change the Windows Updates settings to manual at any time in the process?

FYI We expect severe weather in my locale today and for the next several days. I live in an older area with frequent power outages. Even with a UPS/battery backup, I avoid doing Windows Updates when thunderstorms threaten. I hope to be able to get this sorted today, before I have to go offline again.
But if there is a delay in my replies, it's because of the weather.

@ lucvdv AND ludebob89:
Thanks for your input.
However, as each computer is unique (especially for these sorts of issues), I will follow the expert advice of NoelDP.
To avoid confusion for everyone, if you need assistance, I would respectfully suggest that you please follow the instructions in this pinned topic and then please start your own topic.
I think NoelDP will agree that it's not advisable for the expert to try to assist more than one OP in a given thread.
Thanks very much for your understanding.

MM

 

[NoelDP]

That's OK - the normal check for updates won't do anything nasty Follow procedure 2.

A normal update shouldn't take more than 5 minutes from the start of the install to the reboot - and possibly another couple of minutes after the boot if it's a big one. Since most Security updates are relatively small, you quite often won't notice the extra time involved, or see the 'configuring Windows' screen.

 

[MoxieMomma]

OK, I have renamed the SD folder and verified that the renamed folder is in the expected location.
(FWIW, as expected, Win Updates did phone home upon cold start -- there are 27 (the 1 Silverlight patch DID install OK last week).)

I am now in the 15-minute waiting period before the reboot.

As you advised, I will leave Win Updates configured to "notify", so it may well phone home on its own when I reboot.
If it does not (because it already checked once when I cold started a while ago), I will follow instructions to do a manual update check 10 minutes after the reboot.

And then I will try 1 update.

<crosses fingers and toes>

 

[MoxieMomma]

How long should the first manual update check take?
It has been 4 minutes on a HSI connection, and it is still checking...
(Does NOT appear to be frozen.)

EDIT: Never mind. Know tells me there are 29 available IMPORTANT patches (including IE10 (which I had been hiding)).

I will start with one "easy" security patch.

Wish me luck.

 

[MoxieMomma]

1 down, 27 to go (assuming I hide IE10 for now).

Just installed KB2827324 (Excel 2007 Security patch).

Successful.
No reboot requested.

I think the Office patches last week did NOT require a reboot.

So, should I select a Windows patch that will need a reboot (BUT NOT .NET, and NOT the 3 kernel-level patches (2847311, 2883150, 2876284) & NOT the USB driver patches that precipitated the original problem)?

Or should I keep going with the "easy patches" in the Office group that won't need rebooting, and then tackle the Windows patches??

 

[MoxieMomma]

Hi, Noel:

So far, so good.
But I've only done what's "easy".

All of the Office patches are in. No reboot requested, so I have not yet done so.

Before I proceed with the Windows patches, I need your advice as to the best sequence.
FYI, Even when I adjust the sliders, I cannot see a "Date" heading in the Window listing the patches.
But the attached screen grab shows the current status.
I am hiding IE10 for now, so I have 21 left:

1. Last week's kernel level SECURITY patches (2847311, 2876284, 2883150).
2. Last week's USB driver SECURITY patches (2884256, 2862335, 2864202, 2868038. NOTE: I do not see 2862330 on the list (the 2-reboot patch)).
3. Last week's various .NET patches (3 for .NET 3.5.1 and 2 for .NET 4)
4. Last week's miscellaneous patches, including the Update cleanup patch (2846960, 2852386, 2882822, 2888049, MSRT (890830)).
5. Last week's IE Cumulative SECURITY patch (2879017).
6. Last week's CCL SECURITY patch (2864058).
7. AND these 2 from 2011 (both of which I am sure I "hid" for some legit reason back then):
   1. 2529073 -- OF NOTE, this is a USB DRIVER PATCH! So, could the lack of this patch on the system account for why last week's USB driver patches failed?
   2. 982018 -- Advanced Disk Format compatibility patch

In what order should I attempt these remaining 21 patches, given that it was the USB Drivers that caused last week's problems, and that the .NET and kernel-level patches probably should be left for last?

I will await your further instructions before I proceed.

Thanks very much, so far!

 

[NoelDP]

First do the Security patches for Windows
Then the ordinary Update for Windows
Then the .NET updates

reboot between each set, and force another Check for updates after the reboot.

 

[MoxieMomma]

Should I do the USB driver group first, perhaps one at a time?

And might last week's USB driver patches depend on the USB driver patch from 2011 (KB2529073)?
​

Or the kernel level patch group first?