Skip to content


Installing Visual C++ 2010 and Windows SDK for Windows 7: offline installer and installation troubleshooting

I spent days (not full time, eh ^^) figuring out how to do this one. So here are pointers for installing Visual C++ 2010 Express (just pointers because I didn’t keep it in the end – so basically I’ll just give you the offline installer), and the most detailed Windows SDK installation troubleshooting guide I can think of, after trying every posted solution and ending up finding out a new (yet simple) one.
NB: all this was done on Windows 7 x64 Enterprise.

Getting the offline installers

For Visual C++ 2010 Express, you can’t get an offline installer without downloading the full Visual Studio 2010 Express ISO. So, well just go there and pick All – Offline Install ISO image file. You can then just mount the ISO (using a tool such as Daemon Tools), or extract it (for instance 7-Zip can do it) into some directory, then browse to the VCExpress folder and run the setup there. To save disk space, you can just keep the C++ folder (VCExpress) and discard the rest (around 380 MiB if compressed using 7-Zip vs 693 MiB for the full ISO).
For the Windows SDK, the offline installer can be found there (Microsoft Windows SDK for Windows 7 and .NET Framework 4 (ISO)). Also, note that the “web” installer is (as of today) no more up-to-date than the offline one. Note that you have to choose between 3 ISOs: GRMSDK_EN_DVD.iso is for x86, GRMSDKX_EN_DVD.iso is for x64, and GRMSDKIAI_EN_DVD.iso is for Itanium. Then, same story as for Visual Studio: either mount the ISO or extract it somewhere.

Solving the most useless error message I’ve ever seen

NB: if you’re in a hurry, just skip until the “Summary of possible solutions for this Windows SDK installation problem” section.

When installing the Windows SDK, I got stuck by the following error message:

A problem occurred while installing selected Windows SDK components.

Installation of the “Microsoft Windows SDK for Windows 7″ product has reported the following error: Please refer to Samples\Setup\HTML\ConfigDetails.htm document for further information.

Please attempt to resolve the problem and then start Windows SDK setup again. If you continue to have problems with this issue, please visit the SDK team support page at http://go.microsoft.com/fwlink/?LinkId=130245.

Click the View Log button to review the installation log.

To exit, click Finish.

As you can see, there is no real error message there, plus the file referred to by the message is nowhere to be found. At first I tried searching online for solutions, here is what I found (NB: none of those worked for me, but maybe they will for you, as the error message is likely a generic error which can be triggered by quite a few very different causes):

  • On CTRL+F5, they suggest to run regedit then change the ownership of key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components (and its subkeys) from SYSTEM to the Administrators group (see the link if you need more details on how to do this).
  • On that same site, they say that if the previous method doesn’t work, you can also make sure that your TEMP and TMP environment variables all point to the same folder (so in my case, and probably yours too, it means deleting your user-specific TEMP and TMP variables). Once again, check out the above-mentioned link if you need more details on how to perform this.

Those fixes didn’t work for me, and I realized I could check the installation log. Which indicated what component was screwing everything up:

10:16:59 06 April 2011: F:\PROGRAMMING\Microsoft SDKs\Windows\v7.1\Setup\SFX\vcredist_x64.exe installation failed with return code 5100
10:17:15 06 April 2011: [SDKSetup:Error] Config_Products_Install: Installation of Product Microsoft Windows SDK for Windows 7 (failed): Please refer to Samples\Setup\HTML\ConfigDetails.htm document for further information. Stack: at SDKSetup.Product.ConfigureRelatedSfx() at SDKSetup.Product.ConfigureNewProduct(ManualResetEvent CancelEvent)

So… vcredist_x64.exe is the culprit then. (Note that if your installation log doesn’t indicate the same error, then probably you can stop reading now as my fix will most likely not work in your case). As previously, I first tried to search online for solutions. The only thing I found was this, basically saying “make sure the Windows Modules Installer service is up and running”. Mine was already.

Finally, I thought why not try to install that vcredist_x64.exe myself, stand-alone. Vcredist_x64.exe is the name taken by basically every Microsoft Visual C++ Redistributable Package (x64): any version of it. So I first tried the latest one, Visual C++ 2010 SP1 Redistributable Package (x64), which offered me to either repair or remove. I picked repair. I tried installing the Windows SDK again, still no success. I thought maybe the vcredist aren’t cumulative, so tried to install the previous version, Visual C++ 2010 Redistributable Package (x64)… and it failed, saying that I already had a more recent version (which was true since I had SP1). But that error message puzzled me, as it really didn’t look graceful: it felt more like a real failure rather than a “you already have a better version, no need to add this one so all done”. And so I decided to uninstall my Visual C++ 2010 SP1 (I just reran the installer previously mentioned and this time picked remove instead of repair). Note that to be able to uninstall VC++ 2010 SP1 I had to kill parts of my Catalyst drivers (the AMD Fuel service as well as CCC.exe (Catalyst Control Center:Host application) in the task manager).
With the Visual C++ 2010 SP1 Redistributable Package removed, I ran the Windows SDK installer again and it worked fine. It installed the Visual C++ 2010 Redistributable Package, which I updated then with its SP1. All working good now, hurray! :)
Note that the Windows SDK installs both the x86 and x64 versions of Visual C++ 2010 Redistributable. I didn’t have the x86 version already installed, but if you do my best guess is that you’ll need to remove it too.

Summary of possible solutions for this Windows SDK installation problem

  • Uninstall Visual C++ 2010 SP1 Redistributable Package (as of today this is totally mandatory to be able to install the Windows SDK) (both x64 and x86 if applicable)
  • Make sure the Windows Modules Installer service is up and running
  • Change ownership of HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components to the Administrators group (not sure if it’s really needed)
  • Make sure that all your TEMP and TMP environment variables (global and user) all point to the same folder (once again, not sure if it’s really needed… but it’s always good to have all temporary folders at the same place: easier to clean ;) )

Posted in programming.


91 Responses

Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.

  1. David Dernoncourt says

    No I don’t think the older versions were an issue when I wrote this post: I had a bit of everything installed, and the only version I had to remove was the 2010 redistributable, as far as I remember.
    But technically, if they upgraded 2008 or 2005 since then without updating the Visual C++ 2010 installer, I guess it’s a possibility that they cause trouble now…

  2. Chris Rojas says

    thank you!!!

  3. Excalibur says

    This DO solve my problem! Thank you!

  4. David Dernoncourt says

    Does, but you’re still welcome ;)

  5. Sigma says

    thank you :)

  6. Ruso_x says

    +1

  7. fliflaflex says

    i have tried some solutions before, but deleting “Visual C++ 2010 SP1 Redistributable Package” fixed the problem finally. Thanks!

  8. steppenwolf89 says

    awesome!!! It worked like a charm!!! We love you

  9. David Dernoncourt says
    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1
    
    Thanks, kisses to you too ^^ Feel free to drop a few bitcents
    there if you can ^^ 1KY8gS9B6pbSvdGgo1M9o1SSpNNxkGv1Zo
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v2.0.19 (MingW32)
    Comment: Using VisualGPG v0.1.2.0
    
    iQUcBAEBAgAGBQJQWiYUAAoJEGAcV4sYvqRCoNEn/0sq7Lnb53N5Pvgesm4L3740
    HSioWZ9+JrhDp6wAmjA9egqQpuoQQf2aNcBNZYNnU5HOg1D33EQW/sBEDx2MYM6Z
    773Cn8ZFYifrLS/ZNHF6Mt49ZdbM6dlC5ehus6F3ELvzM9rTO1dbpf2nEPQ6hAZu
    lcg5paoTOpbpiBMyNzJP/7Pt/1unLcb1zoJBo1IsEnTL/FAflbjdoL7YNG9dFBoY
    M1++PBusBL0rxe0vjVDFRpVoggAs+NhOdPTpMX0NQXtwkhgZMX8COsQKjNsxf7Nw
    8LC/hAsOvbrm+VFXo3DMd8tOE/cO14MbRwT/VblxoSc5wjo+iOba1N9IfrP+X14T
    Gsu9iUSPr472QULegGFbq874F3L1eCwW1TLBXzKBHTYrw+AI6/Qe/97U/+w/JRgS
    mDDNqUHfekEpiviDLV4gs+SnbAqxKfVwB0WdNnGc7uQpG5yP5Qo3yrNfEIWFiK6y
    9N98g6Gxlgf22pJlW2k3nwRiSsPriOlYpKdnZxRvMkSO537+eLEnbhznXamduTkc
    +f4ywahw8kQUA9mwXhCwfreFFqc/yZgIxzQ/4zkbGOUfXhtMNTvXmePdoikL6CdY
    4FVp9KCwDmrTg8mkAy0ojqvMDb+bN5mopmc9wwbc738x/plTRfsuysQ0OjbDTvOD
    XmbCLIZyd05iic+wljXNK+EOuHtFRuajuC2hdfeqxi0GwS4gu9kUis5IBLoXIGnD
    IbBBp6OyR5mrdw0PEpo+QwT9XAbwqwQrK0vUOyFyKlIU1f+2cQrGJ1C/LP/LHWUx
    VKt07wBx3vkS8fD9Lv77pTQiVjsjSickhZ2mlWYtERMU9opBLGGiQ1ZRZyxSo6tK
    Tsb88Ld2H+AEotqqGoJvRvrIG8+ebKVOqRT2quQ1+gOakJhVJgXpPOpDnkS+QLMK
    AUoakYq+pdU3R6k+S1veYx+a01ZiOpLBjW9UXdPXQPv/Fu7k49Liy50ICzJRKIXz
    Zdup5SlsBac07Gafz0LIOeAL5VtJkDM0AW4rdWHJHxDVv41KoiynM7f0hxpI4jIe
    Os4Ea/20uowAm9yFE22j8Db/a2idSp8nEYFpKZFtdbGJU2YGWwKjFwfuF37XZafC
    14kgyCcqsokjJpmR+9M3aziNzaHpDa/pduVcTxZcOjK2Ejz0JKX1XUa8uR0j35lO
    hrLVsadkA3FFxG9i/WxkV6mxXmOx8G3LRzGS3xgOcO8hOTG3E2SLlj4X6gvG3E/A
    ImFbhXQL8Ted9yotsEsq78Vm5LmCgFyiUa0j6mhboFvn792E9Id8vZRs05DQ13Oa
    IN0aPo24GRZ+Xw2LMj3fpfRZ6DsmoqvF7H6SXptPTiAQHXDypEDtZ6RIc4iTJxo7
    yJ1wvb+2/nCwHNumT757NLav4Hu8w+KKh1y2Un0rnINRlWi8H4ka7UbsG0J6qW0N
    HrgVGGbaRQKpid1t8PjHt8lYc+hD17j3wzffVn/hV1ddl1x7FSUCECkhvk7u4it2
    2n6iV/IHB0gZnobvdjjBEXvykfA6AEkIrL/GaXM+D1Kn1rxPm+/ccgK0fbXqzR9q
    juc4/qbVLUfj67NsuTTvYxwydmipAZ8JPZ+cSgoog+0EYEZXuAEHUJSLPaXi68Eb
    S+sAI7fexH+1/JnlnjdL7NeCFVhdH1lBN0r2HRCzWQB/5iCf+apu8XKip/nR5CaO
    iT3OrPQSxyo2ljL+I5P/
    =DpCA
    -----END PGP SIGNATURE-----
  10. TheRoSS says

    Just uncheck the option “install redistributables” upon SDK installation

  11. David Dernoncourt says

    lol, never noticed this one :D Maybe it’s a new option they introduced as a “fix”

  12. Anonymous says

    Hi there would you mind letting me know which webhost you’re working with? I’ve loaded your blog in 3 completely different web browsers and I must say this blog loads a
    lot quicker then most. Can you recommend a good web hosting provider at a reasonable
    price? Many thanks, I appreciate it!

  13. David Dernoncourt says

    I use both 1&1 and OVH.

  14. Franck says

    Great!

  15. Anonymous says

    Thanks

  16. Anonymous says

    Many thanks to this article :-)
    It worked for me by uninstalling the x86 variant.

    It’s a shame that Microsoft still has not learned how to develop useful error messages.

  17. binoy says

    how do i find if the windows modules installer service is running?
    i googled a little bit and found that the process for the service is trustedinstaller.exe, it wasnt running and i do not know how to start it, google wasnt hepful either
    how exactly do i get this service up and running?

    thanks

  18. David Dernoncourt says

    Hi,
    I don’t remember how I did that. Most likely you just go to services management (open the start menu and type “services”, you should get to the right place then), find “Windows Modules Installer” in the list, and check its status.

  19. Melissa says

    I think I love you!

  20. Mac&Me says

    This is the single most important webpage for everyone who attends my university! We all are given laptops with some preinstalled and preconfigured software as part of our school’s laptop program. So everyone who needs the SDK runs into this same set of problems.

1 2 3 4 5



Some HTML is OK

or, reply to this post via trackback.