Windows API - Wikipedia https://en.wikipedia.

org/wiki/Windows_API

Windows API
The Windows API, informally WinAPI, is the
Windows API
foundational application programming interface (API) that
allows a computer program to access the features of the
Microsoft Windows operating system in which the
program is running.

Each major version of the Windows API has another name

that identifies a compatibility aspect of that version. For
example, Win32 is the major version of Windows API that
runs on 32-bit systems. The name, Windows API,
collectively refers to all versions of this capability of
Windows.

Microsoft provides developer support via a software

development kit, Microsoft Windows SDK, which includes
documentation and tools for building software based on
The Win32 subsystem shown next to the
the Windows API.
POSIX and OS/2 subsystem in the
architecture of Windows NT (later Win64
is also available.)
Services
Developer(s) Microsoft
The functions provided by the Windows API can be Initial release November 20, 1985
grouped into eight categories:[1] Operating system Microsoft Windows,
OS/2
Base Services
Provides access to the basic resources available to a Predecessor DOS API
Windows system. Included are things like file Type API
systems, devices, processes, threads, and error
License Proprietary
handling. These functions reside in kernel.exe,
krnl286.exe or krnl386.exe files on 16-bit Website https://
Windows, and kernel32.dll and KernelBase.dll learn.microsoft.com/
on 32 and 64 bit Windows. These files reside in the en-us/windows/
folder \Windows\System32 on all versions of apps/
Windows. [2]
Advanced Services
Provides access to functions beyond the kernel. Included are things like the Windows
registry, shutdown/restart the system (or abort), start/stop/create a Windows service, manage
user accounts. These functions reside in advapi32.dll and advapires32.dll on 32-bit
Windows.
Graphics Device Interface
Provides functions to output graphics content to monitors, printers, and other output devices.
It resides in gdi.exe on 16-bit Windows, and gdi32.dll on 32-bit Windows in user-mode.

1 of 9 31/07/2024, 15:41
Windows API - Wikipedia https://en.wikipedia.org/wiki/Windows_API

Kernel-mode GDI support is provided by win32k.sys which communicates directly with the
graphics driver.[3][4]
User Interface
Provides the functions to create and manage screen windows and most basic controls, such
as buttons and scrollbars, receive mouse and keyboard input, and other functions associated
with the graphical user interface (GUI) part of Windows. This functional unit resides in
user.exe on 16-bit Windows, and user32.dll on 32-bit Windows. Since Windows XP
versions, the basic controls reside in comctl32.dll, together with the common controls
(Common Control Library).[5]
Common Dialog Box Library
Provides applications the standard dialog boxes to open and save files, choose color and
font, etc. The library resides in a file called commdlg.dll on 16-bit Windows, and
comdlg32.dll on 32-bit Windows. It is grouped under the User Interface category of the
API.[6]
Common Control Library
Gives applications access to some advanced controls provided by the operating system.
These include things like status bars, progress bars, toolbars and tabs. The library resides in
a dynamic-link library (DLL) file called commctrl.dll on 16-bit Windows, and comctl32.dll
on 32-bit Windows. It is grouped under the User Interface category of the API.[7]
Windows Shell
Component of the Windows API allows applications to access functions provided by the
operating system shell, and to change and enhance it. The component resides in shell.dll
on 16-bit Windows, and shell32.dll on 32-bit Windows. The Shell Lightweight Utility
Functions are in shlwapi.dll. It is grouped under the User Interface category of the API.[8]
[9]
Network Services
Give access to the various networking abilities of the operating system. Its subcomponents
include NetBIOS, Winsock, NetDDE, remote procedure call (RPC) and many more. This
component resides in netapi32.dll on 32-bit Windows.[10]
Web
The Internet Explorer (IE) web browser also exposes many APIs that are often used by
applications, and as such could be considered a part of the Windows API. IE has been
included with the operating system since Windows 95 OSR2 and has provided web-related
services to applications since Windows 98.[11] Specifically, it is used to provide:

▪ An embeddable web browser control, contained in shdocvw.dll and mshtml.dll.

▪ The URL moniker service, held in urlmon.dll, which provides COM objects to applications for
resolving URLs. Applications can also provide their own URL handlers for others to use.
▪ An HTTP client library which also takes into account system-wide Proxy settings (wininet.dll);
however, Microsoft has added another HTTP client library called winhttp.dll which is smaller
and more suitable for some applications.
▪ A library to assist multi-language and international text support (mlang.dll).
▪ DirectX Transforms, a set of image filter components.
▪ XML support (the MSXML components, held in msxml*.dll).
▪ Access to the Windows Address Books.

Program interaction

2 of 9 31/07/2024, 15:41
Windows API - Wikipedia https://en.wikipedia.org/wiki/Windows_API

The Windows API is defined in the C programming language.[12] Its functions and data structures
are defined in C syntax (see windows.h). However, the API may be consumed via any programming
language that can inter-operate with the API data structures and calling conventions for function
calls and callbacks.

Of note, the internal implementation of the API functions has been developed in several languages
other than C.[a]

Despite the fact that C is not an object-oriented programming (OOP) language, the Windows API is
somewhat object-oriented due to its use of handles. Various other technologies from Microsoft and
others make this object-oriented aspect more apparent by using an OOP language such as C++ --
see Microsoft Foundation Class Library (MFC), Visual Component Library (VCL), GDI+. Of note,
Windows 8 provides the Windows API and the WinRT API, which is implemented in C++[13] and is
object-oriented by design.[13]

Windows.pas is a Pascal/Delphi unit that exposes the features of Windows API. It is the Pascal
equivalent to the C language windows.h.[14]

The Windows API is for the most part intended for a program to access operating system features.
For communication among different Windows applications, Microsoft has developed a series of
technologies alongside Windows API. This started with Dynamic Data Exchange (DDE), which was
superseded by Object Linking and Embedding (OLE) and later by the Component Object Model
(COM), Automation Objects, ActiveX controls, and the .NET Framework. There is not always a
clear distinction between these technologies, and there is much overlap.

The variety of terms is basically the result of grouping software mechanisms that relate to a given
aspect of software development. Automation specifically relates to exporting the function of an
application or component (as an application programming interface (API)) so that it can be
controlled by other applications instead of by human users only, .NET is a self-contained general
methodology and technology to develop desktop and web applications written in a variety of just-
in-time (JIT) compiled languages.

Related technologies
Many Microsoft technologies use the Windows API -- as most software running on Windows does.
As middle-ware between Windows API and an application, these technologies provide some access
to Windows API. Some technologies are described as wrapping Windows API, but this is debatable
since no other technology provides or exposes all of the capabilities of Windows API.

▪ Microsoft Foundation Class Library (MFC) exposes some of Windows API functionality in C++
classes, and thus allows a more object-oriented way to interact with the API
▪ Active Template Library (ATL) is a C++ template library that provides some Windows API
access
▪ Windows Template Library (WTL) was developed as an extension to ATL, and intended as a
smaller alternative to MFC

3 of 9 31/07/2024, 15:41
Windows API - Wikipedia https://en.wikipedia.org/wiki/Windows_API

▪ Most application frameworks for Windows provide some access to Windows API; including
.NET runtime and Java virtual machine and any other programming languages targeting
Windows
Although almost all Windows programs use the Windows API, on the Windows NT line of
operating systems, programs that start early in the Windows startup process use the Native API
instead.[15]

History
The Windows API has always exposed a large part of the underlying structure of the Windows
systems to programmers. This had the advantage of giving them much flexibility and power over
their applications, but also creates great responsibility in how applications handle various low-
level, sometimes tedious, operations that are associated with a graphical user interface.

For example, a beginning C programmer will often write the simple "hello world" as their first
assignment. The working part of the program is only a single printf line within the main
subroutine. The overhead for linking to the standard I/O library is also only one line:

#include <stdio.h>

int main(void) {
printf("Hello, World!\n");
}

Charles Petzold, who wrote several books about programming for the Windows API, said: "The
original hello world program in the Windows 1.0 SDK was a bit of a scandal. HELLO.C was about
150 lines long, and the HELLO.RC resource script had another 20 or so more lines. (...) Veteran
programmers often curled up in horror or laughter when encountering the Windows hello-world
program."[16] Petzold explains that while it was the first Windows sample programs developers
were introduced to, it was quite "fancy" and more complex than needed. Tired of people ridiculing
the length of the sample, he eventually reduced it to a simple MessageBox call.[17]

Over the years, various changes and additions were made to Windows systems, and the Windows
API changed and grew to reflect this.[18] The Windows API for Windows 1.0 supported fewer than
450 function calls, whereas modern versions of the Windows API support thousands. However, in
general, the interface remained fairly consistent, and an old Windows 1.0 application will still look
familiar to a programmer who is used to the modern Windows API.[19]

Microsoft has made an effort to maintain backward compatibility. To achieve this, when
developing new versions of Windows, Microsoft sometimes implemented workarounds[20] to allow
compatibility with third-party software that used the prior version in an undocumented or even
inadvisable way. Raymond Chen, a Microsoft developer who works on the Windows API, has said:
"I could probably write for months solely about bad things apps do and what we had to do to get
them to work again (often in spite of themselves). Which is why I get particularly furious when
people accuse Microsoft of maliciously breaking applications during OS upgrades. If any
application failed to run on Windows 95, I took it as a personal failure."[21]

4 of 9 31/07/2024, 15:41
Windows API - Wikipedia https://en.wikipedia.org/wiki/Windows_API

One of the largest changes to the Windows API was the transition from Win16 (shipped in
Windows 3.1 and older) to Win32 (Windows NT and Windows 95 and up). While Win32 was
originally introduced with Windows NT 3.1 and Win32s allowed use of a Win32 subset before
Windows 95, it was not until Windows 95 that widespread porting of applications to Win32 began.
To ease the transition, in Windows 95, for developers outside and inside Microsoft, a complex
scheme of API thunks was used that could allow 32-bit code to call into 16-bit code (for most of
Win16 APIs) and vice versa. Flat thunks allowed 32-bit code to call into 16-bit libraries, and the
scheme was used extensively inside Windows 95's libraries to avoid porting the whole OS to Win32
in one batch. In Windows NT, the OS was pure 32-bit, except parts for compatibility with 16-bit
applications, and only generic thunks were available to thunk from Win16 to Win32, as for
Windows 95. The Platform SDK shipped with a compiler that could produce the code needed for
these thunks. Versions of 64-bit Windows are also able to run 32-bit applications via WoW64. The
SysWOW64 folder located in the Windows folder on the OS drive contains several tools to support
32-bit applications.[22]

Major versions
Each version of Microsoft Windows contains a version of Windows API, and almost every new
version of Microsoft Windows has introduced additions and changes to the Windows API.[23]

The name, Windows API, refers to essentially the same capability in each version of Windows, but
there is another name for this capability that is based on major architectural aspects of the
Windows version that contains it. When there was only one version, it was simply called Windows
API. Then, when the first major update was made, Microsoft gave it the name Win32 and gave the
first version the name Win16. The term Windows API refers to both versions and all subsequently
developed major versions.[1]

▪ Win16 is in the 16-bit versions of Windows. The functions reside mainly in core files of the OS:
kernel.exe (or krnl286.exe or krnl386.exe), user.exe and gdi.exe. Despite the file extension of
exe, such a file is accessed as a dynamic-link library (DLL).
▪ Win32 is in the 32-bit versions of Windows (NT, 95, and later). The functions are implemented
in system DLL files including kernel32.dll, user32.dll, and gdi32.dll. Win32 was introduced with
Windows NT. In Windows 95, it was initially referred to as Win32c, with c meaning
compatibility. This term was later abandoned by Microsoft in favor of Win32.
▪ Win32s is an extension for the Windows 3.1x family of Microsoft Windows that implemented a
subset of the Win32 API for these systems. The "s" stands for "subset".
▪ Win64 is the version in the 64-bit platforms of the Windows architecture (as of 2021, x86-64
and AArch64).[b][24][25] Both 32-bit and 64-bit versions of an application can be compiled from
one codebase, although some older API functions have been deprecated, and some of the API
functions that were deprecated in Win32 were removed. All memory pointers are 64-bit by
default (the LLP64 model), so porting Win32-compatible source code includes updating for 64-
bit pointer arithmetic.[26]
▪ WinCE is the version in the Windows CE operating system.

5 of 9 31/07/2024, 15:41
Windows API - Wikipedia https://en.wikipedia.org/wiki/Windows_API

Other implementations
The Wine project provides a Win32 API compatibility layer for
Unix-like platforms, between Linux kernel API and programs
written for the Windows API. ReactOS goes a step further and
aims to implement the full Windows operating system, working
closely with the Wine project to promote code re-use and
compatibility. DosWin32 and HX DOS Extender are other
projects which emulate the Windows API to allow executing
simple Windows programs from a DOS command line. Odin is
a project to emulate Win32 on OS/2, superseding the original
ReactOS is a free and open-source
Win-OS/2 emulation which was based on Microsoft code. operating system that aims to
Other minor implementations include the MEWEL and Zinc implement the Windows API
libraries which were intended to implement a subset of the
Win16 API on DOS (see List of platform-independent GUI
libraries).

Windows Interface Source Environment (WISE) was a licensing program from Microsoft which
allowed developers to recompile and run Windows-based applications on Unix and Macintosh
platforms. WISE SDKs were based on an emulator of the Windows API that could run on those
platforms.[27]

Efforts toward standardization included Sun's Public Windows Interface (PWI) for Win16 (see
also: Sun Windows Application Binary Interface (Wabi)), Willows Software's Application
Programming Interface for Windows (APIW) for Win16 and Win32 (see also: Willows TWIN), and
ECMA-234, which attempted to standardize the Windows API bindingly.

Compiler support
To develop software that uses the Windows API, a compiler must be able to use the Microsoft-
specific DLLs listed above (COM-objects are outside Win32 and assume a certain vtable layout).
The compiler must either handle the header files that expose the interior API function names, or
supply such files.

For the language C++, Zortech (later Symantec, then Digital Mars), Watcom and Borland have all
produced well known commercial compilers that have been used often with Win16, Win32s, and
Win32. Some of them supplied memory extenders, allowing Win32 programs to run on Win16
with Microsoft's redistributable Win32s DLL. The Zortech compiler was probably one of the first
stable and usable C++ compilers for Windows programming, before Microsoft had a C++ compiler.

For certain classes of applications, the compiler system should also be able to handle interface
description language (IDL) files. Collectively, these prerequisites (compilers, tools, libraries, and
headers) are known as the Microsoft Platform SDK. For a time, the Microsoft Visual Studio and

6 of 9 31/07/2024, 15:41
Windows API - Wikipedia https://en.wikipedia.org/wiki/Windows_API

Borland's integrated development system were the only integrated development environments
(IDEs) that could provide this (although, the SDK is downloadable for free separately from the
entire IDE suite, from Microsoft Windows SDK for Windows 7 and .NET Framework 4 (http://ww
w.microsoft.com/download/en/details.aspx?displaylang=en&id=8279)).

As of 2016, the MinGW and Cygwin projects also provide such an environment based on the GNU
Compiler Collection (GCC), using a stand-alone header file set, to make linking against the Win32-
specific DLLs simple. LCC-Win32 is a C compiler maintained by Jacob Navia, freeware for non-
commercial use. Pelles C is a freeware C compiler maintained by Pelle Orinius. Free Pascal is a free
software Object Pascal compiler that supports the Windows API. The MASM32 package is a
mature project providing support for the Windows API under Microsoft Macro Assembler (MASM)
by using custom made or converted headers and libraries from the Platform SDK. Flat assembler
FASM allows building Windows programs without using an external linker, even when running on
Linux.

Windows specific compiler support is also needed for Structured Exception Handling (SEH). This
system serves two purposes: it provides a substrate on which language-specific exception handling
can be implemented, and it is how the kernel notifies applications of exceptional conditions such as
dereferencing an invalid pointer or stack overflow. The Microsoft/Borland C++ compilers had the
ability to use this system as soon as it was introduced in Windows 95 and NT, however the actual
implementation was undocumented and had to be reverse engineered for the Wine project and free
compilers. SEH is based on pushing exception handler frames onto the stack, then adding them to
a linked list stored in thread-local storage (the first field of the thread environment block). When
an exception is thrown, the kernel and base libraries unwind the stack running handlers and filters
as they are encountered. Eventually, every exception unhandled by the application will be dealt
with by the default backstop handler, which pops up the Windows common crash dialog.

See also
▪ Windows Libraries for OS/2
▪ Interix
▪ Linux kernel API
▪ Microsoft Windows library files
▪ Windows legacy audio components
▪ C++/WinRT, a library providing access to Windows Runtime

Notes
a. Both Pascal and x86 assembly were heavily used in earlier versions, before C became
dominant. A reminiscence of this is that the API functions still use the Pascal calling convention
to restore the stack from pushed parameters after a call (although they expect parameters
pushed from right to left, as most C compilers do, by default).
b. Nomenclature of released 64-bit versions includes Windows XP Professional x64 Edition and

7 of 9 31/07/2024, 15:41
Windows API - Wikipedia https://en.wikipedia.org/wiki/Windows_API

x64 Editions of Windows Server 2003, Windows Vista and Windows Server 2008 on the x86-64
(AMD64) platform, and Windows 2000 Server Limited Edition, Windows XP 64-bit Edition,
Windows Advanced Server 2003 for Itanium and Windows 2008 Advanced Server for Itanium
on the IA-64 platform.

References
1. Microsoft Developer Network (July 2005). Overview of the Windows API. (http://msdn.microsof
t.com/library/default.asp?url=/library/en-us/winprog/winprog/overview_of_the_windows_api.as
p) Retrieved August 28, 2005.
2. Microsoft Developer Network (July 2005). Base Services. (http://msdn.microsoft.com/library/def
ault.asp?url=/library/en-us/winprog/winprog/base_services.asp) Retrieved August 28, 2005.
3. Microsoft Developer Network (July 2005). Graphics Device Interface. (http://msdn.microsoft.co
m/library/default.asp?url=/library/en-us/winprog/winprog/graphics_device_interface.asp)
Retrieved August 28, 2005.
4. "G" (http://msdn.microsoft.com/en-us/library/ms789535.aspx). Microsoft Developer Network.
Retrieved January 28, 2009.
5. Microsoft Developer Network (July 2005). User Interface. (http://msdn.microsoft.com/library/def
ault.asp?url=/library/en-us/winprog/winprog/user_interface.asp) Retrieved August 28, 2005.
6. Microsoft Developer Network (2005). Common Dialog Box Library. (http://msdn.microsoft.com/li
brary/default.asp?url=/library/en-us/winui/winui/windowsuserinterface/userinput/commondialog
boxlibrary.asp) Retrieved September 22, 2005.
7. Microsoft Developer Network (July 2005). Common Control Library. (http://msdn.microsoft.com/
library/default.asp?url=/library/en-us/winprog/winprog/common_control_library.asp) Retrieved
August 28, 2005.
8. Microsoft Developer Network (July 2005). Windows Shell. (http://msdn.microsoft.com/library/de
fault.asp?url=/library/en-us/winprog/winprog/windows_shell.asp) Retrieved August 28, 2005.
9. Microsoft Developer Network (2005). Shell Programmer's Guide. (http://msdn.microsoft.com/lib
rary/default.asp?url=/library/en-us/shellcc/platform/shell/programmersguide/shell_intro.asp)
Retrieved August 28, 2005.
10. Microsoft Developer Network (July 2005). Network Services. (http://msdn.microsoft.com/en-us/l
ibrary/aa969177) Retrieved August 28, 2005.
11. Microsoft Developer Network (January 2006); Programming and reusing the browser (http://ms
dn.microsoft.com/library/default.asp?url=/workshop/browser/prog_browser_node_entry.asp)
Retrieved January 22, 2006.
12. "Walkthrough: Create a traditional Windows Desktop application (C++)" (https://docs.microsof
t.com/en-us/cpp/windows/walkthrough-creating-windows-desktop-applications-cpp). Microsoft
Docs. February 23, 2022.
13. Mayberry, Michael (2012). WinRT Revealed. New York City: Apress. p. 3.
ISBN 978-1-4302-4585-8.
14. Texeira, Steve and Xavier Pacheco (2002). Borland Delphi 6 Developer's Guide (https://book
s.google.com/books?id=9JzBn4vcUBoC&q=%22windows.pas%22&pg=PA253). Sams. p. 253.
ISBN 0672321157.
15. Russinovich, Mark (November 2006). "Inside Native Applications" (https://docs.microsoft.com/e
n-us/sysinternals/resources/inside-native-applications). Microsoft Docs. Retrieved April 12,
2022.

8 of 9 31/07/2024, 15:41
Windows API - Wikipedia https://en.wikipedia.org/wiki/Windows_API

16. Charles Petzold (December 2001). Programming Microsoft Windows with C#. Microsoft Press.
Beyond the Console, page 47.
17. Petzold, Charles. "The Infamous Windows "Hello World" Program" (https://www.charlespetzol
d.com/blog/2014/12/The-Infamous-Windows-Hello-World-Program.html).
www.charlespetzold.com. Retrieved June 30, 2024.
18. Detailed analysis of changes in the Windows API from XP to 10. (http://abi-laboratory.pro/inde
x.php?view=winapi) Retrieved September 08, 2016.
19. Charles Petzold (November 11, 1998). Programming Windows, Fifth Edition. Microsoft Press.
APIs and Memory Models, page 9.
20. Smith, Graham (October 8, 2022). "Windows 95 had special code just to fix a bug in the
original SimCity" (https://www.rockpapershotgun.com/windows-95-had-special-code-just-to-fix-
a-bug-in-the-original-simcity). Rock, Paper, Shotgun.
21. Raymond Chen (October 15, 2003). What about BOZOSLIVEHERE and
TABTHETEXTOUTFORWIMPS? (https://devblogs.microsoft.com/oldnewthing/20031015-00/?p
=42163) Retrieved June 29, 2022.
22. Hoffman, Chris. "What's the Difference Between the "System32" and "SysWOW64" Folders in
Windows?" (https://www.howtogeek.com/326509/whats-the-difference-between-the-system32-
and-syswow64-folders-in-windows/). How-To Geek. Retrieved April 11, 2023.
23. The Iseran Project (1996–2001). History of the Windows API. (https://web.archive.org/web/200
20802081510/http://www.iseran.com/Win32/FAQ/history.html) Retrieved October 7, 2005.
24. "Windows XP Professional x64 Edition home page" (http://www.microsoft.com/windowsxp/64bi
t/). Microsoft.
25. "Microsoft 64-bit Computing Overview" (http://www.microsoft.com/servers/64bit/). Microsoft.
26. "MSDN: Getting Ready for 64-bit Windows" (http://msdn.microsoft.com/en-us/library/aa384198
(VS.85).aspx). Microsoft.
27. WISE (http://hyper.sunjapan.com.cn/~hz/win32/wise.htm) Archived (https://web.archive.org/we
b/20080330032918/http://hyper.sunjapan.com.cn/~hz/win32/wise.htm) 2008-03-30 at the
Wayback Machine

External links
▪ MSDN Windows API index (https://docs.microsoft.com/en-us/windows/win32/apiindex/window
s-api-list)
▪ Windows API Microsoft Code Samples (https://docs.microsoft.com/en-us/samples/browse/?filte
r-products=windows%20api&products=windows-api-win32)
▪ ECMA-234 (https://www.ecma-international.org/publications-and-standards/standards/ecma-23
4/) – ECMA standard for a subset of the Windows API
▪ Advanced Win32 API newsgroup (news://comp.os.ms-windows.programmer.win32)
▪ French Win32 API newsgroup (news://fr.comp.os.ms-windows.programmation)

Retrieved from "https://en.wikipedia.org/w/index.php?title=Windows_API&oldid=1236291541"

9 of 9 31/07/2024, 15:41