{"id":3158,"date":"2018-11-09T20:00:46","date_gmt":"2018-11-09T18:00:46","guid":{"rendered":"https:\/\/mariusbancila.ro\/blog\/?p=3158"},"modified":"2018-11-10T23:30:21","modified_gmt":"2018-11-10T21:30:21","slug":"troubles-with-windows-sdk","status":"publish","type":"post","link":"https:\/\/mariusbancila.ro\/blog\/2018\/11\/09\/troubles-with-windows-sdk\/","title":{"rendered":"Troubles with Windows SDK"},"content":{"rendered":"

I recently installed a fresh copy of Visual Studio 2017 on a new machine and went on to build several projects some of them being VC++. The trouble was that I immediately run into a problem (actually the first problem was that MFC & ATL were missing because I forgot to check that in the list of Individual components so I had to install them separately). The problem was an error with a missing new.h<\/tt> header:<\/p>\n

1>c:\\program files (x86)\\microsoft visual studio\\2017\\enterprise\\vc\\tools\\msvc\\14.15.26726\\atlmfc\\include\\afx.h(62): fatal error C1083: Cannot open include file: ‘new.h’: No such file or directory<\/p><\/blockquote>\n

That happens on compiling the following piece of code in afx.h<\/tt>:<\/p>\n

#ifndef _INC_NEW\r\n\t#include <new.h>\r\n#endif<\/pre>\n
Searching for the new.h<\/tt> header releaved two locations:<\/p>\n
c:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Enterprise\\SDK\\ScopeCppSDK\\SDK\\include\\ucrt\\new.h\r\nc:\\Program Files (x86)\\Windows Kits\\10\\Include\\10.0.17134.0\\ucrt\\new.h<\/pre>\n
But looking at the location of the include directories in Visual C++ (from the expansion of $(VC_IncludePath);$(WindowsSDK_IncludePath);<\/tt>) I’ve seen only these:<\/p>\n
C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Enterprise\\VC\\Tools\\MSVC\\14.15.26726\\include\r\nC:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Enterprise\\VC\\Tools\\MSVC\\14.15.26726\\atlmfc\\include\r\nC:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Enterprise\\VC\\Auxiliary\\VS\\include\r\nC:\\Program Files (x86)\\Windows Kits\\10\\Include\\10.0.10240.0\\ucrt\r\nC:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Enterprise\\VC\\Auxiliary\\VS\\UnitTest\\include\r\nC:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\um\r\nC:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\shared\r\nC:\\Program Files (x86)\\Windows Kits\\8.1\\Include\\winrt\r\nC:\\Program Files (x86)\\Windows Kits\\NETFXSDK\\4.6.1\\Include\\um<\/pre>\n
None of the actual locations where new.h<\/tt> was present were in this list. That was because I had chosen to install version 10.0.17134.0 of the Windows SDK and no other version. However, my Visual C++ projects were targeting Windows SDK 8.1. It turns out that is in hard-coded in MSBuild that 10.0.10240.0 is used when targeting 8.1. Here is the relevant excerpt from c:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Enterprise\\Common7\\IDE\\VC\\VCTargets\\Microsoft.Cpp.Common.props<\/tt><\/p>\n
<!-- 10.0.10240.0 is the hardcoded checked-in version of uCRT that we use in case we target 8.1 SDK -->\r\n<TargetUniversalCRTVersion Condition=\"'$(TargetUniversalCRTVersion)' == ''  and ('$(TargetPlatformVersion)' == '8.1' or '$(DefineWindowsSDK_71A)' == 'true')\">10.0.10240.0<\/TargetUniversalCRTVersion>\r\n<UniversalCRT_PropsPath Condition=\"'$(UniversalCRT_PropsPath)' == ''\">$(UniversalCRTSdkDir)\\DesignTime\\CommonConfiguration\\Neutral\\ucrt.props<\/UniversalCRT_PropsPath><\/pre>\n
To solve this there are three possible solution:<\/p>\n
    \n
  1. Install the required 10.0.17134.0 Windows SDK. To do so, you need to run the Visual Studio Installer, select Individual Components and check it in the list.\n
    \"\"<\/p>\n
    Mind that this SDK requires an additional 3GB of disk space.<\/li>\n
  2. Change the targe version from 8.1 to 10.0.17134.0 or whatever else you have installed.\n
    \"\"<\/p>\n
    If you plan to do this and you work in a team with other developers and have dedicated build machines, etc. you need to coordinate so that everybody has the target version of the SDK installed, otherwise the build will run on your machine but not on others.<\/li>\n
  3. Manually alter the MSBuild user property files C:\\Users\\{user}\\AppData\\Local\\Microsoft\\MSBuild\\v4.0\\Microsoft.Cpp.<target>.user.props<\/tt> (where <target><\/tt> is Win32<\/tt>, x64<\/tt> and Arm<\/tt>) to overwrite the defaults. These files are initially empty and should look like this:\n
    <?xml version=\"1.0\" encoding=\"utf-8\"?> \r\n<Project DefaultTargets=\"Build\" xmlns=\"http:\/\/schemas.microsoft.com\/developer\/msbuild\/2003\">\r\n  <ImportGroup Label=\"PropertySheets\">\r\n  <\/ImportGroup>\r\n  <PropertyGroup Label=\"UserMacros\" \/>\r\n  <PropertyGroup \/>\r\n  <ItemDefinitionGroup \/>\r\n  <ItemGroup \/>\r\n<\/Project><\/pre>\n
    You can replace the empty PropertyGroup<\/tt> item with the following (this example is for x86, but you need to do the same with the appropriate paths in all the files):<\/p>\n
    <PropertyGroup>\r\n   <IncludePath>$(VC_IncludePath);$(WindowsSDK_IncludePath);c:\\Program Files (x86)\\Windows Kits\\10\\Include\\10.0.17134.0\\ucrt\\;<\/IncludePath>\r\n   <LibraryPath>$(VC_LibraryPath_x86);$(WindowsSDK_LibraryPath_x86);c:\\Program Files (x86)\\Windows Kits\\10\\Lib\\10.0.17134.0\\ucrt\\x86\\;<\/ExecutablePath>\r\n<\/PropertyGroup><\/pre>\n<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"
    I recently installed a fresh copy of Visual Studio 2017 on a new machine and went on to build several projects some of them being VC++. The trouble was that I immediately run into a problem (actually the first problem was that MFC & ATL were missing because I forgot to check that in the list of Individual components so I had to install them separately). The problem was an error with a missing new.h<\/tt> header:<\/p>\n
    1>c:\\program files (x86)\\microsoft visual studio\\2017\\enterprise\\vc\\tools\\msvc\\14.15.26726\\atlmfc\\include\\afx.h(62): fatal error C1083: Cannot open include file: 'new.h': No such file or directory<\/pre>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","advgb_blocks_editor_width":"","advgb_blocks_columns_visual_guide":"","_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[10,8],"tags":[453,271,34,55,459],"class_list":["post-3158","post","type-post","status-publish","format-standard","hentry","category-visual-studio","category-windows-programming","tag-mfc","tag-sdk","tag-vc","tag-visualstudio","tag-windows"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t