While you right-click a record in Home windows 11 or release a conventional desktop utility, you’re interacting with code that predates the industrial web. The Win32 API, offered all of the long ago within the Home windows 95 period, remains to be an important a part of the arena’s most well liked desktop working device. However consistent with Microsoft’s personal management, this used to be by no means the plan.
First noticed through Home windows Newest, in a contemporary video posted through the professional Microsoft Dev Doctors account on X, Mark Russinovich, Microsoft’s Leader Generation Officer of Azure and the mythical author of Sysinternals, admitted that the survival of Win32 is likely one of the largest surprises within the corporate’s historical past.
“Did any person within the 90s be expecting Win32 to be a firstclass API floor within the 12 months 2026? And I believe I will safely solution, no,” Russinovich defined. “No one, I believe, would have anticipated that as a result of we have been pondering flying automobiles and, you realize, moon stations through the 12 months 2026, now not Win32 that used to be designed again in Home windows 95 days.”
At the same time as the entirety on this planet has modified, it baffles me that laptop code, as outdated as me, remains to be related when not anything round me feels the similar because it did simply 10 years in the past.
So how did a 30-year-old API outlive a long time of interior makes an attempt to switch it? In line with Russinovich, all of it comes all the way down to the large ecosystem constructed on most sensible of it. “I believe that one of the most causes it’s were given the endurance is it’s only a elementary layer inside Home windows that such a lot of apps have constructed on… it’s more or less bedrock,” he stated.
Russinovich pointed to his personal Sysinternals equipment as evidence. Based in 1996, he famous that he would have “wager 1,000,000 greenbacks” that his earliest equipment wouldn’t be related in 2026. As a substitute, they’re extra related than ever. Sysmon, which changed into an in-built characteristic with the March 2026 replace, is actively being built-in immediately into Home windows, and Zoomit, evolved within the early 2000s, stays a shockingly standard application within PowerToys nowadays.
Microsoft has a graveyard of Win32 replacements
A number of years in the past, once I got here to learn about Win32, the very first thing I used to be instructed used to be how powerful it used to be. So, if Win32 is one of these succesful bedrock, why has Microsoft spent the closing 20 years looking to kill it?
Like lots of you, I’ve extra Win32 apps on my PC than cyber web apps or apps in-built a contemporary framework. Sure, they’re extremely instant and deeply built-in into the OS {hardware}, however the truth is, they’re notoriously tricky to modernize visually. To stay alongside of trendy consumer interface expectancies, Microsoft desperately obligatory a brand new framework.
What adopted used to be a decades-long graveyard of deserted app frameworks. Microsoft attempted MFC (a C++ wrapper), adopted through WinForms for .NET builders. Whilst those aren’t truly Win32 replacements, they have been abstractions on most sensible of Win32.
Then got here Home windows Presentation Basis (WPF), which used to be when the true effort for alternative began and it offered XAML and hardware-accelerated rendering.
WPF used to be meant to be the definitive long term of Home windows apps, till Silverlight in short took the highlight as a cross-platform wager, most effective to be in the end killed off through the upward push of HTML5.
Probably the most competitive push to switch Win32 got here with Home windows 8 and the creation of WinRT. Microsoft sought after builders to construct protected, touch-friendly, full-screen apps.
When the Home windows 8 UI failed, they redirected to the Common Home windows Platform (UWP) in Home windows 10.
Again in my Home windows 10 Cellular days, the only factor I used to inform everybody concerning the app scenario in Microsoft’s cellular OS used to be that UWP would permit an impressive unified platform for apps that paintings throughout telephones, Xbox, and PCs. Smartly, that didn’t age neatly.
Additionally, UWP used to be too restrictive, closely sandboxed, and entirely alienated conventional desktop builders who obligatory deep OS get right of entry to.
As Russinovich famous in his video: “There’s been quite a lot of instances in Microsoft’s historical past the place we idea we’d reboot the Home windows API floor like WinRT that in reality didn’t play out the best way that a large number of folks anticipated it to, given there’s nonetheless the separation between thick consumer and Win32 and the browser, which is HTML and JavaScript.”
Builders nonetheless favor WebView2 for Home windows amid the RAM disaster
I requested a couple of builders why they proceed making RAM-hungry cyber web apps for Home windows. That, too, used to be Microsoft’s fault.
As a result of Microsoft stored introducing and due to this fact leaving behind local frameworks, builders merely misplaced consider within the Home windows platform. I defined this intimately in a Home windows Newest record, the place a developer instructed me why Home windows 11 helps to keep getting cyber web apps as an alternative of local apps.
I used to be instructed that construction a local Home windows app began to really feel like a large legal responsibility. And they are able to’t be blamed. Why make investments years right into a framework that Microsoft may deprecate the next day to come?
Funnily sufficient, it used to be Microsoft that pivoted to the cyber web. Microsoft offered WebView2, a developer keep watch over that necessarily embeds the Chromium-based Microsoft Edge engine immediately within desktop packages. Abruptly, all the OS used to be flooded with cyber web apps, together with Microsoft Groups, Clipchamp, the brand new Outlook, OneDrive, the Home windows 11 Widgets board, or even the most recent model of Copilot is a cyber web app.
Whilst cyber web apps are inexpensive to construct and far more uncomplicated to handle throughout a couple of platforms, they’re essentially incorrect for desktop computing. Embedding a complete browser engine into each and every person utility is a recipe for crisis with regards to device assets.
This love for WebView2 and Electron is the explanation Home windows 11 has change into one of these reminiscence hog. I exploit the WhatsApp desktop app each and every unmarried day, and it’s an absolute crisis. In my checking out, WhatsApp consumes an absurd quantity of RAM when doing completely not anything, completely as it makes use of heavy cyber web wrappers as an alternative of the light-weight local code it used to make use of within the UWP period.
Microsoft’s Clipchamp is every other cyber web app that I had to make use of for fundamental video edits, however I later left it as a result of Microsoft’s integrated video editor now wishes OneDrive sync to paintings!
My frustration is compounded once I evaluate Home windows to macOS. Whilst Apple customers experience extremely optimized, local packages like iMovie or the devoted Pages suite free of charge, dependable Home windows customers like me don’t have any selection however to depend on web-based choices like Clipchamp that want a consistent web connection, lack deep OS integration, and consume thru device reminiscence.
Thankfully, Apple’s luck with a sub $600 price range pc pressured the Redmond massive to reconsider their app construction priorities.
Microsoft is pivoting again to local apps with WinUI 3
Fortunately, the tide is in the end turning. Microsoft has learned that making Home windows right into a glorified Chrome OS is alienating energy customers and actively destroying device efficiency.
A couple of months in the past, Rudy Huyn, a Spouse Architect at Microsoft, showed he used to be hiring a workforce devoted particularly to construction “100% local” apps for Home windows 11. The focal point has aggressively shifted towards WinUI 3, the most recent local UI framework constructed below the Home windows App SDK umbrella.
WinUI 3 is strictly what Microsoft must win again builders. It lets them construct stunning, trendy, Fluent-designed packages that also have complete, unrestricted get right of entry to to the underlying Win32 “bedrock.” Only recently, Microsoft launched a large Home windows App SDK 2.0 replace, equipping builders with semantic versioning, a refactored Home windows ML stack, and much-needed drag-and-drop fortify for bridging WebView2 content material seamlessly into local WinUI 3 shells.
Microsoft is retiring legacy Win32 the precise manner
Microsoft is in the end consuming its personal pet food and cleansing up Home windows 11.
Moderately than forcing a troublesome reboot as they did with WinRT, Microsoft is thoroughly etching out the oldest, ugliest (some may disagree) Win32 UI parts in Home windows 11 and changing them with extremely optimized WinUI 3 local code. We lately found out that the Home windows 95-era Document Explorer Homes conversation field is in the end getting changed with a contemporary WinUI 3 model, whole with complete darkish mode fortify.
The legacy Run conversation (Win + R) has been totally rewritten right into a blazing-fast WinUI 3 utility. After the usage of each variations, I will with a bit of luck say that the brand new Run conversation is as just right, if now not higher, than the outdated Run conversation, particularly bearing in mind how stunning it seems.
Compiled with .NET AOT, the brand new Run conversation achieves a staggering 94ms median time-to-show, which is strangely quicker than the outdated Run conversation, and it proves that trendy WinUI 3 frameworks can completely fit the uncooked velocity and potency of legacy Win32 code.
As Microsoft continues to switch heavy WebView2 wrappers with local WinUI 3 parts, Home windows 11 will inevitably prevent eating such a lot pointless reminiscence. We won’t have flying automobiles or moon stations in 2026, however after a long time of missteps, we may in the end get a quick, local, and constant Home windows working device that respects its personal legacy.
