The Hot Take: What about that small file handling, any better on that yet?
Microsoft admitted that File Explorer on Windows 11 is slower than the previous version and is taking steps to make it faster, but the performance improvements extend beyond just UI surfaces. Iâm told that Microsoft is internally testing a major performance boost for file operations, starting with batch deleting files.
When you select dozens or hundreds of smaller files, or a few large files, and delete them all in one go, the speed depends on both the SSD/HDD and Windows.
Windows file system overhead matters as well because the OS has to update NTFS entries, permissions, indexes, thumbnails, metadata, and a bunch of other items when you delete or bulk delete files.
Of course, Iâm not saying a faster Windows alone can magically purge files faster. Hardware still matters, especially the SSDâs random I/O speed when youâre dealing with many small files. But itâs also wrong to say the speed only comes down to SSD I/O. If Windows handles file operations more efficiently, bulk delete can still get noticeably faster.
Microsoft also confirmed that a combination of hardware and software advancements could help make file operations faster on all PCs.
According to Microsoft, bulk deleteâŚ
The Hot Take: OH look at that, suddenly we're getting more performance out of windows. Like they were handy capping it or something to push lets say something like mid-range hardware of the ARM variety....
Microsoft recently released Windows 11 KB5089573 (Build 26200.8524) optional update, and buried inside the lengthy release notes is a major performance upgrade. While the company simply calls it a â[General Performance]â improvement, we know this is the highly anticipated CPU boost feature internally codenamed âLow Latency Profile.â
According to the official changelog released on May 26, 2026, Microsoft notes: â[General Performance] This update accelerates app launch and core shell experiences such as Start menu, Search, and Action Center.â
We already reported that Windows 11 Low Latency Mode is rolling out in June 2026 with the mandatory security update. But as we said, the CPU boost feature will be available in the optional May update as well, so if youâre eager enough to enable it, go to Settings > Windows Update > Advanced options > Optional updates and just select the update to install it.
However, due to Microsoftâs Controlled Feature Rollout (CFR) strategy, the new performance boost may not be activated straightaway even after you install the Windows 11 KB5089573 optional update. Your PC has definitely downloaded the underlying code, but Microsoft often keeps the activation switch turned off for a subset of users to monitor stability.
Fortunately, you do not have to wait for Microsoft to flip the switch remotely. You can manually force the feature on right now using a popular third-party utility called ViveTool.
Note: The Low Latency Profile currently only makes OS flyouts, such as the Start menu, Notification Center, right-click menu, and other areas, load faster. It does not allow your apps to launch faster. That change will roll out in the next update.
How to enable Low Latency Profile in Windows 11
Before you proceed, you need to be sure you have already installed the May optional update.
To verify if the May 2026 optional update is installed, open Settings > System > About, and check the build number. If itâs Build 26200.8524 / 26100.8524 or newer, youâre eligible for Low Latency Profile improvements. Also, the Low Latency Profile does not require any special hardware, but itâs more impactful on budget/low-end PCs.
Now, follow these steps to activate Windows 11âs CPU boost feature:
Get ViveTool by going to the official ViveTool GitHub repository and downloading the latest .zip release.
Extract the contents to a convenient folder. For ease of use, I created a folder called ViveTool directly on my C drive and extracted the files there.
Click the Start menu, type âcmdâ, right-click on Command Prompt, and select Run as administrator.
Type cd C:\ViveTool and press Enter.
Type the following command to activate the feature and press Enter:
vivetool /enable /id:58989092
Restart your PC to apply the changes.
Note: The command uses /enable to turn the feature on. If you ever want to revert the changes, you can repeat the process using /disable instead. This only works for now, and once the feature officially becomes default on your device, you wonât be able to turn it off.
Ideally, we shouldnât have to enable features manually. Since Microsoft already has a vibrant Insider community, all testing should occur earlier, and deployment should begin now. Many users have complained that they still havenât received features rolled out in the April 2026 updates. And since Low Latency Profile is, by definition, just a CPU boost, it should have already arrived by now.
How do you verify if the Low Latency Profile is working?
Windows 11 does not include a toggle to enable or disable the Low Latency Profile. Instead, the feature is enabled by default on all PCs once it rolls out with the May 2026 Update, or if you enable it using the bypass method mentioned above.
As a result, the only way to verify that itâs working is by comparing performance before and after the feature is enabled. Check if the Start menu, Action Center, and Search load faster than before.
We canât rule out a placebo either, so you can also try checking CPU usage before and after Low Latency Profile is enabled:
No CPU boost before Low Latency Profile is enabled:
https://www.windowslatest.com/wp-content/uploads/2026/05/Low-Latency-Profile-CPU-boost-feature-is-disabled.mp4
On the top right side of the screen recording, you can see that the CPU has not reached peak utilization while opening the Start menu or Action Center. I have checked it multiple times to be sure.
After enabling Low Latency Profile using the bypass method given above, I opened the Start menu and Action Center:
CPU utilization peaks while opening the Start menu after Low Latency Profile is enabled:
https://www.windowslatest.com/wp-content/uploads/2026/05/CPU-jumps-to-100-while-opening-Start-menu-after-enabling-Low-Latency-Profile.mp4
Â
As you can see on the top right side, CPU utilization jumps to 100% in the P cores on my Intel Core i5 13420H, and then falls to normal levels in a second or two, which essentially confirms the presence of Low Latency Profile.
CPU reaches 100% while opening the Action Center after Low Latency Profile is enabled:
https://www.windowslatest.com/wp-content/uploads/2026/05/CPU-Boost-while-using-Action-centre-after-enabling-Low-Latency-Profile.mp4
Here, too, you can see that the CPU utilization reaches 100% while opening the Action Center and then falls to normal levels almost immediately.
I have done these tests several times, and after seeing the CPU boost for the Start menu and Action Center only after enabling the feature, it is clear that my system has Low Latency Profile enabled.
Microsoft mentioned General Performance improvements to only the Start menu, Action Center, and Windows Search, so as of now, there is no speed boost while opening inbox apps or third-party apps.
Hands-on: UI smoothness over raw speed (for now)
I previously tested Low Latency Profile in a highly constrained environment, and the CPU Boost feature worked well enough that I felt it could make budget PCs usable. It was a dual-core virtual machine limited to 4GB of RAM. But even then, some actions felt surprisingly responsive because the OS was no longer waiting for the CPU to slowly ramp up to the required speeds.
Before enabling Low Latency Profile CPU boost:
https://www.windowslatest.com/wp-content/uploads/2026/05/Before-Low-Latency-Profile-in-Windows-11.mp4
Yes, you have to be eagle-eyed enough to see the micro-strutters and occasional jitters. But itâs safe to say that most people have first-hand experience with the stuttery Start menu!
But now, after running before-and-after screen recordings on a regular, full-powered daily-driver PC with this new May optional update, the results are slightly different, but I like it.
After enabling Low Latency Profile CPU boost:
https://www.windowslatest.com/wp-content/uploads/2026/05/After-Low-Latency-Profile-in-Windows-11.mp4
The changes may look minute in the screen-recording, but it is definitely noticeable in the real world.
Opening the Start menu is less choppy than before. The Action Center glides onto the screen smoothly, and the notorious rendering delay when bringing up the right-click context menu looks to be significantly reduced. As the official release notes specifically highlight âcore shell experiences,â it appears the Low Latency Profile is currently prioritizing OS fluidity over speeding up inbox or third-party app launches.
Either way, since my regular PC wasnât slow in the first place, it now feels more premium because of the extra smoothness. Also, I didnât notice any heating or battery drain during my testing.
The needless controversy behind Windows 11âs CPU boost
When news of this CPU-spiking feature first broke, several users on social media heavily criticized Microsoft, claiming that artificially boosting the processor was a âlazy fixâ to cover up poorly optimized code.
Microsoft Copilot reaches 97% CPU
However, Microsoft stepped in to clarify the engineering behind it, and we agree. Scott Hanselman defended the technology by explaining the concept of âRace to Sleep.â By instantly spiking the CPU to its maximum frequency for a brief 1 to 3 seconds during a UI interaction, the processor completes the heavy lifting in a fraction of the time, allowing it to return to its low-power idle state much faster.
Hanselman pointed out that Apple uses similar hardware-level scheduling tricks on macOS to make the operating system feel buttery smooth.
Because of this initial public backlash, it makes sense that Microsoft chose to quietly label the feature as âGeneral Performanceâ in the changelog rather than explicitly announcing the âLow Latency Profileâ by its internal codename or sharing specific speed improvement metrics.
Whatâs next for Windows 11 performance improvements?
Windows 11 desktop still hasnât quite reached the flawless 120fps smoothness of modern-day smartphones. This update is a massive step in the right direction. And most importantly, this CPU boost is just one half of a much larger strategy.
As Microsoft commits to native UI for Windows 11, the company is replacing heavy web frameworks with lightweight native code, including in the Start menu. So, when you combine native optimizations with the immediate power delivery of Low Latency Profile, pretty soon, Windows 11 will feel as fast and premium as we expect.
The post Microsoftâs Windows 11 CPU boost is rolling out, and hereâs how to enable it right now appeared first on Windows Latest
The Hot Take: Been saying it for years, Microsoft is pulling Linux into windows on bite at a time. This probably I would assume only accelerates.
Microsoft is turning Azure Linux into a general-purpose, Fedora-based cloud distribution available to all Azure customers, while also productizing Flatcar as Azure Container Linux for immutable container hosts. "When Microsoft joined the Linux Foundation, there was this big conspiracy theory that somehow the Linux Foundation was undermining open source in partnership with Microsoft, and now you announce that you're shipping a Linux distribution," Jim Zemlin, the Linux Foundation's CEO, said in response to Microsoft's surprise announcement. "That's amazing." ZDNet reports: Until now, [Lachlan Everson, Microsoft's Principal Program Manager on Azure's open-source team] noted, "we had Azure Linux only available to third-party customers through AKS specifically, and that was Azure Linux 3.0." Going forward, this will be ACL. Everson emphasized that Azure Linux 4.0 is the culmination of years of internal usage and the evolution of the earlier Mariner distribution. "So we've been running Azure Linux for many years internally, and we got through to 3.0, and we only allowed it on as a container host on AKS. What we've done is make it a general-purpose, so this is all the learnings that we've had in the heritage of Mariner."
Under the hood, Azure Linux 4.0 is based on Fedora Linux and is delivered as an open distribution on GitHub. This code is available now. Yes, Red Hat knows that Microsoft has done this. Everson continued, "So, we made a decision to use Fedora as an upstream, so it's using RPMs in the Fedora ecosystem. Microsoft curates the packages and the supply chain to fit Azure's cloud platform." Microsoft also created "it to be purpose-built for Azure, which integrates vertically into all of our infrastructure to give you the best Azure Linux experience on Azure." While Azure Linux will ship as a VM image, Microsoft is already preparing a developer-friendly path onto Windows desktops: "And as of today, we have it as a VM image for your VM host on Azure. We're going to announce WSL images as well."
While developers will be able to run Azure Linux locally through WSL, Microsoft is not positioning it as a traditional desktop Linux. Asked whether he could run it on his laptop, Everson said: "I will be able to run it on my laptop, or what have you. Yes, on Windows 11." However, when pressed about a desktop experience, Everson was clear that there are "no plans" for a graphical environment. "It's optimized for server-side in the cloud," he said, adding that even on a developer machine, users should expect a lean environment. "Minimal packages, yeah. The idea is that we offer you a consistent experience to do your development on your machine, and that you can take your workloads as you develop them on your machine and run them with VS Code. You can run your applications on that, and know that the platform is the same that you're running on the cloud, so that you have that kind of consistency between environments."
Flatcar itself remains the upstream project, but Microsoft is packaging it for Azure customers. Everson described Flatcar as "purpose-built, immutable, secure by default, production-ready operating system, and Azure Container Linux is the productization of that, but we're still investing in the upstream Flatcar ecosystem and pulling that downstream into a productized exterior experience just for container workloads, so it's a container hosting in AKS." To underscore the immutable model, he added that "Everything's baked in, so there is no package manager. We bake the bits into the immutable, and they're in the immutable version. So Azure Container Linux is the immutable version. So you shouldn't be changing any system packages or any application packages. Anything that you need to change is customer workloads run in containers."
Read more of this story at Slashdot.
The Hot Take: SMS/TXT is going to cause some pain for sure.
For years, typing in a six-digit code sent to your phone has been the universal standard for verifying your identity online. But that era is officially coming to an end in the Windows ecosystem.
In a statement to Windows Latest, Microsoft independently confirmed that itâll stop sending SMS codes for personal accounts.
Now, first spotted by Windows Latest, Microsoft has officially announced that it is pulling the plug on SMS codes for personal accounts. According to a support document quietly published earlier this year, the company is actively phasing out text messages as a method for both two-factor authentication and account recovery.
While the tech giant subtly hinted at this shift in a previous security advisory earlier this year, stating it was âcommitted to advancing security standards,â the newly released documentation explicitly confirms the end of SMS verification.
Moving forward, Microsoft is forcing a transition to passwordless alternatives, mandating the use of passkeys, authenticator apps, and verified secondary email addresses.
Why Microsoft is abandoning SMS authentication
Redmondâs decision to kill off SMS verification comes down to the undeniable fact that text messages are no longer a secure way to protect your digital identity.
In their official advisory, Microsoft states that âSMS-based authentication is now a leading source of fraud.â
âMicrosoft is committed to advancing security standards, and as such, we will start phasing out SMS as a method of authentication and account recovery for personal Microsoft accounts,â Microsoft noted in an advisory spotted by Windows Latest. âMicrosoft believes that the future of authentication is passwordless, secure, and user-friendly.â
Text messages were never designed with modern cybersecurity in mind. They are transmitted in plain text across vulnerable cellular networks, making them highly susceptible to interception.
Furthermore, hackers frequently use SIM-swap attacks, a tactic where a malicious actor tricks your mobile carrier into transferring your phone number to a device they control. Once the transfer is complete, the hacker instantly receives all of your SMS two-factor authentication codes, allowing them to easily hijack your accounts.
To combat this, Microsoft believes the future of account security is entirely passwordless. The company is replacing SMS with passkeys, which are a modern, phishing-resistant security standard.
Unlike traditional passwords or text codes that can be intercepted, passkeys use your deviceâs built-in biometric hardware.
When you sign in using a passkey, you authenticate your identity using Windows Hello facial recognition, a fingerprint scanner, or a localized device PIN. This creates a cryptographic key pair where the private key never leaves your physical hardware, rendering remote phishing attacks virtually impossible.
Depending on your setup, passkeys can be device-bound, meaning the private key never leaves the physical hardware (like your laptopâs TPM chip), or they can be synced across your devices via services like Apple iCloud Keychain or Google Password Manager. This cross-device compatibility ensures that if you lose your phone, your verified email and synced passkeys will still allow you to recover your account safely.
The problem of a forced passwordless transition
On paper, eliminating vulnerable SMS codes in favor of biometric passkeys is an objective win for global cybersecurity. In my daily workflow, the passwordless ecosystem is genuinely fantastic. I use Microsoft Edge, Microsoft Password Manager, and the Microsoft Authenticator app across all my devices. Thanks to the IR camera on my Lenovo laptop, Windows Hello face recognition makes logging into my personal Microsoft account a breeze.
However, Microsoftâs forced transition may cause significant headaches for power users.
As a Windows Insider, I constantly spin up, configure, and manage new virtual machines (VMs) to test software builds.
When I attempt to log into my Microsoft account within these isolated, nested environments, the passkey experience falls apart. Biometric hardware wonât be available on a VM, for obvious reasons, and I do not have access to security keys either. When trying to log in with passkeys via PIN, Iâm always shown an error.
In these highly technical, edge-case scenarios, requesting an SMS code was the ultimate, foolproof fallback. It just worked.
Passwords and SMS codes are ubiquitous. Typing in a six-digit text code is an instinctive, habitual behavior for billions of people. To successfully change a deeply ingrained habit, the replacement technology must be utterly flawless across every conceivable scenario.
Microsoft could drop the forced Microsoft account sign-in during Windows 11 setup; now thatâs one less place where youâll need to sign in!.
Either way, Microsoft will soon begin prompting all personal account holders with a âSign in faster with your face, fingerprint, or PINâ screen, urging them to set up a passkey and verify a backup email address. While losing the convenience of SMS codes may be a bitter pill to swallow for some, it is a necessary step to secure Windows 11 against modern threats.
The post Microsoft is killing SMS codes for Microsoft account sign-in, aggressively pushes passkeys on Windows 11 appeared first on Windows Latest
The Hot Take: Well now, that definitely sucks it was doing that. No wonder people are moving to Linux!
Microsoft is reportedly preparing significant changes to how Windows 11 manages graphics driver installations through Windows Update. The update is intended to address a long-standing issue where the operating system could overwrite newer manually installed GPU drivers with older OEM-certified releases.
The Hot Take: Trying to get those linux converts back?
Microsoft is reportedly developing a new Windows 11 performance optimization feature internally known as Low Latency Profile. The technology is said to be part of the companyâs broader Windows K2 initiative, which focuses on improving responsiveness throughout the operating system.
The Hot Take: So legacy is always a ball and chain keeping you from moving forward faster. We'll see how they drop some of the legacy architecture to modernize the OS.
When you right-click a file in Windows 11 or launch a traditional desktop application, you are interacting with code that predates the commercial internet. The Win32 API, introduced all the way back in the Windows 95 era, is still a significant part of the worldâs most popular desktop operating system. But according to Microsoftâs own leadership, this was never the plan.
First spotted by Windows Latest, in a recent video posted by the official Microsoft Dev Docs account on X, Mark Russinovich, Microsoftâs Chief Technology Officer of Azure and the legendary creator of Sysinternals, admitted that the survival of Win32 is one of the biggest surprises in the companyâs history.
https://www.windowslatest.com/wp-content/uploads/2026/05/Microsoft-statement-on-Win32.mp4
âDid anyone in the 90s expect Win32 to be a first-class API surface in the year 2026? And I think I can safely answer, no,â Russinovich explained. âNobody, I think, would have expected that because we were thinking flying cars and, you know, moon stations by the year 2026, not Win32 that was designed back in Windows 95 days.â
Even as everything in the world has changed, it baffles me that computer code, as old as me, is still relevant when nothing around me feels the same as it did just 10 years ago.
Disk Management Tool is a Win32 application still relevant in Windows 11
So how did a 30-year-old API outlive decades of internal attempts to replace it? According to Russinovich, it all comes down to the massive ecosystem built on top of it. âI think that one of the reasons itâs got the staying power is itâs just a fundamental layer inside of Windows that so many apps have built on⌠itâs kind of bedrock,â he said.
Russinovich pointed to his own Sysinternals tools as proof. Founded in 1996, he noted that he would have âbet a million dollarsâ that his earliest tools wouldnât be relevant in 2026. Instead, they are more relevant than ever. Sysmon, which became an inbuilt feature with the March 2026 update, is actively being integrated directly into Windows, and Zoomit, developed in the early 2000s, remains an incredibly popular utility inside PowerToys today.
Microsoft has a graveyard of Win32 replacements
Several years ago, when I came to know about Win32, the first thing I was told was how robust it was. So, if Win32 is such a capable bedrock, why has Microsoft spent the last twenty years trying to kill it?
Like many of you, I have more Win32 apps on my PC than web apps or apps built in a modern framework. Yes, they are incredibly fast and deeply integrated into the OS hardware, but the fact is, they are notoriously difficult to modernize visually. To keep up with modern user interface expectations, Microsoft desperately needed a new framework.
What followed was a decades-long graveyard of abandoned app frameworks. Microsoft tried MFC (a C++ wrapper), followed by WinForms for .NET developers. While these arenât really Win32 replacements, they were abstractions on top of Win32.
Then came Windows Presentation Foundation (WPF), which was when the actual effort for replacement started and it introduced XAML and hardware-accelerated rendering.
WPF was supposed to be the definitive future of Windows apps, until Silverlight briefly took the spotlight as a cross-platform bet, only to be eventually killed off by the rise of HTML5.
The most aggressive push to replace Win32 came with Windows 8 and the introduction of WinRT. Microsoft wanted developers to build secure, touch-friendly, full-screen apps.
When the Windows 8 UI failed, they redirected to the Universal Windows Platform (UWP) in Windows 10.
Back in my Windows 10 Mobile days, the one thing I used to tell everyone about the app situation in Microsoftâs mobile OS was that UWP would enable a powerful unified platform for apps that work across phones, Xbox, and PCs. Well, that didnât age well.
Also, UWP was too restrictive, heavily sandboxed, and completely alienated traditional desktop developers who needed deep OS access.
As Russinovich noted in his video: â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 that a lot of people expected it to, given thereâs still the separation between thick client and Win32 and the browser, which is HTML and JavaScript.â
Developers still prefer WebView2 for Windows amid the RAM crisis
I asked multiple developers why they continue making RAM-hungry web apps for Windows. That, too, was Microsoftâs fault.
Because Microsoft kept introducing and subsequently abandoning native frameworks, developers simply lost trust in the Windows platform. I explained this in detail in a Windows Latest report, where a developer told me why Windows 11 keeps getting web apps instead of native apps.
WhatsApp web app stuck in the loading screen
I was told that building a native Windows app started to feel like a massive liability. And they canât be blamed. Why invest years into a framework that Microsoft might deprecate tomorrow?
Funnily enough, it was Microsoft that pivoted to the web. Microsoft introduced WebView2, a developer control that essentially embeds the Chromium-based Microsoft Edge engine directly inside desktop applications. Suddenly, the entire OS was flooded with web apps, including Microsoft Teams, Clipchamp, the new Outlook, OneDrive, the Windows 11 Widgets board, and even the latest version of Copilot is a web app.
Copilot in Task Manager
While web apps are cheaper to build and much easier to maintain across multiple platforms, they are fundamentally flawed for desktop computing. Embedding a full browser engine into every individual application is a recipe for disaster when it comes to system resources.
This love for WebView2 and Electron is the reason Windows 11 has become such a memory hog. I use the WhatsApp desktop app every single day, and it is an absolute disaster. In my testing, WhatsApp consumes an absurd amount of RAM when doing absolutely nothing, entirely because it uses heavy web wrappers instead of the lightweight native code it used to use in the UWP era.
Microsoftâs Clipchamp is another web app that I had to use for basic video edits, but I later left it because Microsoftâs built-in video editor now needs OneDrive sync to work!
My frustration is compounded when I compare Windows to macOS. While Apple users enjoy highly optimized, native applications like iMovie or the dedicated Pages suite for free, loyal Windows users like me have no choice but to rely on web-based alternatives like Clipchamp that need a constant internet connection, lack deep OS integration, and eat through system memory.
Microsoft Clipchamp is a WebView2 powered video editor
Fortunately, Appleâs success with a sub $600 budget laptop forced the Redmond giant to rethink their app development priorities.
Microsoft is pivoting back to native apps with WinUI 3
Thankfully, the tide is finally turning. Microsoft has realized that making Windows into a glorified Chrome OS is alienating power users and actively destroying system performance.
A few months ago, Rudy Huyn, a Partner Architect at Microsoft, confirmed he was hiring a team dedicated specifically to building â100% nativeâ apps for Windows 11. The focus has aggressively shifted toward WinUI 3, the latest native UI framework built under the Windows App SDK umbrella.
WinUI 3 is exactly what Microsoft needs to win back developers. It allows them to build gorgeous, modern, Fluent-designed applications that still have full, unrestricted access to the underlying Win32 âbedrock.â Just recently, Microsoft released a massive Windows App SDK 2.0 update, equipping developers with semantic versioning, a refactored Windows ML stack, and much-needed drag-and-drop support for bridging WebView2 content seamlessly into native WinUI 3 shells.
Microsoft is retiring legacy Win32 the right way
Microsoft is finally eating its own dog food and cleaning up Windows 11.
Rather than forcing a hard reboot as they did with WinRT, Microsoft is carefully etching out the oldest, ugliest (some might disagree) Win32 UI elements in Windows 11 and replacing them with highly optimized WinUI 3 native code. We recently discovered that the Windows 95-era File Explorer Properties dialog box is finally getting replaced with a modern WinUI 3 version, complete with full dark mode support.
The legacy Run dialog (Win + R) has been completely rewritten into a blazing-fast WinUI 3 application. After using both versions, I can confidently say that the new Run dialog is as good, if not better, than the old Run dialog, especially considering how beautiful it looks.
Compiled with .NET AOT, the new Run dialog achieves a staggering 94ms median time-to-show, which is surprisingly faster than the old Run dialog, and it proves that modern WinUI 3 frameworks can absolutely match the raw speed and efficiency of legacy Win32 code.
As Microsoft continues to replace heavy WebView2 wrappers with native WinUI 3 components, Windows 11 will inevitably stop consuming so much unnecessary memory. We may not have flying cars or moon stations in 2026, but after decades of missteps, we might finally get a fast, native, and consistent Windows operating system that respects its own legacy.
The post Microsoft admits Windows 11 is still built on 90s-era Win32, and no one saw it coming appeared first on Windows Latest