• Anonymous Joe Blizzard
    11 May 2011 3:20 AM

    Tried to post this earlier, but it didn't take. Noticed after failing at step 6 that KB976932 showed up in the installed updates under programs and features. Pretty sure it wasn't there before. When I tried another machine I looked at installed updates before starting and noted that it had 91 updates listed and KB976932 wasn't one of them. I got the same not valid error on the second machine, but now it lists 16 updates with KB976932 at the top of the list.

  • Kelvin Aston Kelvin Aston
    11 May 2011 10:33 AM

    @Nick Whittome

    Sorry to stick my oar in but looking at your log I don't think that you've adjust the name of the package correctly. You've changed the x86 to x64 but I believe it should be amd64. So the dism command for you would be...

    dism /online /remove-package /packagename:Package_for_KB976932~31bf3856ad264e35~amd64~~6.1.1.17514

    Not sure what's happening for Brenda on her x86 machine(s) though as I don't have any torn x86 boxes to try it on.

  • Kelvin Aston Kelvin Aston
    11 May 2011 10:49 AM

    @Brenda

    One thing you might try is running DISM /online /get-packages and look for the package for KB976932. Compare the name of the package with what you're typing at the command prompt to see if it matches as it may be slightly different. For instance, I've seen an extract from a log where the package name contained "...ad364..." rather than "...ad264...". I presume that this was because it was a Finnish machine.

  • Kelvin Aston Kelvin Aston
    11 May 2011 1:01 PM

    I'm just trying this out on one of my few remaining torn PCs.

    Step 6 also initially failed for me as it would appear that by following these steps I've ended up with the ad364 package rather than the ad264 package. No idea why but there you have it. Changing the dism command appropriately got it to work. I'm currently reinstalling SP1 and all seems to be well.

    @joscon

    Thought it might be worth noting that following steps 1-6 rolls back the ati folder to the previous version. As I think I've said before I don't actually have any ATI hardware in use in the machines but the correct (pre SP1) folder seems to be a dependency of getting the install completed. Glad that you've come up with a more graceful way of getting it rolled back.

    Also, I don't wish to appear as confrontational but I feel that I have to point out that torn PCs were not only caused by using the unsupported pending.xml hack. The SetupExecute registry edit from this blog post blogs.technet.com/.../error-0xc0000034-during-service-pack-1-installations-for-windows-7-and-windows-2008-r2.aspx also left my machines in a torn state and certainly felt, at the time it went up, that it was being "recommended by Microsoft".

  • Anonymous Brenda
    11 May 2011 1:21 PM

    @ Kelvin

    Going to try your suggestion.  will let you guys know!

  • Anonymous Brett
    11 May 2011 1:35 PM

    I'm confused. I'm getting the 0xc0000034 error after SP1 install and can't do a system restore. I haven't tried the pending.xml workaround. Should I try it or not?

  • joscon [Microsoft] joscon [Microsoft]
    11 May 2011 1:39 PM

    @Brett;

    No, you should be usng the script mentioned in the KB (reported on a prior post).

    @Everyone else;

    We're looking into what's causing the errors you're seeing in step 6.  It's worked for us internally so we're investigating.

  • Anonymous Brenda
    11 May 2011 1:42 PM

    My file name was different.  

    :Package_for_KB976932~31bf3856ad364e35~x86~~6.1.1.17514

    ad364 instead of 264

    ran fine once i changed that.  rebooting now and will try reinstall of Sp1

  • joscon [Microsoft] joscon [Microsoft]
    11 May 2011 1:43 PM

    @Kelvin;

    No worries man.  I appreciate the input here.

  • Anonymous Brett
    11 May 2011 1:59 PM

    @Joscon

    You say do the script, not the pending.xml workaround, I'm reading kb 975484 it seems the pending.xml and script are one and the same? Is this the right kb i should be looking at? Thanks.

  • Anonymous Brenda
    11 May 2011 2:10 PM

    Got Service Pack installed... successfully! and i see it in Installed Updates in Control Panel. Sweet.

  • joscon [Microsoft] joscon [Microsoft]
    11 May 2011 2:34 PM

    @Brett, yes, thats the proper KB.

    @Brenda; great!  thanks for letting me know.

  • Anonymous Joe Blizzard
    11 May 2011 2:48 PM

    @Brenda: Did you happen to notice if the service pack showed up in control panel after step 5? That's what I'm seeing.

    @joscon: I haven't tried a modified step 6 yet, being somewhat reluctant nowadays to proceed without something approaching an official Microsoft stamp of approval.

  • Anonymous Brenda
    11 May 2011 2:56 PM

    Yes it shows in control panel as being installed.  Before it didn't.

  • joscon [Microsoft] joscon [Microsoft]
    11 May 2011 3:05 PM

    @Joe; I've updated the package name to be (364) instead of (264), please use that and let me know the results.  Maybe I fat fingered it but I know when I was working on this I had the right package names.  However in rechecking my main tools machine here, my package name is 364 so thats probably my fault.

    Let me know your results and thanks for bearing with me.

<>