March 14, 2017 1:30 pm

Windows 10 SDK Preview Build 15052 Released

By / Senior Technical Product Manager, Windows Developer Team

Today, we released a new Windows 10 Creators Update SDK Preview to be used in conjunction with Windows 10 Insider Preview (Build 15052 or greater). The Preview SDK Build 15052 contains bug fixes and under development changes to the API surface area.

The Preview SDK can be downloaded from developer section on Windows Insider.

For feedback and updates to the known issues, please see the developer forum.  For new feature requests, head over to our Windows Platform UserVoice.

What’s New

  • No API changes have occurred since build 15021.
  • Windows SDK setup name change: With this release of the Windows SDK the setup executable name changed.  If you have scripts designed to install the previous SDK, you will need to update the path to use the new name:  WinSDKSetup.exe
  • The Windows SDK will now formally only be supported by Visual Studio 2017 and greater. You can download the Visual Studio 2017 here.

Known Issues Windows SDK

  • DX12 Template Throws when running Build 15042: This is a known bug in the Windows SDK installer.  If you encounter this issue, you can repair the SDK by simply running the following command from an Administrative command prompt:  C:\program files (x86)\windows kits\10\bin\10.0.15042.0\x86\DismFoDInstall.cmd

API Updates and Additions

No API changes have occurred since build 15021. For a list of the APIs added since Windows 10 Anniversary Update, please see 15021.

Updated March 14, 2017 1:36 pm

Join the conversation

  1. For those of us who maintain utilities that find and use Windows SDKs – does the VS2017 support limitation mean that it’s only designed for use with that IDE (but may work with other compilers)? or does it mean, more strictly, that it won’t build with versions of `cl` reporting `_MSC_VER < 1910`?

    Basically, I'd be interested in any guidance in adding these new versions to this CMake module used across numerous projects:

    • Thanks Ryan:
      The SDK will continue to work with other compilers.
      One significant reason for that statement is that we made changes to the layout of the SDK with the tools (bin folder) and the contract files which previous versions of Visual Studio cannot access.

      Kevin Larkin
      Program Manager