Windows SDK 10.0.26100 causes compilation error in wchar.h with MSVC 2015 compiler
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 27%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
MikeB
16
Reputation points
I'm trying to build a legacy product that used MSVC 2015 Update 3 (compiler version 19.00.24215.1).
Since Windows SDK 10.0.26100 was installed on the machine the build fails with the following error:
C:\PROGRA~2\WI3CF2~1\10\include\10.0.26100.0\ucrt\wchar.h(313): error C3861: '_mm_loadu_si64': identifier not found
Apparently, in the recent SDK the wchar.h uses intrinsics that weren't available back in the VS2015 days (26100 is the first SDK that uses them, they do not appear in that file in the earlier versions of the SDK ).
Is there any official requirement or compatibility matrix for MVSC compiler/Windows SDK versions?
Developer technologies | C++
{count} votes
-
RLWA32 50,576 Reputation points2025-04-29T13:33:17.8566667+00:00 If I remember correctly the last Windows 10 SDK that integrated properly with VS2015 was the 10.0.14393.0 version from the 1607 build.
-
MikeB 16 Reputation points
2025-04-29T13:48:48.11+00:00 Well, maybe we were just lucky not to step on any landmines, but it used to work up to and including 10.0.22621.0.
So I'm looking for any official info regarding that compatibility. Like, "Windows SDK version X requires at least MSVC version Y" or "MSVC version N works with Windows SDK up to verson M", something of that kind
-
RLWA32 50,576 Reputation points
2025-04-29T13:58:17.97+00:00 I'm not aware of any compatibility documentation across VS and Windows 10/11 SDK versions.
You might be better off installing VS2022. Microsoft says that VS2022 and VS2015 can coexist on the same machine.
-
MikeB 16 Reputation points
2025-04-29T14:02:25.1033333+00:00 Of course they can coexist, but migrating a big legacy project to a different compiler is quite an effort, it's much more than just installing another IDE or toolset :)
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 86%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDL%3C/text%3E%3C/svg%3E)
David Lowndes 2,660 Reputation points MVP2025-04-29T14:24:00.9533333+00:00 The longer you leave it, the harder it may be.
Have you tried building your project with VS2022, what issues have you had? -
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 59%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EZW%3C/text%3E%3C/svg%3E)
Zhi Wei Lau 0 Reputation points2025-08-21T07:31:09.0766667+00:00 I able to compile successfully using Windows SDK 10.0.26100.1742 in VS2015 v140, beyond 1742 will fail error as you mention above
Sign in to comment
Sign in to answer