How to fix Windows Update error 80070011

When updating my freshly installed Windows 7 on my Eee PC 901 I stumbled upon the 80070011 error when trying to install KB974431. I did manage to find a solution to the problem, and since it was a bit tricky to find, I figured I should post it here, hoping that anyone that has this problem in the future will have an easier time finding the solution than I did.

UPDATE: Apparently this solution will not work in Windows 8! If you know of a solution, why not post it in the comments?

The cause of the problem is that you might have junctioned your Program Files directory to another hard drive in order to save space (that’s what I did – if you haven’t done anything like this to your Program Files directory, this fix might not work for you), but this update still wants to install to the default path in C:.

Luckily, the fix is only a regedit away. Now, I guess I should mention that editing the registry might cause problems if you edit the wrong things, that you should only do it if you feel comfortable and that I don’t take any responsibility for any potential problems. I hope I got that right, I’m new at writing posts like this.

The solution:

  1. Open the registry editor by going to Run and typing in regedit
  2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
  3. Edit the ProgramFilesDir and CommonFilesDir entries so that they point to the actual location of your Program Files and Common Files folders (most likely just change the drive letter from C: to D:)
  4. Close the registry editor, KB974431 should now install without any problems

Thanks to LionelHutz at the EeeUser Forum for the solution!

34 thoughts on “How to fix Windows Update error 80070011

  1. Thank you alot. I have been searching a solution to this error. I have googling for weeks now. This really helped to my error. Im really gratefull you shared this info with us. Again, THANKS!

    – Peter

  2. Thank you so much!! I’ve been struggling with this problem for months, today I thought to Google again and this page was hit #1! Solved the problem immediately!!

  3. Holy crap it worked. As a follow up, I run a 64 bit system and i changed the entries for Program Files and Program Files (x86). Actually, I went ahead and changed ALL the entires in Program*Dir* and Common*Dir* (on my system, that was 6 keys in all) in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion key/folder/whatever to point to my D drive.

  4. Thanks a million ! I have actually symlink’ed (or junctioned) all my Programs* and Users* locations out of my SSD (where Windows is) to a RAID array. I changed ALL the dirs from C:\* to D:\* and Voila, no more update issues.
    Brilliant :-)

    1. 24October 9, 2012 at 7:01 pm151Great review Joe. I love the game but I agree there needs to be more ctiuomizatson. The ctiuomizatson options they added in this one are appreciated but if they aren’t going to develop the characters then they might as well go all out and give us full ctiuomizatson.ce

  5. Thanks!
    I have had this problem for at least a month now, Windows Update couldn’t install KB2423089, KB2419640, KB2416400, and KB905866.

  6. The same values are also present in
    “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion”
    for the 64-bit version.

    So it’s probably a good idea to change those as well.

  7. Oh, and for those that did the same for their User folder, these are the locations for the keys to edit:

    HKEY_CURRENT_USER\Volatile Environment
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\[Profile Code]
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\[Profile Code]
    HKEY_USERS\[Profile Code]\Volatile Environment

  8. Sorry, the third one was supposed to be:

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\ProfileList\[Profile Code]

  9. This is excellent! Thanks!

    A quick question: does this affect installs? The whole point of me not creating a D:\Program Files manually, and instead junction-pointing it away, is I have other programs that don’t like to recognise anything but the original C:\Program Files path.

    In short: are new installs going to read that key, too?

    1. I think properly configured installers (i.e. those that don’t just have “C:\Program Files” hardcoded in them) will do that, yes. I no longer have a machine where I have done as I wrote in the post (got a new Eee with a proper harddrive, put Linux on the old one) so I cannot check.

    1. 25October 30, 2012 at 3:55 pm1eeDuring the first game there was a hack that allowed for mutiplle things. The first game was also not on Steam and could be hacked easier. It just seems whom you was playing with was using one of the hacking tools and cheated with invincible shields. Know where the items came from or they were hacked in. Don’t blame the game for the problem but try again without those items and possibly not with that person but with others that you know aren’t cheating too badly.ce

  10. I see a lot of interesting posts on your blog. You have to spend a lot
    of time writing, i know how to save you a lot of time, there is a tool
    that creates unique, google friendly posts in couple of minutes, just search in google – k2 unlimited content

  11. I read a lot of interesting posts here. Probably
    you spend a lot of time writing, i know how to save
    you a lot of work, there is an online tool that
    creates readable, google friendly articles in seconds, just type in google – laranitas free content

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>