Windows 7 SDK Setup: common installation issues and fixes


This post describes common installation problems with the Windows SDK for Windows 7 and .NET Framework 3.5 SP1 (released August 2009), and workarounds for each issue. The Windows SDK for Windows 7 is available for download in both ISO and Web Setup format.  Web setup allows you to install a specific subset of the SDK you select without having to download the entire SDK.  The DVD ISO setup allows you to download the entire SDK to install later.



Error:



During the installation of Windows SDK you receive an error similar to


An error occurred installing the Microsoft Windows SDK for Windows 7 package. Error: A file that is required cannot be installed because the cabinet file.


Or


Cabinet file does not have correct format


Cause:


This error usually occurs when you have a bad download of SDK Components or corrupted files.


Solution:


Running the Windows SDK web setup on some connections can sometimes have issues when downloading the files.  We recommend that you clear the %temp%\sdksetup directory and retry your web setup. If that fails, switch over to the ISO setup for the Windows SDK. 


For Windows 7 SDK please refer to the download page here http://www.microsoft.com/downloads/details.aspx?familyid=71DEB800-C591-4F97-A900-BEA146E4FAE1&displaylang=en



Error:



When using Web setup to install Windows SDK, you might receive an error similar to


“Unable to find the file SDKSetup.cab at the installation source.  The most likely…”


clip_image002



Cause:


This error usually indicates a problem with underlying proxy issues or problems with network connection.


Solution:


Verify your network connection and try to install the SDK again. If the problem persists, download the ISO instead of using the Web Setup.



Error:



During the Windows SDK installation you encounter an error similar to


“A problem occurred while installing selected Windows SDK components.



Installation of the “Microsoft Windows SDK XXXXXX” product has reported the following error: Fatal error during


Installation.”


Cause 1:


You are installing Windows SDK to a non fixed physical hard drive like a RAM/USB hard drive.


Solution:


Please change the install location of the Windows SDK during install options and install Windows SDK to a fixed physical hard drive.


Cause 2:


Network Connection is lost during installation when using web setup.


Solution:


Re try the Windows SDK installation and switch to ISO install if the problem persists.


Cause 3:


User cancelled the installation


Solution:


Reinstall Windows SDK either from Web Setup or ISO downloads.



Error:



During an attempt to install Windows SDK you receive an error similar to


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.


Cause:


This error usually occurs when you have a corrupted Document Explorer installation.


Solution:


Uninstall the document explorer and re try the Windows SDK Installation.


If uninstalling Document explorer fails with errors similar to “Unable to open key” please refer to the solution explained here to uninstall Document Explorer.



Error:



When installing using an ISO download you receive an error similar to


“Setup could not find the file WinSDK_amd64\WinSDK_amd64.msi at any of the specified source locations”.


Cause:


This problem usually occurs when you are installing from an ISO build for a different architecture.


Solution:


Windows SDK now have different ISO’s for different architectures. Please download the correct ISO based on your system platform and architecture type.



Error:



An attempt to install Windows SDK might fail with the following error


A problem occurred while installing selected Windows SDK components.
Unknown product: {E28FB85C-8E3E-4E12-B1E6-58A3AFC0AFB4}
Parameter name: productCode


Cause:


Document Explorer has shared component dependencies which break if you delete VS 2008 or Windows SDK files/registry entries manually. If these Files/Registry entries are deleted manually, Document Explorer installer will not be able to access its installer components.


Solution:


Uninstall Document Explorer and retry installing Windows SDK. If you are experiencing problems uninstalling Document explorer please refer to the blog post here http://ctrlf5.net/?p=184.



Error:



An attempt to uninstall earlier Versions of Windows SDK may fail and Windows SDK setup reports error similar to


Unable to find required source files in any of the source locations”.


Cause:


Some earlier versions of Windows SDK like the Windows SDK for Windows Server 2008, require source files to be able to uninstall the SDK. Windows SDK for Windows 7 does not require the source file to be able to uninstall.


Solution:


1.       Download installer cleanup utility from http://support.microsoft.com/kb/290301


2.       Select All Windows SDK related packed with the version number you are trying to remove.


a.       Also select VCRedist and Document Explorer packages with the Windows SDK Version number. Do not select VcRedist/Document Explorer packages that have a different version number


b.      Also Select Windows SDK .Net Development tools (It has .Net version number, something like 3.5.XXXXX)


3.       Remove the selected packages


With this method, you will remove the installer cache, but the physical files remain on the disk. These will mostly get overwritten by the latest SDK but the behavior is not guaranteed.




Error:



When installing Windows SDK, you receive an error similar to


Unable to install Microsoft Visual C++ (error 1935)


Cause:


Usually this error occurs when files required by the installer are in use. Most probably the mscoree.dll is in use.


Solution:


Close all the application that are already in use and try the Windows SDK Installation again.



Finding Errors from the SDKSetup log:



On each install and uninstall session, SDKSetup creates a descriptive log in the System %temp% folder. (Usually it is C:\Users\UserName\AppData\Local\Temp). When an error occurs during the Windows SDK installation or un-installation, a more descriptive error message is logged towards the end of the log file. The current log file is named similar to SDKSetup_7.0.7000 1800.log and changes based on the Windows SDK you are using. You can also search for “error” within the log to verify if there are another errors during the installation. Ignore messages similar to ‘ErrorDialog = ErrorDialog’ and “Error Status: 0”.


Nanda Lella
Software Development Engineer
Windows C++ & SDK Team


Send your thoughts to the Windows SDK Feedback alias.  Tell us how you use the SDK and what we can do to improve your development experience.


The MSDN Windows SDK Developer Center is the place to find resources and links to Windows SDK products, release notes, technical articles, and more.

Comments (21)

  1. jmealing says:

    The web setup doesn’t have the x86 libraries in it. Only the IA64 and x64 libraries. Neither one has the qedit.h file or interface. The qedit exists in the Windows SDK V 6.0A, and perhaps previous versions. Unfortunately, neither V6.0A no the original DirectShow downloads are visible – at least to me.

  2. MSDNArchive says:

    Libraries to support for all 3 platform architectures (X86, X64 and IA64) are installed by default.  The X86 libraries install directly to the Program FilesMicrosoft SDKsWindowsv7.0Lib directory.  There is no X86 subfolder.  Can you check your install log to ensure that SDK installed correctly?

    Windows SDK v6.0a is the set of Windows SDK resources that install in-the-box with Visual Studio 2008.  If you don’t have VS2008 on your computer you will not see the v6.0a components – Windows headers, libraries and tools.  If you do have Visual Studio 2008 installed on your computer you will see the v6.0a resources installed to this folder by default: Program FilesMicrosoft SDKsWindowsv6.0a.

    Karin Meier

    Windows SDK

  3. wsdkblog@microsoft.com says:

    Jmealing, qedit.h no longer ships in the Windows SDK.  The qedit.h file included with earlier versions of the Windows SDK is dependent on some header files which previously shipped with the Microsoft DirectX SDK, such as dxtrans.h.  Newer DirectX SDKs do not include these files.  Microsoft is aware of this issue, and the recommendation for now is to install and use the August 2007 DirectX SDK, which does include all files needed to build qedit.h.  To install the August 2007 DirectX SDK, go to http://www.microsoft.com/downloads and search All Downloads for "dxsdk_aug2007.exe".

    Karin Meier

    Windows SDK

  4. pariuri says:

    I receive "An error occurred installing the Microsoft Windows SDK for Windows 7 package. Error: A file that is required cannot be installed because the cabinet file" but the solution you post is not working for me. What should i do?

  5. wsdkblog@microsoft.com says:

    pariuri, you should delete all files intalled to the %temp%sdksetup directory and click on the download button again.  If you’re still having problems you should use the ISO setup for the Windows SDK found here:  http://www.microsoft.com/downloads/details.aspx?familyid=71DEB800-C591-4F97-A900-BEA146E4FAE1&displaylang=en

    If this doesn’t work, please let us know the exact error you are seeing.  Thanks!

    Karin Meier

    Windows SDK

  6. pariuri sportive says:

    I have tried over and over to get the Windows 7 SDK installed and it fails every time. I had an older version of the Windows 7 SDK (at least I think it was older) and I wanted to uninstall it first but its uninstaller kept saying it couldn’t do it because I have to uninstall Windows 7 SDK first but, of course, this is exactly what I was trying to uninstall! I then tried deleting all trace of the SDK using regedit and deleting its files. This enabled me to get it out of Control Panel/Programs and Features.

    After all that I thought I was ready to reinstall the Win 7 SDK. I then tried the web version of the installer and it complains that some cab is missing before I even get a setup window appear. So, I tried the ISO and it seemed to do a bit better. However, every time I start the setup proper, it stalls with:

    A problem occurred while installing selected Windows SDK components.

    Unknown product: {50E3D23F-F6A5-33C5-B8C4-331D3CB03EC4}

    Parameter name: productCode

    I have tried restarting with system services only and I get the same result. I am on Vista 64. I have installed VS 2008 with SP 1. I have read the troubleshooting page but it does not offer any help for this situation. What do I do?

  7. poker player says:

    @pariuri sportive, this is strange, i am running on my laptop windows 7 from a while and i had never problems.

    what is your computer configuration?

  8. stefan popa says:

    Congrats for qedit.h problem which is ignored version after version… what can I say more…

  9. I have this problem too

  10. If you are installing Windows 7 or new to Windows 7 check out The ABCs of Windows 7 which will help –

    ninjarabbits.blogspot.com/…/windows-7-abcs.html

  11. dd2 says:

    A problem occurred while installing selected Windows SDK components.

    Unknown product: {4B509F1E-BEA7-3D0E-BE94-3BBF85E8D698}

    Parametername: productCode

    Please attempt to resolve the problem and then start Windows SDK setup,

    Installation Failed, unable to clear and install sdk while existing vs2010.

  12. dd2 needs help also from Mr Zander - Vs2010 Developer says:

    Reinstallation does not help, anyway unable to install windows sdk 7.1 on windows 7 and vs2010.

    Could not find a tool to remove sdks, PrgMicrosoft SDKsWindowsv7.0A was installed via vs2010 uncomplete and the installation of Version 7.0A is hidden in software – installations not removable!!!

  13. johnylog says:

    Hello guys,

    Do you encounter errors while deleting files in Windows? I'm here to provide a solution. I've been reading several threads on this topic on different forums where computer users were asking about this popular error "The filename you specified is not valid or too long".

    My research helped me to find a tool for you guys.

    Its LONG PATH TOOL, a very easy to run but highly powerful software.

    Follow the link to read more about this error.

    http://www.longpathtool.com

  14. Steve Lessard says:

    Another cause of the "Installation of the "Microsoft Windows SDK for Windows 7" product has reported the following error: Please refer to SamplesSetupHTMLConfigDetails.htm document for further information." problem could be a previous install of Visual C++ 2010 Redistributable. After I uninstalled that I was finally able to successfully install  Windows SDK 7.1.

  15. Nazanin says:

    Hello,

    I am sure that I was successful in installing Windows SDK, but when I try to run mex -setup in MATLAB, I still get the following error, can anybody help me with solving this issue?

    (I have windows 7 x64)

            Could not find the 64-bit compiler.  This may indicate that the  

            "X64 Compilers and Tools" or the Microsoft Windows Software  

            Development Kit (SDK) is not installed.  To build 64-bit MEX-files  

            Microsoft Visual C++ 2008 Express Edition requires that these two  

            packages are installed properly.

  16. The_Assimilator says:

    All I wanted was WinDBG, so I downloaded and ran the SDK web setup which failed repeatedly. The web setup is one of the biggest pieces of junk MS has ever shipped, please replace it with something that actually works. "Download the ISO" IS NOT A SOLUTION TO A BROKEN PIECE OF JUNK. If it doesn't work, don't offer it as an "option"!

    And on that topic, thanks for making the SDK ISO download require authentication cookies. As I found after pausing my download at 93%, attempting to resume it at a later stage fails because the cookies used are no longer valid.

    You write some of the best tools in the world, but people can't get them. Keep up the good work.

  17. dis says:

    same issue. Doesnt work, and all solutions neither.

  18. bahar says:

    I received this"Setup could not find the file WinSDK_amd64WinSDK_amd64.msi at any of the specified source locations”. but your solution confused me! which ISO should be dowmload?

  19. Omar says:

    Thanks Steve Lessard, your solution worked!

  20. Andreas says:

    If you are still having issues try to remove

    either

    Microsoft Visual C++ 2010 x64 Redistributable

    or

    Microsoft Visual C++ 2010 x86 Redistributable

    depending on the Version of the SDK you are installing prior to SDK installation. SDK tries to install an older version but the VCRedist_xxx.exe installer fails because a newer version is already installed (typically some 10.0.4xxxx version).

  21. Elzo says:

    My installation of the SDK 7.1 seems to be correct but I still having this frusting error when buildin a projectt :

    C:Program FilesMicrosoft SDKsWindowsv7.1includesdkddkver.h(251): fatal error C1189: #error :  NTDDI_VERSION setting conflicts with _WIN32_WINNT setting

    I use Microsolft Visual Studio 2010 and MS SDK v7.1…Please can you help me…