KB2862335 error 80070057 causes other patches to fail

[MoxieMomma]

IE Patch, 2864058 and the 3 kernel-level patches are in.

I am hiding IE10 for now, so I have 16 left:

1. Last week's 4 USB driver SECURITY patches (2884256, 2862335, 2864202, 2868038. NOTE: I do not see 2862330 on the list (the 2-reboot patch)).
2. Last week's 5 .NET patches (3 for .NET 3.5.1 and 2 for .NET 4)
3. Last week's 5 miscellaneous patches, including the Update cleanup patch (2846960, 2852386, 2882822, 2888049, MSRT (890830)).
4. 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

I understand to finish Security Patches before moving on to regular Windows patches and then .NET.

But now the rubber meets the road, as the final group of Security patches is the USB drivers <GULP!>.
2862335 seems to have been the culprit last week.

So:

1. Do I need to try first to install 2529073 (a USB patch from 2011) before I do last week's USB driver patches , even though it's not a "security patch"? (I don't recall now, but I am quite sure there was a valid reason for my NOT having installed it back in 2011.) Just wondering if there is some sort of dependency with last week's USB driver patches that caused last week's failure.
2. Should I perhaps do this USB driver group one at a time, saving 2862335 for last?

Thanks a ton for your ongoing support!

 

[NoelDP]

Just do them in the order I stated - don't worry if a couple fail, as it could be that they depend on others being installed first (just add the failures to the next batch of updates)

run driver updates last of all.

 

[MoxieMomma]

Thanks for the prompt reply.

OK, so now I am confused.
My brain is old and tired.
I'm only trying hard NOT to screw this up or to burn any bridges.

The original advice was security updates (which would include the USB driver group) FIRST > regular windows updates > .NET.
But now you advise doing "driver updates last of all"?

But the USB driver patches ARE security patches?
And it looks as if 2862335 was the one that caused the group to fail the other day.
Once it failed, I couldn't install any other patches until we had done the SURT/sfc/rename-SD-folder thing.
And I don't know if that outlier from 2011 (2529073) needs to go first, or not?
(The fact that it relates to USB drivers may or may not be related to my problem - I have no idea.)

So, if 2862335 fails again now, it might prevent installing the other updates again, just like last time????

I am perfectly OK with doing the regular Windows patches and then the .NET groups before doing the USB driver security patches last, even though these latter are both *drivers* and *security* patches.

I'm so sorry -- I know this must be intolerably frustrating for you.

Unless you advise differently, I guess I will tackle the regular Windows update group from last week next -- I know from my other 2 rigs that it will require a reboot.

I will post back after that.

Thanks again so very much.

 

[NoelDP]

Yeah - it does get confusing

Those updates are primarily Security updates - to drivers. As such they come under 'Security' rather than 'driver' to my mind.

Always do a reboot after each group - whether it asks for it or not - as this helps to ensure that the latest set are properly embedded in both file-system and registry before proceeding to the next group.
It may take 10-15 minutes to do things that way - but the alternative may be a System Restore that takes an hour, (if it works at all) and repeating the installs all over again.

 

[MoxieMomma]

OK, they are all in EXCEPT for last week's 4 USB driver security patches, KB2529073 and KB982018.

Even though the .NET updates did not request a reboot, I am about to do so.

Once I reboot, the only significant questions are still the same:
1. Whether to try 2529073 first, because it is older than the 4 USB patches from last week?
2. Whether to tackle last week's USB driver group (4 patches) all at once, or individually, perhaps saving 2862335 for last?

Thanks so much for your infinite patience!

 

[NoelDP]

In cases where updates are dated the same, go in order of KB number

KB number are assigned at the start of a debugging project - and are used only for that project, so if a later update needs to make changes to an earlier one that's still in development, the older one is canned, and subsumed into the new project with the new KB number (at least most of the time!)
Certainly take the older one first - and reboot. Since the others are the same date, they should be designed to install at the same time, so try that, and only if you get a failure should you revert back to single installs, with a reboot in between.

 

[MoxieMomma]

OK, thanks for that.
I guess I need to try 2529073 first, then.

Normally I would have left 2529073 for last, since it is NOT a security patch (and since I cannot recall why I hid it back in 2011, in the first place, but there must have been a compelling reason).

But since it relates to the USB drivers, it seems prudent to try this one first > reboot > then attempt the 4 USB driver updates from last week as a group?
(982018 is the last priority among the 6 remaining patches....)

ODD NOTE: I was not ever offered 2862330 (the "2-reboot" USB driver patch) today, despite several manual update checks. With the updates history removed, I don't know if it might have actually installed the other day, or whether MS has pulled it?

OK, well, wish me luck with KB2529073.

If you hear a loud crash in a few minutes, it will be my PC heading out the window.

Back soon.

 

[MoxieMomma]

KB2529073: Failed at 7% during configuration AFTER the requested restart.
Error code: 80070057

(I guess there WAS a reason why I had hidden that patch when it was first offered in 2011. Oddly, it is now coming up only as "recommended", not important.)

I still have the 4 USB driver patches from last week (but fear they may fail now, too, if they depend on it).
And there is 982018 (low priority).

What's the next step, please?

 

[NoelDP]

OK - try installing the 4 new ones - they may clear the decks

 

[MoxieMomma]

Will do.

I guess if these fail again, it will be back to SURT & sfc /scannow (perhaps offline?)???

What about the native Windows 7 control panel > troubleshooter > Windows Updates? (Or have the steps already taken done what it would have done?)

Gonna try the 4 from last week now.

P.S. Recall I mentioned way back in the original post that this rig had had USB/PnP issues a long time ago. Just thought I'd mention it again.

 

[MoxieMomma]

No joy again with the 4 USB driver patches.
Got all the way to restart > configuring > failed at 7% again (even though these were different updates)

KB & error code:
2862335: 80070057 (same as last week)
2884256: 800F0826 (same as last week)
2864202: 800F0826 (same as last week)
2860838: 800F0826 (same as last week)

FWIW When I tried to omit the 80070057 update and reinstall the rest the other day, it didn't work.
And it seems that SURT did not fix the 80070057 error for 2862335 from last time.
I checked the Dev Manager and the USB controllers all look OK (no yellow exclamations).

I guess there is some sort of deep USB driver corruption in the OS?

Next step, please?

Random ideas:
1. Rerun SURT & perhaps offline sfc /scannow?
2. Built-In/Native Windows troubleshooter from the control panel?
3. MS Fixit?
4. Clean boot attempted install?
5. Manual attempted install?
6. Disconnect older HP USB printer & re-attempt troubleshooting or install?

None of these sounds particularly promising, so I'll defer to you, of course.

 

[NoelDP]

Now we try installing the failing patches from downloads.....
download the updates from the links below, and then install them (with reboots in between)

if/when any fail, stop, and post details of the error message.

Download Update for Windows 7 for x64-based Systems (KB2529073) from Official Microsoft Download Center
Download Security Update for Windows 7 for x64-based Systems (KB2862335) from Official Microsoft Download Center
Download Security Update for Windows 7 for x64-based Systems (KB2864202) from Official Microsoft Download Center
Download Security Update for Windows 7 for x64-based Systems (KB2868038) from Official Microsoft Download Center
Download Security Update for Windows 7 for x64-based Systems (KB2884256) from Official Microsoft Download Center

 

[MoxieMomma]

OK, just manual downloads, right?

FWIW I never got 2529073 installed back in 2011, either. So I could skip it, if you think that's advisable.
Also, FWIW re: "clean boot" -- my other 2 rigs (a very similar Win7/x64 Dell DT and a Win7/x86 Dell LT) run the very same security suite (KIS2013) & they took all patches fine. So, I don't think KIS is blocking the install.

Any thought to disconnecting the older HP printer that is connected via USB?
It has the latest drivers (Win7-compatible, of course) and it works just fine.
So it may have no bearing on this whatsoever.
I just need to be sure it will still work when it is reconnected after the next round of attempted repairs.
Just a stoopid thought.

I have been at this all day and am exhausted.

I need to take a break.
In the interim, I am sending you via the Transatlantic intertubes a 6-pack of our finest local microbrew.

I will be back later, probably after bedtime in Wales.

So, if the first attempt to manually install the first update (2529073) fails, I should stop there, & post back with the error code, right?

Thanks!

 

[NoelDP]

Yep - got it in one (and thanks for the 6-pack!)

KIS is pretty good - but is also known to occasionally cause trouble for some fairly esoteric reasons.

Have ANY other AV's EVER been installed on this machine? - if so, which?

If the install fails in a normal boot, then installing from a Clean Mode boot has been known to work on occasions, if the cause is interfering software.

I'm reasonably sure that unplugging the printer won't cause problems later - and may be a good idea, since all the problem updates are related to USB drivers. (Hopefully, the Clean Mode boot would also do this - but some divers hook into the system at a very early stage, so you may need to try both)

 

[MoxieMomma]

Yep - got it in one (and thanks for the 6-pack!)

I hope the brewskis were still cold when they arrived.

KIS is pretty good - but is also known to occasionally cause trouble for some fairly esoteric reasons.

Both other Win7 rigs also run KIS2013 -- got these same patches installed without issue.
Even tried pausing protection for a few minutes during the install today (yes, I am behind a router/NAT firewall), but it didn't help.
TOTALLY disabling or uninstalling KIS would be a royal PITA.
Before I embark on the latter, I would probably wait until I am ready to uninstall 2013 before cleanly upgrading to 2014 in a month or so (I am waiting for 2014 to stabilize a bit).

Have ANY other AV's EVER been installed on this machine? - if so, which?

Crapafee was OEM when I bought the rig from Dell in Feb 2010.
A major version upgrade in Aug 2010 borked many, many users' computers (black screen, no boot) b/c of a network driver compatibility problem.
I was among those afflicted.
Ended up having to do a factory restore then (over 3 years ago) and promptly, completely (MCPR.exe, etc) removed all traces of McAfee from the system.
Have been using KIS since then (2011, then 2012 and then 2013, always a clean upgrade).
Have been running KIS2013 (on all 3 boxes) since December 2012 (have not yet updated any rig to 2014 version).
SOOOOOOO, a long way of saying I don't think there are any traces of McAfee left KIS (KIS would never have installed or run correctly, if there had been).
I also run MBAM PRO on all 3 rigs (have done so for > 3 years) without issue; and I had disabled MBAM realtime protection will all of the recent Windows Updates attempts on this box.

If the install fails in a normal boot, then installing from a Clean Mode boot has been known to work on occasions, if the cause is interfering software.

Shall I try that for one of the patches, if the manual d/l & install in normal mode doesn't work?
Or should I just quit when I get the first error message, to avoid messing things up?

I'm reasonably sure that unplugging the printer won't cause problems later - and may be a good idea, since all the problem updates are related to USB drivers. (Hopefully, the Clean Mode boot would also do this - but some divers hook into the system at a very early stage, so you may need to try both)

OK, I'll think about it overnight.
It is the only 1 of the 3 rigs connected to the old HP printer locally via USB (the LT connects wirelessly and the main production desktop uses a different local printer).
But that might all be a coincidence.
I'm growing a bit fearful of creating new problems, e.g. failure to recognize it or failure to print to it after disconnecting it to troubleshoot.

I gather the NATIVE Windows troubleshooter applet is not helpful?
Or the online MS Windows Update Fixit?

OK, gotta take a break before I do something dangerous....

Will be back later or in the AM, weather-permitting.

THANKS!!!!

 

[NoelDP]

McAfee can cause all sorts of strange errors even after uninstall - but the MCPR tool does get most of the residuals out (it may be worth running it again, now that it's been updated, just in case they forgot something at that time)


In my experience, most of the standard MS Fixits for this sort of error are as much use as a chocolate teapot in a foundry.

If the first update 2529073 fails in Normal boot, try this...

Boot to a Clean Boot, and try again (does the error change?)
if it still fails, go back to Normal Mode, and unplug the printer and try again - does this help?
If it still fails, try Clean Boot again (with the printer still unplugged)

note the error message every time - if it changes, we need to know!
If it still fails, please run through the http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html again, and post the full data set again, and I'll see if I can make any sense out of it - also post the c:\Windows\windowsupdate.log file

 

[MoxieMomma]

Hi, Noel:

I haven't forgotten.
Have been offline for work, etc.
(On my unaffected laptop at the moment.)

Hope to tackle this later today or tomorrow...

Thanks,

MM

 

[adi518]

So there we go... searching of these annoying KB(s) and failing to install brought me here.

Now, not only they failed to install, something else happened during the process and now I get a "failure to configure windows updates" msg when trying the new "windows updates cleanup" option from the disk cleanup wizard.

The "fixit" apps or wu troubleshooter.. none of these help. It's a new screw up on behalf of microsoft.