Microsoft Azure CTO Mark Russinovich has publicly reaffirmed what many developers have long suspected: Win32, the venerable programming interface born in the Windows 95 era, is not going anywhere. In a Microsoft developer video posted in early May 2026, Russinovich described Win32 as a "first-class foundation" for Windows 11—a striking declaration given the company's decade-long push toward modern app frameworks like UWP and WinUI.

The statement arrived during a technical discussion aimed at developers building for Windows. Russinovich, a renowned systems expert and co-founder of Winternals, emphasized that Win32 remains deeply embedded in the operating system's architecture and will continue to serve as the backbone for countless desktop applications. His remarks cut through years of speculation about the API's gradual phase-out, providing clarity on why a 30-year-old technology still dominates the Windows ecosystem.

The Unshakeable Pillar of Windows

Win32 first emerged with Windows NT and Windows 95, offering a 32-bit API that allowed developers to tap into the core functionality of the operating system. It provided direct access to window management, graphics, file systems, and hardware—a level of control and performance that was revolutionary at the time. Over the years, Win32 evolved to support 64-bit computing, but its fundamental model remained largely unchanged, creating a massive and mature codebase.

Today, Win32 is not merely a legacy compatibility layer. It is the substrate on which Windows itself is built. The Windows kernel, drivers, and system services all rely on the same API surfaces that desktop applications use. File Explorer, Notepad, Paint, and even newer administrative tools all speak Win32. More importantly, thousands of business-critical applications—from Adobe Creative Suite to AutoCAD to proprietary financial software—are written against the Win32 API. Removing or deprecating it would break a staggering amount of software and essentially compel customers to abandon Windows.

Microsoft's own developer guidance, updated alongside Russinovich's video, confirms that Win32 remains the most comprehensive and performant way to build desktop applications. The API offers fine-grained control over threading, memory management, and I/O operations that is simply not available in sandboxed environments like UWP. For power users and enterprises, this performance edge is non-negotiable; it underpins everything from video editing suites to complex engineering simulations.

The Modernization Myth: Why UWP and WinUI Haven't Replaced Win32

When Microsoft introduced the Universal Windows Platform (UWP) with Windows 10, many interpreted it as a death knell for Win32. UWP apps run in isolated sandboxes, offer built-in security features, and can target multiple device form factors. The platform was paired with a new UI framework, WinUI, which promised fluid, Modern-style interfaces. The plan, it seemed, was to eventually shepherd all developers onto this new stack.

Reality proved far more stubborn. UWP's sandboxing prevented the deep system access that many professional applications require. The UI framework, while aesthetically pleasing, could not match the complexity and flexibility of WPF or even raw Win32 controls. Performance overhead, limited API coverage, and a painful migration path meant that most established software vendors stuck with their existing Win32 codebases. Microsoft itself quietly acknowledged the limitations: the company famously ported its own Edge browser from UWP to the Chromium engine, built on—you guessed it—Win32.

Project Reunion (now Windows App SDK) emerged as an attempt to bridge the gap, unifying UWP and Win32 APIs into a single development model. It allows developers to use modern UI components while still accessing the full power of the operating system. Yet even this approach does not retire Win32; it simply layers a more palatable abstraction on top. Russinovich's comments reinforce that the Win32 layer underneath remains intact and essential.

Security: The Giant Caveat

The most persistent criticism of Win32 is its security model. Because Win32 applications run with the full privileges of the user, a bug in one app can compromise the entire system. Malware, buffer overflows, and privilege escalation attacks have been rampant throughout Windows history, with Win32's open memory model enabling everything from drive-by downloads to ransomware. The rise of UWP was partially a response to this: by confining apps in sandboxes, Microsoft sought to reduce the attack surface dramatically.

Russinovich is uniquely qualified to address this tension. As the author of the famed Sysinternals tools and now Azure CTO, he has spent decades analyzing Windows internals and securing cloud environments. In the developer video, he acknowledged the security challenges but pointed to the numerous hardening mechanisms that Microsoft has layered atop the Win32 runtime over the years: Address Space Layout Randomization (ASLR), Data Execution Prevention (DEP), Control Flow Guard, and Arbitrary Code Guard, among others. Windows 11 itself introduces additional protections, such as virtualization-based security (VBS) and hardware-enforced stack protection.

Moreover, he stressed that the move to cloud and containerization—the domain he now oversees—offers a complementary security model. Many Win32 workloads are being migrated to virtual machines and containers, where the heavy lifting of isolation is handled at the hypervisor level rather than by the application framework. This hybrid approach preserves the performance and flexibility of Win32 while mitigating its inherent risks.

The Azure Perspective: Containers, VMs, and Win32 Longevity

Russinovich's vantage point as Azure CTO gives his endorsement of Win32 an unexpected twist. Cloud-native workloads often run on Linux in containers, but Windows remains dominant in enterprise desktop and legacy server roles. Many Windows Server applications—and by extension, Azure VMs—are intricately tied to the Win32 API. The Azure Stack family, SQL Server, and countless middleware products expose this dependency.

Containers on Windows (Windows Containers) further illustrate the symbiotic relationship. A Windows container can run a process-isolated environment that efficiently shares a common kernel; inside, that application typically leans on Win32 to function. The container image might include the full .NET Framework, COM components, and other Win32 artifacts. In other words, Win32 is the unseen engine powering many Azure workloads, not just traditional desktops.

Russinovich's affirmation is therefore pragmatic: the massive installed base of Win32 software is an asset Microsoft intends to preserve, not discard. Future innovations around Windows 365 and Cloud PC simply extend the reach of Win32 applications into the browser via streaming, but they do not alter the fundamental API reliance.

What the Community Is Saying

Although no windowsforum_content was available at the time of writing, the developer community has long debated the future of Win32. Common sentiments on platforms like Reddit and Microsoft's own Developer Community echo Russinovich's realism. Many developers report frustration with the shifting messaging around UWP and WinUI, feeling they were urged to adopt technologies that later faltered. There is relief in hearing a senior executive confirm that the Win32 investment remains safe.

Independent software vendors (ISVs) have been particularly vocal. For them, rewriting a decade-old Win32 codebase into a modern framework does not just entail financial cost; it risks introducing bugs, losing feature parity, and alienating power users who depend on advanced capabilities. The CTO's statement serves as de facto permission to continue building and maintaining Win32 applications without fear of imminent deprecation.

However, community feedback also highlights areas where Win32 shows its age. High-DPI scaling remains a persistent headache, and multi-monitor setups can expose quirks in classic window management. Accessibility and dark mode support require extra effort compared to modern frameworks. Developers want Microsoft to invest in smoothing these rough edges rather than chasing replacement APIs.

Practical Impact on Windows 11 Development

Windows 11 itself venerates this dual approach. The operating system ships with a refreshed user interface that includes modern shells and widgets, but those shells are often built upon the same trusted system calls. The new taskbar and Start menu, for instance, communicate with the underlying Windows shell services—services that are exposed via Win32 interfaces to third-party tools. Classic utilities like PowerToys, popular among enthusiasts, tap deep Win32 hooks to enhance productivity.

For IT administrators, the news reinforces that Group Policy, PowerShell, and other management tooling will continue to rely on backend components rooted in the Win32 world. Even Microsoft's own Intune and Endpoint Manager configurations ultimately touch APIs that originated decades ago. The message is clear: investing in Win32 knowledge and tooling pays dividends for the foreseeable future.

Looking Ahead: Will Win32 Ever Fade?

The question inevitably arises: could a Windows 12 or future release finally sunset the Win32 API? Based on Russinovich's remarks and the deep integration throughout the stack, the answer is a resounding no. More likely, Windows will continue to provide a robust compatibility shim layer alongside modern alternatives. As long as enterprises demand support for line-of-business applications that are costly to replace, the OS must maintain backward compatibility.

Microsoft's strategy seems to center on improving the security boundaries around Win32 rather than eliminating the API. Technologies like Windows Sandbox, which creates a lightweight desktop environment completely isolated from the host, offer a way to run questionable Win32 executables safely. Combined with Defender's enhanced machine learning and attack surface reduction rules, these mitigations provide a practical defense without breaking the ecosystem.

Industry analysts note that Apple's macOS has successfully coexisted with a mature API (Cocoa) while gradually introducing SwiftUI. However, Apple enjoys tighter hardware control and a smaller legacy enterprise footprint. Windows' vast diversity of hardware and software, coupled with its market share of over 70% on desktop, makes any radical deprecation plan extremely unlikely. Russinovich's acknowledgment is simply a formal acceptance of this reality.

Conclusion

Mark Russinovich's straightforward assessment that Win32 remains a first-class citizen in Windows 11 should come as a relief to millions of developers and businesses. Rather than signaling a lack of innovation, it reflects a mature understanding of how operating systems evolve: through layering and incremental improvement, not through breaking changes. Windows continues to be the world's most popular desktop OS precisely because it runs an enormous corpus of existing software. The Azure CTO's remarks affirm that Microsoft intends to keep that promise.

For developers, the takeaway is pragmatic. Win32 is not a dead technology to be abandoned but a powerful foundation to be leveraged and, where necessary, secured. As Microsoft continues to shore up defenses and bridge old and new frameworks with projects like Windows App SDK, the API that began its journey in the mid-1990s will continue to serve as the engine room of Windows well into the next decade.