Hubbry Logo
Microsoft Windows SDKMicrosoft Windows SDKMain
Open search
Microsoft Windows SDK
Community hub
Microsoft Windows SDK
logo
7 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Microsoft Windows SDK
Microsoft Windows SDK
Microsoft Windows SDK
View on Wikipedia
from Wikipedia
Microsoft Windows SDK
DeveloperMicrosoft
Stable release
10.0.26100.1742 / September 26, 2024; 12 months ago (2024-09-26)
Operating systemWindows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, Windows 8, Windows 10, Windows 11
TypeApplication programming interface (API)
Websitedeveloper.microsoft.com/windows/downloads/sdk-archive

Microsoft Windows SDK, and its predecessors Platform SDK, and .NET Framework SDK, are software development kits (SDKs) from Microsoft that contain documentation, header files, libraries, samples and tools required to develop applications for Microsoft Windows and .NET Framework.[1] These libraries are also distributed as Windows System Files.

The Platform SDK specializes in developing applications for Windows 2000, XP and Windows Server 2003. .NET Framework SDK is dedicated to developing applications for .NET Framework 1.1 and .NET Framework 2.0. Windows SDK is the successor of the two and supports developing applications for Windows XP and later, as well as .NET Framework 3.0 and later.[2]

Features

[edit]

Platform SDK is the successor of the original Microsoft Windows SDK for Windows 3.1x and Microsoft Win32 SDK for Windows 9x. It was released in 1999 and is the oldest SDK. Platform SDK contains compilers, tools, documentations, header files, libraries and samples needed for software development on IA-32, x64 and IA-64 CPU architectures. .NET Framework SDK however, came to being with .NET Framework. Starting with Windows Vista, the Platform SDK, .NET Framework SDK, Tablet PC SDK and Windows Media SDK are replaced by a new unified kit called Windows SDK. However, the .NET Framework 1.1 SDK is not included since the .NET Framework 1.1 does not ship with Windows Vista. (Windows Media Center SDK for Windows Vista ships separately.) DirectX SDK was merged into Windows SDK with the release of Windows 8.[3]

Windows SDK allows the user to specify the components to be installed and where to install them. It integrates with Visual Studio, so that multiple copies of the components that both have are not installed; however, there are compatibility caveats if either of the two is not from the same era.[4][5] Information shown can be filtered by content, such as showing only new Windows Vista content, only .NET Framework content, or showing content for a specific language or technology.

Windows SDKs are available for free; they were once available on Microsoft Download Center but were moved to MSDN in 2012.

A developer might want to use an older SDK for a particular reason. For example, the Windows Server 2003 Platform SDK released in February 2003 was the last SDK to provide full support of Visual Studio 6.0. Some older PSDK versions can still be downloaded from the Microsoft Download center; others can be ordered on CD/DVD.[6]

Microsoft SDK version release history[7]
Name Version number Build number Release date Download Notes
Microsoft Windows Software Development Kit 3.1 ? 1992 [1]
Microsoft Windows Software Development Kit 3.11 ? ? ?
Microsoft Win32 Software Development Kit 3.1 ? ? [2]
Microsoft Win32 Software Development Kit 3.5 3.50.612.1 1994-04 [3]
Microsoft Win32 Software Development Kit 3.51 ? 1995-06 [4]
Microsoft Win32 Software Development Kit 4.0 4.0.1381.1 1996-11 [5]
Microsoft Win32 Software Development Kit v5.0 5.0.1636.1 1998-06 ? Included in Visual Studio 6
Microsoft Platform SDK April 1999 ? ? 1999-04 [6] MSDN subscription CD-ROM disc.

Last Platform SDK to officially install on Windows 95

Microsoft Platform SDK September 1999 ? 5.0.2128.8 1999-09 [7], [8] MSDN subscription CD-ROM disc.

Also known as Microsoft Platform SDK for Windows 2000 RC2.

Includes Alpha to AXP64 cross toolset.

Last Platform SDK to fully support Visual C++ 5.0

Microsoft Platform SDK January 2000 ? ? 2000-01 ? MSDN subscription CD-ROM disc.
Microsoft Platform SDK April 2000 ? 5.0.2195.32 2000-04 [9] MSDN subscription CD-ROM disc.
Microsoft Platform SDK November 2000 ? 5.0.2296.5 2000-11 [10] MSDN subscription CD-ROM disc.

Also known as Microsoft Platform SDK for Whistler Beta 1.

Includes preliminary tools for Itanium.

Microsoft Platform SDK February 2001 ? ? 2001-02 ?
Microsoft Platform SDK June 2001 v5.1 5.1.2505.0 2001-06 [11] MSDN subscription CD-ROM disc.

Last Platform SDK to officially develop for Windows 95. (Does not officially install on Windows 95)

Microsoft Platform SDK August 2001 v5.1 5.1.2601.0 2001-08 [12], [13] MSDN subscription CD-ROM disc.

Last Platform SDK to unofficially develop for Windows 95. (Does not officially install on Windows 95)

Microsoft Platform SDK November 2001 v5.2 5.2.3590.2 2001-11 [14]
Microsoft Platform SDK May 2002 v5.2 5.2.3639.1 2002-05 [15]
Microsoft Platform SDK July 2002 v5.2 5.2.3663.0 2002-07 [16]
Microsoft Platform SDK August 2002 v5.2 5.2.3672.1 2002-08 [17]
Microsoft Platform SDK November 2002 v5.2 5.2.3718.1 2002-11 [18]
Microsoft Platform SDK February 2003 v5.2 5.2.3790.0 2003-02 [19] Last version with VC6 support[8] and latest version with Windows 95 and Windows 98 support.
.NET Framework SDK Version 1.1 ? 1.1.4322.573 2003-03-29 [20] Included in Visual Studio 2003. Does not include the Platform SDK.
Microsoft Platform SDK for Windows XP SP2 ? 5.1.2600.2180 2004-08 [21] Introduced strsafe.h
Windows Server 2003 SP1 Platform SDK v5.2 5.2.3790.1830.15 2005-05-02 [22]
Windows Server 2003 R2 Platform SDK v5.2 5.2.3790.2075.51 2006-03-14 [23] Last Platform SDK to develop for Windows 2000.[9] Also suggested by MS to work with VS6 with no guarantee as it has not been tested with specific requirements.[10]
.NET Framework 2.0 Software Development Kit ? 2.0.50727.42 2006-11-29 [24] Included in Visual Studio 2005 Professional. Does not include the Platform SDK.
Microsoft Windows Software Development Kit for Windows Vista and .NET Framework 3.0 Runtime Components v6.0 6.0.6000.16384 2006-10-30 [25] The C++ compilers in this SDK release support the /analyze key.
Microsoft Windows Software Development Kit Update for Windows Vista v6.1 6.1.6000.16384.10 2007-03-22 [26] First unified .NET and Platform SDK. Does not support Visual Studio .NET 2003 and Microsoft Visual C++ Toolkit 2003
Included in Visual Studio 2008[11] v6.0a 6.1.6723.1 2007-11-19 [27]
Windows SDK for Windows Server 2008 and .NET Framework 3.5 v6.1 6.0.6001.18000.367 2008-02-05 [28] .NET Framework 3.5
Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 SP1 v7.0 6.1.7600.16385 2009-07-24 [29], [30]
Included in Visual Studio 2010 v7.0a 6.1.7600.16385 2010-04-12 [31] .NET Framework 4. Works only with Visual Studio 2010 and not Visual Studio 2010 Express. This is also the last version to include offline documentation.[12]
Microsoft Windows SDK for Windows 7 and .NET Framework 4 v7.1 7.1.7600.0.30514 2010-05-19[13][14] [32], [33] It is the latest version that officially supports Windows XP target. .NET Framework 4 needed. Higher sub-version from .NET Framework is not recognised by installation. Building the samples with nmake.exe is not supported, most of the NMAKE macros are removed.
Included in Visual Studio 2012 Update 1 (or later) v7.1A 7.1.51106 ? ? Introduces the "v110_xp" platform toolset
Microsoft Windows SDK for Windows 8 and .NET Framework 4.5 v8.0 6.2.9200.16384 2012-11-15[15] [34] .NET Framework 4.5, Windows Store apps and Integrated DirectX SDK
Included in Visual Studio 2012 v8.0A 8.0.50727 ? ?
Windows Software Development Kit (SDK) for Windows 8.1 v8.1 8.100.25984.0 2013-10-17 [35] Windows 8.1, .NET Framework 4.5.1, Windows Store apps and Integrated DirectX SDK
Included in Visual Studio 2013 v8.1A 8.1.51636 ? ? Includes the "v120_xp" platform toolset
Windows Standalone SDK for Windows 10 v10 10.0.10240.0 2015-07-29 [36] Also included in Visual Studio 2015[16]
Windows Standalone SDK for Windows 10, Version 1511[17] v10 10.0.10586.212 2015-11-30 [37] Also included in Visual Studio 2015 Update 1 & 2[18]
Windows Standalone SDK for Windows 10, Version 1607 v10 10.0.14393.795 2016-08-02 [38] Also included in Visual Studio 2015 Update 3
Windows Standalone SDK for Windows 10 Creators Update, Version 1703 v10 10.0.15063.0 2017-04-05 [39] Included in Visual Studio 2017 ver.15.1
Windows 10 SDK for Fall Creators Update, version 1709 v10 10.0.16299.15 2017-10-10 [40] Included in Visual Studio 2017 ver.15.4
Windows 10 SDK for April 2018 Update, version 1803 v10 10.0.17134.0 2018-05-08 [41] Included in Visual Studio 2017 ver.15.7
Windows 10 SDK for October 2018 Update, version 1809 v10 10.0.17763.0 2018-10-02 [42] Included in Visual Studio 2017 ver.15.8
Windows 10 SDK for Windows 10, version 1903 v10 10.0.18362.0 2019-05-21 [43] Included in Visual Studio 2019
Windows 10 SDK for Windows 10, version 2004 v10 10.0.19041.0 2020-05-12 [44]
Windows 10 SDK for Windows 10, version 2004 v10 10.0.19041.685 2020-12-16 [45] Servicing update
Windows 10 SDK for Windows 10, version 21H1 v10 10.0.20348.0 2021-05-25 [46]
Windows 10 SDK for Windows 11 v10 10.0.22000.194 2021-10-04 [47]
Windows SDK for Windows 11 v10 10.0.22621.755 2022-10-25 [48] Released as part of Windows 11, version 22H2. Includes servicing update 10.0.22000.755 on October 25, 2022,

Includes ARM64 support for the Visual Studio 17.4 release

Windows SDK for Windows 11 v10 10.0.22621.1778 2023-05-24 [49] Released as part of Windows 11, version 22H2 Build 10.0.22621.1778.
Windows SDK for Windows 11 v10 10.0.26100.0 2024-05-22 [50] Initial release of the 10.0.26100 series, to correspond with the Windows 11, version 24H2 preview.
Removed features of Windows SDK
Version Removed feature
Windows SDK for Windows 7 and .NET Framework 3.5 SP1[19]
  • capicom.dll (CAPICOM is deprecated)
  • iacom.dll
  • ialoader.dll
  • msistuff.exe
  • perflibmig.exe
  • permcalc.exe
  • secutil.exe
  • windowssideshowvirtualdevice.exe (replaced by DeviceSimulatorforWindowsSideShow.msi)
  • wpfperf.msi (now included in the Windows Performance Toolkit suite)
  • xamlpad.exe (XAMLPad)
Windows SDK for Windows 7 and .NET Framework 4[20]
  • UISpy.exe (Replaced by newer tools)
  • Wpt_arch.msi
  • Managed code samples (Moved to Code Gallery)
  • DExplore document viewer (Can be separately installed)
Windows Software Development Kit (SDK) for Windows 8[21]
  • Command-line build environment, including:
    • Windows SDK Platform Toolset
    • Visual C++ Compilers and C Runtime (CRT)
    • Windows SDK Configuration Tool
  • Tools and reference assemblies for versions of the .NET Framework earlier than 4.5
  • Apatch.exe
  • Bind.exe
  • Checkv4.exe
  • Consume.exe
  • DeviceSimulatorForWindowsSideShow.msi
  • Err.exe
  • FDBrowser.exe
  • FXCopSetup.exe
  • Guidgen.exe
  • Make-Shell.exe
  • MDbg.exe
  • Mpatch.exe
  • MSIZap.exe
  • PTConform.exe
  • ReBase.exe
  • sddlgen.exe
  • setenv.cmd
  • SetReg.exe
  • SoapSuds.exe
  • Sporder.exe
  • TcpAnalyzer.exe
  • TSPDesigner.exe
  • UTL2IDL.exe
  • ValidateSD.exe
  • VirtualLightSensor.exe
  • WinDiff.exe
  • WpfPerf.exe
  • All Windows samples (moved to Code Gallery)
  • Microsoft Help Viewer
  • IntelliSense XML documentation comments for the .NET Framework reference assemblies
Windows Software Development Kit (SDK) for Windows 8.1[22] Nothing
Windows Software Development Kit (SDK) for Windows 10 Nothing[23]

Documentation

[edit]

The Windows SDK documentation includes manuals documenting:

See also

[edit]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Microsoft Windows SDK

View on Grokipedia
from Grokipedia
The Microsoft is a provided by consisting of headers, libraries, metadata, and tools designed to enable developers to build native applications, including both (UWP) and classic Win32 desktop apps, targeting and earlier versions down to version 1507. Introduced as a successor to earlier SDKs for Windows 3.1x and Win32, the has evolved alongside major releases to provide updated APIs and resources for application development. Key historical milestones include the SDK released in June 2010, which supported .NET Framework 4.0 and targeted through ; the SDK in November 2012 for the Metro-style apps of that era; and the SDK in October 2013, introducing enhancements for touch-enabled interfaces. Subsequent versions aligned with updates, such as the 10.0.17763.0 SDK in 2018 for version 1809, and continued with SDKs starting from 10.0.22000.194 in October 2021, incorporating ARM64EC support. The latest release, version 10.0.26100 (build 10.0.26100.7175) as of November 2025, accompanies 25H2 and emphasizes forward compatibility while allowing downlevel targeting. Core components of the Windows SDK include C/C++ headers and libraries for accessing Windows APIs, such as the Win32 API for desktop features and UWP APIs for modern apps; metadata packages for .NET interoperability; and development tools like the MakeCat utility for catalog signing and the RC compiler for resources. It also provides code samples, extensive documentation, and integration with , where the SDK is selectable via the Target Platform Version in project properties to ensure compatibility with specific Windows versions from 7 SP1 onward. Since 2015, the SDK incorporates the Universal C Runtime (UCRT) library, which delivers standard C functions and supports and modern C++ standards as a system component on and later. The SDK is typically installed through the Installer under the "Desktop development with C++" workload or downloaded separately as an ISO or via for modular components, facilitating both packaged and unpackaged app deployment. While it focuses on low-level native development, it complements higher-level frameworks like .NET and serves as a foundational resource for and optimizing Windows applications across desktop, server, and mobile scenarios.

History

Origins in Early Windows

The Windows 3.1 (SDK) was introduced in April 1992, coinciding with the release of on April 6, 1992, to provide developers with essential tools and resources for building 16-bit applications targeting the Win16 API. This initial SDK included core header files such as , which enforced STRICT type-checking for improved code reliability, along with redistributable dynamic link libraries (DLLs) like COMMDLG.DLL for common dialog boxes and for . It supported the development of (GUI) elements through sample demonstrating controls, menus, and windows, and integrated seamlessly with compilers including the C version 6.0 and QuickC for Windows. Key tools in the early SDK facilitated and for 16-bit environments, including the Dialog Editor (DLGEDIT.EXE) for designing user interfaces, the Image Editor (IMAGEDIT.EXE) for handling icons and bitmaps, the Help Compiler (HC31.EXE) for creating application help files, and (DRWATSON.EXE) for crash analysis. These components emphasized compatibility with while introducing enhancements like drag-and-drop functionality, (OLE) support, and font integration, enabling developers to create more robust multimedia and networked applications on MS-DOS-based systems. The SDK's documentation, spanning multiple volumes such as the Programmer's Reference and Guide to Programming, provided detailed references for core functions, underscoring its role in standardizing Windows application development during the early 1990s. The first major update to the SDK arrived in 1993, aligned with the release of Windows for Workgroups 3.11 on August 11, 1993, extending support for networking features through expanded documentation and functions for and printer access. This iteration maintained the 16-bit focus but added libraries and samples for network redirectors, reflecting the growing emphasis on connectivity in enterprise and small office environments. By 1995, the SDK evolved significantly with the introduction of the Win32 SDK alongside 's retail release on August 24, 1995, marking the shift to 32-bit application support and preemptive multitasking. This version provided comprehensive headers for elements (e.g., windows, controls, and dialogs via USER32.H), the (GDI32.H for drawing and printing), and kernel functions (KERNEL32.H for process management and file I/O), enabling developers to leverage the full 32-bit subset compatible with both and contemporary NT systems. Samples and tools in this SDK illustrated modern features like long file names and shell extensions, establishing a foundation for scalable, protected-mode applications that outperformed their 16-bit predecessors.

Platform SDK Transition

In 1999, Microsoft released the Platform SDK as the successor to the earlier Microsoft Win32 SDK, consolidating fragmented development resources into a unified package that included headers and libraries for core Windows technologies such as Component Object Model (COM), Active Template Library (ATL), and Microsoft Foundation Classes (MFC). This consolidation addressed the growing complexity of Windows application development by providing a single, comprehensive set of tools and documentation, serving as a critical bridge between established Win32 programming models and the forthcoming .NET Framework ecosystem. Building briefly on the limitations of early 16-bit SDKs, which were constrained by DOS compatibility and lacked robust 32-bit support, the Platform SDK fully enabled modern 32-bit application creation for Windows NT-based systems. Key components of the Platform SDK included primary support for the architecture, early preparations for x64 (AMD64) development through updated headers and tools, and utilities like the Microsoft Interface Definition Language (MIDL) for generating from Interface Definition Language (IDL) files in scenarios, such as Remote Procedure Calls (RPC). The February 2003 edition marked the final release compatible with Visual C++ 6.0, targeted at development, after which subsequent versions required newer . Additionally, the SDK integrated elements from the Internet Explorer SDK, incorporating APIs and headers for web-related technologies like controls and rendering components to facilitate and web-integrated application development. The Platform SDK's evolution aligned closely with major Windows releases, notably the launch in February 2000, where updated editions provided essential APIs for enterprise-scale applications, including those leveraging for directory services, authentication, and LDAP-based queries. This alignment empowered developers to build secure, scalable solutions for networked environments, such as domain management and user authentication systems, solidifying the SDK's role up through compatibility.

Modern Unified SDK

The unified Windows SDK was introduced in November 2006 alongside , merging the existing Platform SDK with tools and components from the .NET Framework 3.0 to streamline development for the new operating system. This consolidation aimed to provide a single, comprehensive package for building both native Win32 applications and managed .NET code, reducing fragmentation that had persisted in prior SDK iterations. Subsequent releases progressively dropped support for older platforms like , with the Windows SDK 7.1—released on June 15, 2010—serving as the final version compatible with XP and Windows Server 2003. Key evolutions in the SDK reflected Microsoft's shifting focus toward modern app architectures and hardware support. In 2012, the Windows 8 SDK integrated the formerly separate DirectX SDK, incorporating its headers, libraries, and tools directly to simplify graphics and multimedia development without requiring multiple installations. The same release added WinRT headers and metadata, enabling developers to target Metro-style (later Universal Windows Platform) apps with a projection layer for languages like C++ and C#. In 2018, updates to the Windows 10 SDK introduced native support for ARM64 architectures, allowing cross-platform compilation for emerging mobile and edge devices. Further adaptations emphasized agility and integration with ecosystem tools. Starting in 2018, Microsoft shifted to delivering SDK updates more frequently through packages, such as for C++/WinRT projections, aligning with the monthly cadence of feature updates and enabling easier workflows. This approach continued into the era, with version 10.0.26100 released in 2024 to support the 24H2 update, incorporating API enhancements for AI workloads via Windows ML and advanced security features like primitives. This pattern of frequent updates persisted into 2025, with servicing releases of the 10.0.26100 SDK supporting version 25H2, released in October 2025, focusing on improved AI integration and security features.

Components

Headers and Libraries

The Microsoft Windows SDK provides a comprehensive set of header files and libraries that enable developers to access the Win32 API for native Windows application development. These components form the foundational layer for building desktop and server applications, supporting both 32-bit and 64-bit architectures, with declarations available in and ANSI versions. The headers define function prototypes, structures, constants, and macros, while the libraries supply the necessary import stubs for dynamic linking to system DLLs. Core headers in the SDK encapsulate key subsystems of the Windows operating system. The [Windows.h](/page/Windows.h) header serves as the primary umbrella file, including fundamental definitions and pulling in other essential headers for base access across categories such as , system services, and graphics. User32.h declares APIs for elements, including creation, message handling, and input processing, which are crucial for graphical applications. Kernel32.h provides declarations for core system services, encompassing memory management, file and device I/O, process and thread control, and synchronization primitives. Similarly, Gdi32.h exposes functions for rendering text, lines, shapes, and bitmap operations, supporting legacy 2D graphics in Windows applications. The SDK's libraries consist of import libraries (.lib files) that facilitate linking to corresponding dynamic-link libraries (DLLs) at build time, enabling runtime resolution of calls. For user interface functionality, User32.lib links to User32.dll, providing access to windowing and input APIs. System services are linked via Kernel32.lib for Kernel32.dll, while graphics operations use Gdi32.lib for Gdi32.dll. Additional libraries support specialized components, such as Advapi32.lib for advanced security and registry APIs in Advapi32.dll, and Ole32.lib for (COM) interfaces in Ole32.dll, which enable and . These static import libraries resolve function addresses during loading, ensuring compatibility with the environment. The Win32 API, as exposed through these headers and libraries, structures over 10,000 functions organized by functional areas like base services, networking, and diagnostics, allowing developers to interact directly with the operating system kernel and subsystems. It supports interoperability with C and C++ languages, where developers include headers to access prototypes and link libraries for resolution. To handle internationalization, the API includes Unicode variants of functions, denoted by a "W" suffix (e.g., MessageBoxW), which operate on wide-character strings (UTF-16) for global text support, while "A" variants use ANSI code pages; generic forms without suffixes adapt based on compile-time macros like UNICODE. Many newer functions are Unicode-only, promoting consistent wide-character usage across applications. In modern versions of the Windows SDK, particularly for (UWP) development, metadata packages in .winmd files extend the traditional headers and libraries by providing a binary description of (WinRT) APIs. These files enable language projections, allowing C++ code to consume WinRT types natively via generated headers from tools like cppwinrt.exe, while C# projections facilitate managed interop through assemblies. This metadata-driven approach supports cross-language scenarios in UWP apps, where Win32 extensions can project into managed environments without direct header inclusion.

Tools and Samples

The Microsoft Windows SDK provides a suite of command-line tools essential for compiling, signing, and packaging applications. The Resource Compiler (Rc.exe) processes resource definition scripts (.rc files) to generate binary resource files (.res), incorporating elements like menus, dialogs, icons, and string tables into executables. SignTool.exe enables digital signing of files for authenticity and tamper detection, along with signature verification and timestamping to comply with certificate validity periods. Additional utilities support debugging, performance monitoring, and deployment. Debugger extensions integrate with to provide Windows-specific debugging features, such as kernel-mode analysis and tracing. The Windows Performance Toolkit, part of the (ADK), includes Windows Performance Recorder (WPR) for capturing event traces to profile system and application performance, identifying bottlenecks in CPU usage and I/O operations, and Windows Performance Analyzer (WPA) for viewing the traces. For deployment, tools like MakeAppx.exe facilitate the creation of app packages, including MSIX formats, by bundling application files, manifests, and dependencies into distributable containers. The SDK includes a large collection of over 300 code samples in C++, available through the official Windows classic samples repository, to illustrate practical usage across domains like Win32 desktop applications, graphics rendering, and network programming with Winsock. These samples emphasize core concepts; for example, a basic Win32 application sample demonstrates window creation and message handling using the CreateWindow function, typically requiring SDK headers such as <windows.h> for compilation. Such examples promote understanding of integration without relying on higher-level frameworks, enabling developers to build native Windows applications from foundational code.

Versions and Compatibility

Release Timeline

The Microsoft Windows SDK has evolved through a series of major releases aligned with Windows operating system milestones, beginning with version 6.0 for in February 2007. This release introduced updated headers, libraries, and tools optimized for the new Vista APIs, marking a shift toward more integrated development support for graphical user interfaces and multimedia features. Subsequent versions built on this foundation, incorporating enhancements for security, performance, and new platform capabilities, including version 7.1 in 2010 for .NET Framework 4.0 and , version 8.0 in 2012 for , and version 8.1 in 2013 for with improved touch and sensor support. Version 7.0, released in August 2009 for and .NET Framework 3.5 SP1, expanded support for taskbar enhancements and improved compatibility with 2008 and 2010. It emphasized better integration with .NET technologies and included samples for developing applications leveraging 's Aero interface and multi-touch features. By this point, the SDK had transitioned from the earlier Platform SDK nomenclature to a more unified branding focused on Windows-specific development. Support for legacy platforms like had already been discontinued in the predecessor Platform SDK releases around 2005. The introduction of version 10.0.10240 in 2015 coincided with the launch of , bringing support for the Universal Windows Platform (UWP) to enable cross-device app development. This version adopted a new numbering scheme of 10.0., where the build number corresponds to the Windows OS build it targets, such as 10.0.19041 for the Windows 10 2004 update released in May 2020. This format allows for precise alignment with OS updates and facilitates through conditional compilation. In 2021, the Windows 11 SDK (version 10.0.22000) was released alongside , adding APIs for features like Snap Layouts to enhance window management and multitasking in desktop applications. Developers could now integrate with the new centered and rounded corners aesthetics, while maintaining support for Win32 and UWP apps. The initial release of version 10.0.26100 in May 2024 corresponded to version 24H2 and introduced enhancements for Copilot+ PCs, including APIs for neural processing unit (NPU) acceleration and AI-driven features like and Live Captions. This version supports advanced on-device AI workloads, enabling developers to build more efficient, hardware-accelerated applications. Updates to 10.0.26100 continued through November 2025 (e.g., build 10.0.26100.7175) to support version 25H2, released September 30, 2025, with additional AI and performance improvements. provides ongoing updates to the SDK aligned with Windows feature updates, allowing for incremental enhancements and security patches.
VersionRelease DateKey Associations and Milestones
6.0February 2007; foundational APIs for Aero and security features.
7.0August 2009 and .NET 3.5 SP1; and support.
7.1November 2010 and .NET 4.0; last to support .
8.0September 2012; initial ARM support and Metro-style apps.
8.1October 2013; touch enhancements and sensor APIs.
10.0.10240July 2015 RTM; UWP introduction for universal apps.
10.0.19041May 2020 2004 update; example of build-specific targeting.
10.0.22000October 2021; Snap Layouts and modern UI APIs.
10.0.26100May 2024 (initial); updates to November 2025 24H2 and 25H2; Copilot+ PC AI enhancements and further on-device AI features.

Platform Targeting

The Microsoft Windows SDK enables developers to target specific Windows operating system versions through preprocessor macros defined in code, primarily _WIN32_WINNT and WINVER, which determine the minimum supported platform and control the availability of APIs in the included headers. These macros are typically set in a file like targetver.h before including sdkddkver.h, ensuring that only features compatible with the targeted version are exposed during compilation. For instance, defining #define _WIN32_WINNT 0x0A00 targets (version 10.0), allowing access to APIs introduced in that release while excluding older, unsupported elements. The SDK supports multiple processor architectures to accommodate diverse hardware, including x86 (32-bit), x64 (64-bit), (32-bit), and ARM64 (64-bit), with comprehensive support for these beginning in the SDK released in 2012. This allows developers to build applications for traditional / processors as well as ARM-based devices, such as those in the Windows on ARM ecosystem, by selecting the appropriate platform configuration in build tools like . Earlier SDK versions provided x86 and x64 support, but ARM and ARM64 integration expanded with to enable native development for mobile and embedded scenarios. Compatibility across Windows versions has evolved, with support for legacy platforms like discontinued in predecessor SDKs by 2005 and the Windows SDK from version 6.0 targeting and later. Subsequent SDK versions maintain backward compatibility for applications targeting older systems through conditional compilation, but full utilization of recent features requires Windows 10 version 1809 (build 17763) or later as the host environment for development and runtime execution. This ensures access to updated APIs and security enhancements, while apps built with newer SDKs can still run on supported downlevel systems via emulation or shims where applicable. Down-level support for behaviors on older operating systems is facilitated through application , which allow developers to specify compatibility settings without altering core code. For example, DPI awareness levels—such as system-aware or per-monitor aware—can be declared in the manifest using elements like <dpiAwareness>PerMonitor</dpiAwareness>, enabling proper scaling on pre-Windows 10 systems that lack native high-DPI handling. This mechanism helps mitigate visual artifacts and ensures consistent user experiences across versions by instructing the OS to apply specific or awareness modes.

Integration and Usage

Visual Studio Integration

The Windows SDK integrates deeply with , enabling developers to install and utilize SDK components directly through the Visual Studio Installer. The "Desktop development with C++" workload includes the Windows SDK starting with Visual Studio 2015, with the latest version included by default from Visual Studio 2019, providing headers, libraries, and tools essential for building Windows applications without requiring a separate download. This streamlined installation process ensures that the SDK aligns with the IDE's build environment, supporting targets from Windows 7 SP1 onward. Key features of this integration include enhanced IntelliSense support for Windows APIs, which leverages the installed SDK headers to provide accurate , parameter information, and error detection during development of C++ projects. offers built-in project templates for creating Win32 desktop applications and WinUI-based apps, allowing developers to generate that incorporates SDK components like window management APIs or modern UI frameworks right from project creation. Additionally, capabilities are augmented by the SDK, enabling step-through execution into Windows system calls with access to symbol information from the attached SDK headers and libraries, facilitated by tools like the integrated and components. For (UWP) development, 2015 and later versions support Extension SDKs, which are specialized added to projects to expose device-family-specific APIs, such as those for mobile or desktop extensions, without altering project structure. Since 2019, modular inclusion of SDK elements has been enabled through packages like Microsoft.Windows.SDK.Contracts, which allow developers to reference APIs in .NET Framework or .NET Core projects without installing the full SDK, promoting lighter-weight dependencies and easier version management via the Package Manager. Project configuration in further simplifies SDK management through property pages, where developers can select specific Windows SDK versions per configuration—such as debug or release—directly in the project's General properties, ensuring compatibility with targeted Windows versions and avoiding build errors from mismatched installations. This selection is also accessible via the "Retarget projects" option in the solution explorer, which updates the SDK version across multiple projects efficiently.

Standalone Development

The Microsoft Windows SDK supports standalone development independent of the IDE, enabling command-line builds and integration with alternative environments for creating Windows applications. Developers can download the SDK via a standalone installer or ISO from the Developer website, with the latest version (10.0.26100 for ) requiring about 4 GB of available hard disk space upon installation. The installer allows customization of components, such as selecting specific headers, libraries, and tools, to tailor the setup to project needs without including unnecessary elements. To perform builds, the SDK is paired with the free Build Tools for , which supplies the essential (cl.exe) and linker (link.exe) from its bin directory. The build environment is initialized by running batch files like vcvarsall.bat, which set critical variables including PATH (for tool executables), INCLUDE (for header paths), and LIB (for library paths), with options to target architectures such as x86, x64, , or ARM64. This setup facilitates direct compilation of C++ source files using commands like cl.exe /EHsc example.cpp followed by linking with link.exe, supporting the creation of executables, DLLs, and static libraries. Specific usage often involves batch scripts to automate multi-target builds across platforms, streamlining workflows for complex projects. For enhanced package management, the SDK integrates with through , where installs dependencies and automatically configures to locate SDK headers and libraries via triplet specifications like x64-windows. This method ensures without manual path adjustments. Standalone development provides a lighter footprint than full installations, ideal for resource-constrained / () pipelines on servers like or later. It also accommodates non-Microsoft compilers, such as GCC via , for accessing SDK headers and libraries, though compatibility tweaks may be needed for seamless operation.

Windows App SDK

The , released in its initial stable version 1.0 on November 16, 2021, serves as a modern extension to the Windows SDK, enabling developers to build desktop applications using WinUI 3 while providing a self-contained runtime that operates independently of specific Windows operating system versions. This framework unifies access to the latest Windows APIs, allowing apps to target Windows 10 (version 1809 and later) and without requiring OS-level updates for new features, thus facilitating cross-version compatibility and faster iteration. Key components of the include APIs for advanced windowing with Win32 interop support, enabling seamless integration of traditional desktop code with modern UI elements; MSIX packaging for secure deployment of both packaged and unpackaged applications; and WinUI controls for native, responsive user interfaces. The SDK emphasizes app lifecycle management through rich mechanisms, such as processing activation arguments for protocols, file types, and system events, distinct from UWP's sandboxed model to offer broader access to desktop capabilities. Stable channel releases, which are production-ready, follow a roughly six-month cadence; for instance, version 1.5 arrived in late February 2024 with enhancements to deployment tools, while the latest 1.8.3 release as of November 2025 includes updates to ONNX Runtime for AI integrations. In contrast to the core Windows SDK's reliance on OS-embedded libraries, the delivers components via packages, supporting self-contained or framework-dependent deployments that minimize runtime dependencies and enable downlevel support back to version 1809. This focus on packaged apps, often using MSIX for installation and updates, combined with activation via the AppLifecycle APIs, allows developers to create hybrid applications that blend Win32 functionality with modern Windows features without UWP restrictions. The SDK maintains separate experimental and preview channels for testing emerging features, such as deeper WebView3 integration for embedded web content and advanced input handling, ensuring stable releases remain reliable while preview channels introduce refinements ahead of production; the experimental channel began with Experimental3 on November 11, 2025. By decoupling from UWP's app model, the provides greater flexibility for desktop developers, supporting both unpackaged Win32 apps and full MSIX packages with access to system resources like notifications and power management.

Merged and Legacy Components

The Microsoft Windows SDK has undergone several mergers that consolidated specialized development kits into its core distribution, streamlining access to APIs and tools for developers. A significant integration occurred with the SDK, which was fully incorporated into the SDK released in 2012. This merger included essential components such as Direct3D 11 (D3D11) headers, libraries, and the effects framework, eliminating the need for a separate download while ensuring compatibility with modern graphics development on Windows platforms. Prior to this, the .NET Framework SDK saw integration into the Windows SDK lineup around 2006, coinciding with the release and .NET Framework 3.0. This absorption combined native development resources with managed code tools, reducing fragmentation for full-stack application building. Earlier versions of the .NET Framework, such as 1.1 and 2.0, had standalone SDKs, but the merger facilitated unified support for hybrid native-managed projects. Legacy components within the SDK reflect the evolution away from outdated technologies, with explicit end-of-support announcements for older tools. For instance, compatibility with Visual C++ 6.0 (VC6) concluded with the February 2003 Platform SDK release, marking the cessation of official builds and debugging aids for that compiler version in subsequent SDK iterations. This shift encouraged migration to newer editions, as VC6 lacked conformance to evolving C++ standards and updates. Certain Win32 API subsets have been phased out or discouraged in favor of contemporary alternatives, underscoring the SDK's focus on modern user interfaces. The Multiple Document Interface (MDI) model, once central for multi-window applications, is now treated as a legacy feature, with Microsoft recommending tabbed document interfaces (TDI) for better usability and integration with current like those in Windows UI frameworks. Developers relying on deprecated MDI functions, such as those in the Common Controls library, are advised to refactor toward extensible UI elements to maintain compatibility with future Windows versions. Microsoft maintains an archive of pre-Windows 10 SDK releases to support maintenance of legacy applications, including versions targeting , Vista, and earlier platforms. These archived kits provide headers, libraries, and samples for obsolete targets, though they require manual installation and may not integrate seamlessly with the latest . Migration paths are a key aspect of handling legacy components, particularly in graphics programming. For example, applications built with DirectX 9 can transition to the built-in Direct3D 12 (D3D12) support in current SDKs by leveraging feature levels, which allow runtime detection of hardware capabilities and gradual upgrades without full rewrites. This approach preserves while enabling performance gains from modern rendering techniques.

References

  1. https://developer.microsoft.com/en-us/windows/downloads/windows-sdk/
  2. https://developer.microsoft.com/en-us/windows/downloads/sdk-archive/
  3. https://developer.microsoft.com/en-us/windows/downloads/sdk-archive/index-legacy
  4. https://learn.microsoft.com/en-us/windows/win32/msi/platform-sdk-components-for-windows-installer-developers
  5. https://learn.microsoft.com/en-us/cpp/windows/how-to-use-the-windows-10-sdk-in-a-windows-desktop-application?view=msvc-170
  6. https://learn.microsoft.com/en-us/shows/inside/windows-sdk
  7. https://learn.microsoft.com/en-us/shows/history/history-of-microsoft-1992
  8. http://www.bitsavers.org/pdf/microsoft/windows_3.1/Microsoft_Windows_3.1_SDK_1992/PC28914-0492_Windows_3.1_SDK_Getting_Started_199204.pdf
  9. https://winworldpc.com/product/windows-sdk-ddk/wfw-311
  10. https://jacobfilipp.com/MSJ/1993-vol8/anoverview.pdf
  11. https://archive.org/details/win95-win32-sdk
  12. https://walbourn.github.io/a-brief-history-of-windows-sdks/
  13. https://learn.microsoft.com/en-us/windows/win32/midl/using-the-midl-compiler-2
  14. https://www.microsoft.com/en-us/download/details.aspx?id=15656
  15. https://learn.microsoft.com/en-us/windows/win32/ad/active-directory-domain-services
  16. https://archive.org/details/ms-win2k-platsdk-rc2
  17. https://www.microsoft.com/en-us/download/details.aspx?id=14477
  18. https://walbourn.github.io/windows-sdk-7-1/
  19. https://learn.microsoft.com/en-us/windows/win32/directx-sdk--august-2009-
  20. https://blogs.windows.com/windowsdeveloper/2018/11/15/official-support-for-windows-10-on-arm-development/
  21. https://learn.microsoft.com/en-us/windows/release-health/windows11-release-information
  22. https://learn.microsoft.com/en-us/windows/win32/winprog/using-the-windows-headers
  23. https://learn.microsoft.com/en-us/windows/win32/apiindex/windows-api-list
  24. https://learn.microsoft.com/en-us/cpp/build/linking-an-executable-to-a-dll?view=msvc-170
  25. https://learn.microsoft.com/en-us/windows/win32/rpc/developing-32-bit-windows-applications
  26. https://learn.microsoft.com/en-us/troubleshoot/windows-client/setup-upgrade-and-drivers/dynamic-link-library
  27. https://learn.microsoft.com/en-us/windows/win32/intl/unicode-in-the-windows-api
  28. https://learn.microsoft.com/en-us/windows/uwp/cpp-and-winrt-apis/intro-to-using-cpp-with-winrt
  29. https://learn.microsoft.com/en-us/windows/win32/menurc/resource-compiler
  30. https://learn.microsoft.com/en-us/windows/win32/seccrypto/signtool
  31. https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-download-tools
  32. https://learn.microsoft.com/en-us/windows-hardware/test/wpt/
  33. https://learn.microsoft.com/en-us/windows/win32/appxpkg/make-appx-package--makeappx-exe-
  34. https://github.com/microsoft/Windows-classic-samples
  35. https://learn.microsoft.com/en-us/windows/win32/desktop-win32-code-samples
  36. https://walbourn.github.io/windows-10-sdk-rtm/
  37. https://learn.microsoft.com/en-us/windows/apps/desktop/modernize/ui/apply-snap-layout-menu
  38. https://learn.microsoft.com/en-us/cpp/porting/modifying-winver-and-win32-winnt?view=msvc-170
  39. https://learn.microsoft.com/en-us/windows/arm/overview
  40. https://learn.microsoft.com/en-us/visualstudio/ide/how-to-configure-projects-to-target-platforms?view=vs-2022
  41. https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/system-requirements
  42. https://learn.microsoft.com/en-us/windows/win32/api/windef/ne-windef-dpi_awareness
  43. https://learn.microsoft.com/en-us/windows/win32/win7appqual/compatibility---application-manifest
  44. https://learn.microsoft.com/en-us/visualstudio/ide/visual-cpp-intellisense-configuration?view=vs-2022
  45. https://learn.microsoft.com/en-us/windows/apps/winui/winui3/winui-project-templates-in-visual-studio
  46. https://learn.microsoft.com/en-us/uwp/extension-sdks/device-families-overview
  47. https://learn.microsoft.com/en-us/windows/apps/desktop/modernize/desktop-to-uwp-enhance
  48. https://www.nuget.org/packages/microsoft.windows.sdk.contracts
  49. https://learn.microsoft.com/en-us/cpp/build/reference/general-property-page-project?view=msvc-170
  50. https://learn.microsoft.com/en-us/cpp/build/building-on-the-command-line?view=msvc-170
  51. https://learn.microsoft.com/en-us/vcpkg/users/buildsystems/cmake-integration
  52. https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/
  53. https://www.zdnet.com/article/microsofts-windows-app-sdk-1-0-is-generally-available/
  54. https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/release-channels
  55. https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/windowing/windowing-overview
  56. https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/stable-channel
  57. https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/deployment-architecture
  58. https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/migrate-to-windows-app-sdk/migrate-to-windows-app-sdk-ovw
  59. https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/preview-channel
  60. https://learn.microsoft.com/en-us/cpp/overview/visual-cpp-samples?view=msvc-170
  61. https://learn.microsoft.com/en-us/windows/win32/direct3d11/overviews-direct3d-11-devices-downlevel-intro
Add your contribution
Related Hubs
User Avatar
No comments yet.