Win32 is not going anywhere. That’s the message from Microsoft Azure CTO Mark Russinovich, who in a May 6, 2026 Microsoft Dev Docs video, reaffirmed that the Win32 API remains a first-class citizen in Windows 11. Despite years of platform evolution, new frameworks, and the push toward cloud and web experiences, the decades-old API still underpins the vast majority of Windows software and system infrastructure. Russinovich—widely respected as the creator of Sysinternals and a chief architect of Azure’s OS strategy—explained that Win32’s continued primacy is not inertia, but a deliberate architectural choice driven by compatibility, security-hardened design, and an intricate symbiosis with modern web technologies.

The video, titled “Windows Internals: API Evolution,” clocks in at just under an hour and delves into the kernel-level reasons Win32 endures. It comes at a time when developers sometimes wonder whether they should abandon Win32 for WinUI 3, .NET MAUI, or Progressive Web Apps. The answer, Russinovich said, is a resounding no. “Win32 is the most tested, most hardened, and most performant API surface we have,” he noted. “It’s not legacy—it’s the foundation that makes Windows, Windows.” His comments reinforce what many enterprise developers and ISVs have long assumed: Microsoft will support the Win32 subsystem indefinitely, and the company’s own internal tools and Azure integrations lean on it daily.

The enduring dominance of Win32

Walk through any Fortune 500 IT department and you’ll find a staggering inventory of Win32 applications. From line-of-business ERP clients to engineering simulation tools, tax preparation software to point-of-sale systems, the Win32 ecosystem represents trillions of dollars in cumulative investment. Microsoft itself dogfoods Win32 at extraordinary scale—think of Office, Visual Studio, SQL Server Management Studio, and the majority of the Windows admin toolchain. Even Azure services like Azure Virtual Desktop rely on Win32 agents to broker remote sessions.

What makes Win32 so difficult to displace is its unparalleled stability contract. An application compiled for Windows NT 4.0 in 1996 will, in most cases, run without modification on Windows 11 24H2—nearly 30 years later. This backward compatibility is not accidental. It’s the result of painstaking engineering: side-by-side assemblies, compatibility shims, and a subsystem that exposes the same guarantees even as the kernel evolves. Russinovich pointed to the Windows compatibility database, which contains over 3,000 shims that silently fix quirks for specific applications, as one of the OS’s “hidden superpowers.” “When enterprises complain about compatibility,” he said, “they’re almost always talking about Win32. That’s why we treat it as tier-one—not tier-two or deprecated.”

Compatibility as Windows’ superpower

The compatibility shim infrastructure isn’t just a crutch; it’s a strategic asset. When a critical line-of-business app built for Windows XP stops working on a new Windows 11 build, Microsoft’s telemetry flags it, and engineers can create a shim—a thin interception layer that fixes the API call without changing the binary. These shims are distributed via Windows Update and often go unnoticed by end users. Russinovich credited the shim engine with keeping global supply chains running during the Windows 11 rollout, when logistics firms discovered that their warehouse management terminals depended on 32-bit drivers that Windows 11’s memory manager otherwise wouldn’t load. A shim was pushed within 48 hours, and every terminal booted successfully the next morning.

This story encapsulates why Microsoft refuses to deprecate Win32. The global economy runs on a thick layer of custom, unmaintained Win32 executables. Replacing them all with modern UWP or PWA equivalents would cost billions of dollars and introduce unacceptable risk. Instead, Windows 11 continues to host the classic subsystem alongside the newer WinRT-based environments. The architecture of “Windows Core” (the shared kernel across client, server, and Xbox) isolates the Win32 subsystem in a way that keeps it maintainable without letting it drag the entire OS into obsolescence.

Security evolution of Win32

A common criticism of Win32 is that its design predates the internet threat landscape—there are no built-in sandboxing or capability-based security models like those found in UWP. Russinovich addressed this head-on in the video, detailing how Win32 security has evolved dramatically without breaking the API surface. Windows 11’s security baseline for Win32 applications now includes mandatory integrity control, which prevents low-integrity processes from writing to high-integrity objects; Arbitrary Code Guard (ACG), which blocks dynamic code generation and injection in sensitive processes; and Control Flow Guard (CFG), which mitigates return-oriented programming exploits.

Perhaps the most significant advancement is AppContainer, introduced in Windows 8 but increasingly adopted in Windows 11 for classic Win32 apps. While originally designed for Store apps, Microsoft now encourages ISVs to voluntarily containerize their Win32 executables using AppContainer profiles. In 2025, Microsoft released the “Win32 AppContainer Wizard” to simplify the process, and by early 2026, over 200 major enterprise applications had shipped with AppContainer profiles. “We’ve proven you can retrofit modern security onto a classic API surface without a rewrite,” Russinovich said. “Our own tools, like Sysinternals Process Explorer, now run inside an AppContainer by default on Windows 11 SE devices.”

Additionally, Windows Defender Application Control (WDAC) and Smart App Control block untrusted Win32 binaries at the hypervisor level. Together, these technologies mean that a malicious macro in a Word document or a supply-chain-compromised installer can be stopped before it ever gains a thread. The result is a Win32 ecosystem that, in 2026, is far more secure than its reputation suggests.

Web technologies and the Win32 symbiosis

One of the more nuanced points in Russinovich’s talk was how Win32 and the web don’t compete—they cooperate in Windows 11. Electron-based apps, which package Chromium and Node.js into a Win32 executable, now dominate the productivity landscape (Slack, Teams, VS Code, and countless others). These apps rely on Win32 for process management, native file dialogs, system tray integration, and performance-sensitive rendering. Even Progressive Web Apps (PWAs) installed through Edge benefit from Win32: the PWA host process uses Win32 APIs to create shortcuts, register protocol handlers, and integrate with the Windows Share contract.

Microsoft’s own Edge WebView2 control, which embeds Chromium into any Win32 (or WinRT) application, further closes the gap. Developers can build a Win32 UI in C++ or C# and seamlessly host interactive web experiences within it. This hybrid model has become the default for new Windows productivity software; it allows teams to leverage web development skills while still delivering the performance and native integration that users expect. Russinovich called WebView2 “the API that saved Win32 from irrelevance,” arguing that it solved the “rich UI problem” that had driven many developers to abandon native Windows code. With WebView2, a Win32 app can have a modern, fluid UI without sacrificing access to the full power of the operating system.

Moreover, the server side of the web depends heavily on Win32. IIS, the built-in web server, is a Win32 service. .NET Framework (still widely deployed in enterprises) sits atop Win32. Even .NET Core/5+ applications that use Kestrel rely on the Win32 threading and I/O completion ports to achieve their impressive throughput. Azure itself, as Russinovich reminded viewers, uses a custom Windows Server image that strips away unnecessary components but keeps the Win32 kernel and drivers intact. “When we need maximum performance in the cloud, we reach for Win32,” he said.

How Win32 fits in modern Windows 11 development

For the developer community, the question isn’t whether Win32 still exists—it’s how to best use it alongside newer frameworks. The Windows App SDK (formerly Project Reunion) now unifies Win32 and WinRT into a single toolkit. Through the Windows App SDK, a developer can call modern APIs like Geolocation or Bluetooth LE while still leveraging raw Win32 handles for hardware-accelerated graphics via Direct3D 12. This unification means that developers don’t have to choose; they can use the best API for each task.

Russinovich’s team at Azure has contributed several open-source libraries that simplify Win32 development, including a modern C++ wrapper called “wil” (Windows Implementation Libraries) that provides RAII patterns for handles and COM objects. He demonstrated how easy it is to write a high-performance Win32 service in C++ with wil, comparing the code verbosity to similar tasks in Rust or Go. “It’s not about the language—it’s about the surface area. Win32 gives you control over memory, scheduling, and I/O that managed runtimes abstract away,” he said. “For anything that touches the disk or network at scale, you want that control.”

The talk also previewed an upcoming feature in Windows 11 24H2: “Win32 Easy Config,” which allows IT administrators to deploy AppContainer profiles and shim fixes across their entire fleet via Group Policy, without needing to repackage installers. This represents a major step toward making Win32 security and compatibility manageable at enterprise scale, and it underscores Microsoft’s continued investment in the subsystem.

The future of Win32 in a cloud-first world

Looking ahead, the line between local Win32 code and cloud services is blurring. Windows 365 and Azure Virtual Desktop stream entire Win32 desktops to any device, essentially turning Win32 into a cloud-native client. Many enterprises have opted not to rewrite their Win32 apps but to host them in AVD and access them via a Remote Desktop client—which itself is a Win32 application on Windows, and a native app on other platforms. This architecture guarantees another decade of life for Win32, regardless of what paradigm shift comes next.

Russinovich hinted that Microsoft Research is experimenting with a “Win32 on ARM64x” compatibility layer that would eventually allow full emulation of x64 Win32 binaries on custom ARM64 silicon, preserving the backwards-compatibility promise even as the hardware platform shifts. “The contract isn’t tied to x86; it’s tied to the API,” he said. “Our goal is to make sure you can take your 1998 DLL and run it on a 2030 Snapdragon workstation, no questions asked.”

For the average Windows user, none of this architectural heavy lifting is visible. They double-click an .exe and it just works. That simplicity, however, is the product of enormous engineering effort—and it’s exactly what keeps millions of people and businesses locked into the Windows ecosystem. As Russinovich put it, “Win32 isn’t just code; it’s a promise. And we intend to keep that promise for as long as Windows exists.”

In an era of rapid churn in software development, that stability is rare and immensely valuable. The 2026 reaffirmation from one of Microsoft’s most senior technical leaders should reassure developers and IT decision-makers that betting on Win32 remains a sound strategy. The API that defined personal computing for decades is not a relic but a living, evolving platform that continues to bridge the old and the new.