Windows 10 Creators Update SDK

The Windows 10 Creators Update (a.k.a. Version 1703) is now available along with a new Windows 10 SDK release. The Windows 10 Creators Update SDK (10.0.15063) can be installed via VS 2017 (15.1) or as a standalone installer. This includes DirectXMath 3.10 and updated versions of Direct3D 12, DXGI 1.6, Direct3D 11.4 Direct2D, and DirectWrite. See What's New in Windows 10 for developers, build 15063.

Visual Studio 2017 (15.1/15.2 Updates)

You can install the new Windows 10 SDK by installing the latest VS 2017 update (15.1, 15.2, or later). The new Windows 10 SDK  (15063) is actually three distinct components: Microsoft.VisualStudio.Component.Windows10SDK.15063.Desktop, Microsoft.VisualStudio.Component.Windows10SDK.15063.UWP, and Microsoft.VisualStudio.Component.Windows10SDK.15063.UWP.Native.

The Windows 10 Creators Update SDK resolves a number of conformance errors in Windows system headers enabling the use of the /permissive- switch.

VS 2015 Users: The Windows 10 SDK (15063) is officially only supported for VS 2017.

FXC: With the Windows 10 SDK (15063), the FXC compiler and the D3DCompiler_47.DLL were made side-by-side. From the Developer Command Prompt for VS 2017, using FXC will use the Windows 10 Anniversary Update (14393) version. You need to explicitly select the side-by-side version if you want to use a newer one from the command-line: "%WindowsSdkBinPath%%WindowsSDKVersion%\x86\fxc.exe"

Related: Windows 10 SDK RTM, Windows 10 SDK (November 2015), Windows 10 Anniversary Update SDK

Comments (2)

  1. Mike says:

    You seem to be some sort of Microsoft software genius so please take my dummy question with a grain of salt. I know nothing of software programming. I am simply trying to run old games on Windows 10 and one person on one of the forums said he installed the Direct X SDK and that in itself helped the compatibility issue for one of the games. Does that make sense? And can I install the Windows 10 SDK separately on my computer and will it do any good? If you respond, can you do so to my email address? Thanks.

    1. Installing the DirectX SDK or a Windows SDK will do nothing to get a game to work. Running the legacy DirectX SDK installer does also run the legacy DirectSetup package (aka the DirectX End-User Runtime) but as detailed in this blog post, the one thing it *never* does is “install DirectX”. DirectX is part of your OS and you can’t change it with an SDK, only by updating the OS in some way (new version, Service Pack, Windows Update etc.). The only thing the old DirectSetup package can fix is if the game in question is incorrectly deploying D3DX9, D3DX10, D3DX11, XActEngine, XAudio (prior to 2.8) or XInput (prior to 1.4)–see KB179113.

      So in short, you can try running the most recent (and last) DirectX End-User Runtime installer which might fix a broken game deployment, but it’s not going to fix any other compatibility issue that is likely impacting an old game run on a modern version of Windows. You could try create a shortcut with some compatibility options, but it likely won’t work if there’s an old DRM technology being used by that game. See KB15078.

      Best of luck!

Skip to main content