Windows 10 Technical Preview

The next version of Windows is now available as a Technical Preview for developers via the Windows Insiders program and for MSDN Subscribers. For more details, see Announcing Windows 10.

DirectX SDK Debug Layer: For Windows 10 Technical Preview (9926 or later), you need to enable the debug layer as a Windows optional feature to successfully use D3D11_CREATE_DEBUG_DEVICE or the Visual Studio 2013 Graphics Diagnostics tools: Start -> Settings -> System -> Optional features -> Add a feature; select "Graphics Tools". See this post for details.

Win32 desktop games: The existing guidance for quality Win32 desktop games running on Windows 7, Windows 8.0, and Windows 8.1 all applies to Windows 10 as well (see Desktop Games on Windows 8.x). Note that there is a new <compatibility> manifest section GUID for Windows 10 (see Manifest Madness), and VerifyVersionInfo is now subject to the same manifest-based behavior as GetVersion(Ex).

DirectX 12: If you are looking to try out DirectX 12, you should read the DirectX Developer Blog post and sign up for the DirectX 12 Early Access program.

Enterprise: If you are curious about the business version of Windows 10, see this post.

Web developers: The Technical Preview includes IE11, but there are a few improvements for Windows 10.

Windows Store and Windows phone developers: See this post.

Command Prompt: There's some fun features added for Windows 10's command prompt. See this post.

Comments (4)

  1. Alessio T says:

    Please, release a public preview of the new Windows SDK asap : (

  2. @AlessioT: New developer tools, SDKs, APIs, and a new universal apps model are all in the works but the Technical Preview's focus is on OS usage, performance, and compatibility. You can use VS 2013 and the Windows 8.1 SDK when trying it out. If you are interested in new compiler features, check out the Visual Studio "14" CTPs (which still includes the Windows 8.1 SDK).

  3. publicENEMY says:

    After you killed Silverlight and WPF, dont expect people have much faith in your platform anymore.

  4. @publicENEMY: Have you see this post on WPF or this post on Silverlight? Those blogs are probably better places to post comments w.r.t. to WPF/Silverlight technologies.

Skip to main content