Windows 11 Still Runs on 30-Year-Old Win32 Code

Key Takeaways

• Win32 API from the mid-1990s still forms the 'bedrock' of Windows 11
• Microsoft's own attempts to replace Win32, like WinRT in Windows 8, failed to gain traction
• Tools written in 1996 using Win32, like Sysmon and ZoomIt, are now part of Windows 11 and PowerToys

Microsoft's CTO Admits the Obvious

Mark Russinovich, Microsoft Azure's Chief Technical Officer, went public with something many developers already suspected. Windows 11 still depends heavily on Win32, the API Microsoft introduced in the mid-1990s.

In a social media post, Russinovich reflected on how unexpected this longevity would have seemed three decades ago. "We were thinking flying cars and moon stations by the year 2026, not Win32," he wrote.

The admission comes as Microsoft faces criticism over Windows performance and reliability. The company has been working to address enthusiast concerns after being slammed for promoting Windows as an "agentic OS" last November.

Why Win32 Survived Every Replacement Attempt

Russinovich doesn't frame Win32 as a problem. He sees it as a foundation that earned its place through sheer utility.

“I think one of the reasons it's got this staying power is just a fundamental layer inside of Windows that so many apps have built on. So many technologies and ecosystems have been built on top of it that it's kind of a bedrock.”

— Mark Russinovich, Microsoft Azure CTO

Microsoft has tried to move beyond Win32 before. The Windows 8 era brought WinRT, an attempt to reboot the Windows API surface. It didn't work out.

"There's been various times in Microsoft's history where we thought we'd reboot the Windows API surface, like WinRT, that actually didn't play out the way a lot of people expected it to," Russinovich explained.

The problem is straightforward. Millions of applications depend on Win32. Replacing it means breaking compatibility with software that businesses and consumers rely on daily. That's a trade-off Microsoft has repeatedly chosen not to make.

Legacy Code, Current Tools

Russinovich pointed to his own work as evidence that old code can stay useful. He wrote Sysmon and ZoomIt in 1996 using Win32. Both tools remain in active use today.

Sysmon is now part of Windows 11's security monitoring. ZoomIt ships with PowerToys, Microsoft's collection of utilities for power users. Russinovich calls them "more relevant than ever in 2026."

This isn't just nostalgia. It's a demonstration of API stability. Code written 30 years ago still runs. That's rare in software.

Strategic Transparency or Damage Control?

The timing of Russinovich's candor is notable. Microsoft is in the middle of what it calls a "major transformation" focused on performance, overhead, and reliability. The company is watching users drift toward macOS and Linux.

Admitting that 30-year-old code runs the show might seem like an odd PR move. But it serves a purpose. By acknowledging what technical users already know, Microsoft positions itself as honest about its challenges.

Whether this translates into actual improvements remains to be seen. The company's recent AI-focused messaging hasn't landed well with users who want a faster, more stable operating system.

What This Means for Developers

For developers, Russinovich's message is clear: Win32 isn't going anywhere. Applications built on it will continue to work. Microsoft isn't planning another WinRT-style upheaval.

That's good news for enterprises with legacy applications. It's less exciting for developers hoping for a cleaner, more modern Windows API. The ecosystem lock-in that makes Win32 durable also makes it difficult to evolve.

Frequently Asked Questions

What is Win32 in Windows 11?

Win32 is the core API (application programming interface) that Windows applications use to interact with the operating system. It was introduced in the mid-1990s and remains the foundation for most Windows software.

Why hasn't Microsoft replaced Win32?

Millions of applications depend on Win32. Replacing it would break compatibility with existing software, which would alienate both enterprise customers and consumers.

What was WinRT and why did it fail?

WinRT was Microsoft's attempt during the Windows 8 era to create a new, modern API to replace Win32. It didn't gain developer adoption because it couldn't match Win32's capabilities or its massive ecosystem of existing applications.

Is Win32 a security risk?

Old code isn't inherently insecure. Microsoft has continuously patched and updated Win32 over three decades. The age of the codebase matters less than ongoing maintenance and security practices.

Will Win32 still be in Windows 12?

Based on Russinovich's comments, yes. Microsoft has no announced plans to deprecate Win32, and the CTO describes it as 'more relevant than ever.'

Source: Latest from Tom's Hardware