I no longer need your log files, but I do need to ask you if I can set up a support case for you.

Email me at susan-at-msmvps.com

Recently there was an issue where Win7 sp1 was put on WSUS and then due to default settings in SBS, it was automatically applied. Depending on if it was installed with other updates, in some cases it failed miserably leaving you with a “C34” error (see blogs below for references).

Many of you then googled and found references to editing the pending.xml file which got you immediately back in business, but put the system in what is now called a ‘torn’ state, i.e. 1/2 rtm, 1/2 sp1.

To get a feel of the true impact I’d like to find out the following. Can you please email me at susan-at-msmvps.com with the following information?

How many PCs under your control were impacted?

How many MS support cases did you open?

Thank you in advance for this info.



2 Responses to How many of you saw "C34" errors in your deployment of Windows 7 sp1?

  1. Dean says:

    “Many of you then googled and found references to editing the pending.xml file which got you immediately back in business”

    That’s why firing up Google and jumping in without thinking first can get you into a lot of trouble. In a bad situation the very first step should be not to panic. Keep calm. Don’t take the first answer that comes along. Use your brain and process the information you get through it to see if it makes sense. Should you do what it tell you to do ? Most of all look for information from the one source that has the most experience with the product. Microsoft.

  2. Paul says:

    @Dean – and what do you do when you have 25% of your company’s users unable to do their job because Windows is down. You look for the quickest solution to get your users back to work. I am all for trying to do correct forensics to discover the issue but sometimes that isn’t possible when users can’t print payroll checks. I think we’re all aware a solution on a random forum site will cause problems but it did get our users up and printing checks. I am sad that the scale of problem made it’s way through WSUS after the lengthy SP1 vetting process. Makes it less trustworthy.