KB2862335 error 80070057 causes other patches to fail

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

MoxieMomma said:

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!

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.

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.

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.

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!

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.

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.

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?

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

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.