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
Read the full article
The Hot Take: APU's competition starting to heat up for that Ai dollar.
Intel's next-generation Razor Lake-AX chips will compete directly against AMD's Medusa Halo while featuring on-package memory. Intel Is Bringing Back On-Package Memory With Its Next-Gen Razor Lake-AX Chips That Fight Against AMD's Medusa Halo On-Package Memory was last used by Intel for its Lunar Lake SoCs. These SoCs were aimed at low-power mobile platforms, and while the chips themselves offered solid performance in a 30W budget, Intel's next on-package memory solution will be a big one. As per Haze2K1 on X, Intel Razor Lake-AX SoCs will feature on-package memory. This is a big deal as moving the DRAM closer to [âŚ]Read full article at https://wccftech.com/intel-resurrects-on-package-memory-with-razor-lake-ax-to-hunt-down-amd-medusa-halo/
Read the full article
The Hot Take: All while the consumer market is high and dry.
Micron has started to ship its fastest DDR5 RDIMM memory modules, which feature 256 GB capacities & up to 9200 MT/s speeds. Micron Offers 40% Boost Vs Current "In-Volume" DDR5 RDIMM Memory Modules, Brings 256 GB Capacities With 9200 MT/s Speeds As Agentic AI requirements grow, memory makers are rolling out faster and higher-capacity memory kits to meet the demands of AI firms. JEDEC is also pushing the DDR5 MRDIMM standard up to 12,800 MT/s, and today, Micron has announced that it is sampling its 256 GB DDR5 RDIMM modules with up to 9200 MT/s speeds. The main highlights include: [âŚ]Read full article at https://wccftech.com/micron-doubles-down-on-ai-memory-256-gb-ddr5-rdimms-hitting-9200-mtps/
Read the full article
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.
Read the full article
The Hot Take: AMD seems to be out performing Intel & Nvidia on the market, while Nvidia is still the preferred Ai holy-grail? Just seems odd.
While Nvidia has dominated the "infrastructure boom" since 2022's launch of ChatGPT and "the generative AI craze," CNBC writes that "This week offered the starkest illustration yet of what MIzuho analyst Jordan Klein said could be a 'changing of the guard in AI.'"
Chipmakers Advanced Micro Devices and Intel notched gains of about 25%, while memory maker Micron jumped more than 37% and fiber-optic cable maker Corning climbed about 18%. All four of those companies have more than doubled in value this year, with Intel leading the way, up well over 200%. Nvidia, meanwhile, is only slightly ahead of the Nasdaq in 2026, gaining 15% for the year, aided by an 8% rally this week. In spreading the wealth to a wider swath of hardware companies, investors are clearly betting that the bull market in AI has long legs and that data centers are going to need a wider array of advanced components for years to come.
Memory has been the biggest theme of late due to a global shortage that's driven up prices and turned Micron, a 47-year-old company tucked in a sleepy corner of the semiconductor market, into one of the hottest trades over the past 12 months. Micron blew past an $800 billion market capitalization for the first time this week, and the stock is now up over 750% in the past year. CEO Sanjay Mehrotra told CNBC in March that key customers are only getting "50% to two-thirds of their requirements" because of supply issues. The memory market is largely dominated by Micron, along with Korea-based Samsung and SK Hynix, which are also both in the midst of historic rallies...
Bank of America estimates the data center CPU market could more than double from $27 billion in 2025 to $60 billion in 2030. AMD's quarterly results this week underscored the emerging trend, as earnings, revenue and guidance sailed past estimates on strong data center growth. The company has long led the CPU charge, and CEO Lisa Su said on the earnings call that AMD now expects 35% growth over the next three to five years in the server CPU market, up from a forecast of 18% growth that the company provided in November.
The article cites two other big movers:
Intel "is in the midst of a revival sparked by a major investment from the U.S. government last year. Intel's stock had its best month on record in April, more than doubling, and has continued notching massive gains, rising 33% in the early days of May."
Nvidia still remains the world's most valuable company "and is expected to show revenue growth of 70% this fiscal year," the article points out â adding that companies like Corning are also benefiting from Nvidia partnerships. "Glass maker Corning, which celebrated its 175th anniversary this week, signed a massive deal with Nvidia on Wednesday that involves the development of three new U.S. factories dedicated entirely to optical technologies... likely a major step in Nvidia's move away from copper cables and towards fiber-optic cables as it builds out its rack-scale systems."
Read more of this story at Slashdot.
Read the full article
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.
Read the full article
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
Read the full article