KB2862335 error 80070057 causes other patches to fail

NoelDP said:

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

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.

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>

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.

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

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!

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.

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?