Windows SDK Configuration Tool May Report an Error When OS Display Format is not English


This post describes a problem with the Windows SDK Configuration Tool, which is used to set the version of Windows SDK headers, libraries and tools you wish to build with in the Visual Studio or Windows SDK build environments.  


Issue: When you launch the Windows SDK Configuration Tool on a system which has Visual Studio 2005 or Visual Studio 2008 and the display format of the operating system is not English, an error may be thrown: “Your system does not have Visual Studio 2005 or Visual Studio 2008 installed.”


This error will occur when the OS is Windows 7, Windows Vista, or Windows Server 2008, and Visual Studio 2005 or Visual Studio 2008 is installed. This error can be reproduced in the Windows 7 SDK and the Windows Server 2008 SDK. 


Cause: With some non-English operating system display formats, the Windows SDK Configuration Tool is unable to parse the version number of Visual Studio as written in the registry.


Solution: There are two workarounds to the problem:


(1) Use the command-line version of Windows SDK Configuration Tool to change to the version of the Windows SDK you wish to target.  For example to target the Windows 7 SDK go to the Windows SDK prompt by Clicking All Programs -> Select Microsoft Windows SDK v7.0 -> Select CMD shell. At the Windows SDK command prompt, type “ WindowsSdkVer.exe -version:v7.0 “ [without quotes]


(2) Change the OS Display Format to English (United States). Go to Control Panel and navigate to your Regional and Language Options. On the Formats tab ensure English (United States) is selected. You should now be able to use the Windows SDK Configuration Tool to target the appropriate build environment. Note: once you have changed the target you may return your OS Display Format to its original setting.


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.


Window SDK Team


 

Comments (13)

  1. VSChawathe says:

    It’s not just the config tool. Try setting language to Marathi with Indic script enabled from regional options in control panel.(that’s official language@India’s financial capital M’bai in Maharashtra state) Things like the VC++ runtime library, most MS VS compilers report the most absurd errors…

  2. Igor says:

    For SDK 7.1, the WindowsSdkVer.exe is inside setup dir. So yuo will have to type:

    setupWindowsSdkVer.exe -version:v7.1

  3. kamilf says:

    This error will also occur  when the OS is Windows XP x64.

  4. kamilf says:

    This error will also occur  when the OS is Windows XP x64.

  5. Marc says:

    Doesn't mention if you have visual studio 2010 installed you get the error too. command succeeds using command prompt. I got this error after upgrading from 2008 where running the exe outside the cmd prompt worked previously.

  6. Robert says:

    Tried both workarounds.

    By changing regional settings the graphical tool worked better, but did not find VS2010 (Express), which I want to use! So I could only select VS2005 and VS2008, which in fact I do not use any more.

    By using the command line tool I still had the same problem. It associated automatically to VS2008, which is of no use to me. But this association was not even visible in  the graphical tool.

    Now what?!

  7. Robert says:

    Addition.

    There does not seem to be a way to do the setting 'by hand' as "WindowsSdkVer /?" does not show an appropriate parameter.

    Usage: WindowsSdkver.exe <options>

    Options:

     -? Usage Scenarios – this message.

     -current Show currently selected version.

     -q Quiet operation – Can only be specified with -version:value.

     -version[:value] Set WinSDK version.  If no version is specified, show all.

  8. Robert says:

    Another addition.

    I am already trying on v7.1!

  9. Robert says:

    Here is an explanation which seems to make all these efforts futile.

    Confusing to say the least!

    Annoying is more close to the truth.

    connect.microsoft.com/…/winsdk-7-1-net-4-windows-sdk-configuration-tool-fails-with-only-vs2010-installed

    Gepost door Microsoft op 4-6-2010 om 10:16

    Hi,

    Thank you for pointing this out. In this case, all of the headers and libraries and tools that shipped with the Win 7.0 SDK are also in VS 2010. It is desired that the SDK Configuration Tool doesn't work with VS 2010.

    If you have any further questions, or comments, please let me know chrishu at microsoft dot com.

    Thanks,

    Chris Hubbard

    Windows C++ SDET

  10. RainerHH says:

    SDK 7.1 / W7/64

    setupWindowsSdkVer.exe -version

    (without version) shows the installes verion, by me 7.0A

    setupWindowsSdkVer.exe -version:v7.0A works, verion successfully registerred

  11. RainerHH says:

    continues:

    my Installation  SDK 7.1, W7/64, VS 2010

    as I wroted: registerred successfully

  12. Niello says:

    Thanks, helped a lot. Hope some day you will be able to fix it. As for now, workaround works 🙂

  13. Ezof says:

    After succefull installation I build my project and i get this frustring error :

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

    my Installation  SDK 7.1, W7/64, VS 2010

    Can you help me please???