The air at Microsoft Build 2025 crackled with a distinct energy, a blend of ambition and a quiet acknowledgment of lessons learned.
A year after the grand unveiling of the Copilot+ PC, and its somewhat rocky start marked by the ill-fated Recall function, Microsoft CEO Satya Nadella stood on stage.
He was not just presenting new features, but articulating a fundamental shift in strategy.
This year, the focus was not just on showcasing what a dedicated Neural Processing Unit (NPU) could do.
It was about democratizing AI across the entire Windows ecosystem, embracing open source, and, crucially, wooing developers back into the fold.
The initial promise of the AI PC, epitomized by the Copilot+ label, felt a bit like a Ferrari without enough roads to truly test its speed.
While all three major silicon vendors now support features like Recall, the critical missing piece has been the vibrant ecosystem of third-party applications truly leveraging the NPU and the AI capabilities embedded within Windows 11.
Microsoft, it seems, has listened.
What was once the Windows Copilot Runtime has now matured into the more robust and aptly named Windows AI Foundry.
At its core lies Windows ML (WinML), an evolution of DirectML, designed to be the universal translator for AI models.
This evolution is perhaps the most significant strategic pivot.
Microsoft is moving beyond the narrow confines of NPU-only acceleration.
WinML, they promise, will allow developers to “bring their own models” and deploy them efficiently across the entire spectrum of PCs – from humble entry-level laptops to formidable high-end AI workstations.
The underlying silicon – be it CPU, GPU, or NPU – will all be fair game for AI acceleration.
This broader approach, while undoubtedly a “heavier lift” for Microsoft in terms of complexity, is a pragmatic move.
It acknowledges the diverse hardware landscape and aims to make AI features accessible to a far wider user base, rather than confining them to a niche of cutting-edge machines.
It is a recognition that the AI revolution needs to be inclusive to truly take hold.
Beyond the architectural shifts, Microsoft’s renewed commitment to open source felt like a breath of fresh air, a stark contrast to some of its historical proprietary tendencies.
The embedding of Anthropic’s open-source Model Context Protocol and the Agent2Agent Protocol into Windows and Azure offerings is a particularly forward-thinking step.
These protocols aim to standardize how AI agents interact with applications and services, laying groundwork for a more interoperable AI future.
Furthermore, the announcement of NLWeb, an open-source project extending agentic user experiences to the internet, signals Microsoft’s intent to bridge the often-disparate worlds of cloud and local device AI.
Perhaps the most resonant news for the developer community was the long-awaited open-sourcing of WSL – the Windows Subsystem for Linux.
Launched in 2016 and popularized by WSL 2 in 2019, WSL has been a lifeline for developers needing to run Linux code on Windows without the overhead of a full virtual machine.
The call to open-source it has been persistent, and its realization is a clear signal that Microsoft is serious about making Windows an easier, more appealing platform for development.
This move, along with the open-sourcing of the new “Advanced Windows Settings” (formerly “Windows Settings for Developers”) on GitHub, underscores a new era of transparency and community engagement.
The Advanced Settings, which give users more granular control over file display and version control, are now accessible to everyone, not just power users.
The health of any platform is ultimately tied to the vibrancy of its app ecosystem.
With the Microsoft Store boasting over 250 million monthly active users, the company is doubling down on developer incentives.
The elimination of the $19 registration fee for individual developers is a low-cost, high-impact move that could inspire a new generation of app creators.
Coupled with the new Store FastTrack program for companies and a commitment to faster, more transparent app certifications, Microsoft is clearly working to smooth out the notoriously bumpy road to app submission.
The enhancements to Windows and Store search, promising more intent-aware results using vector embeddings and semantic ranking, are also critical.
As a user who relies heavily on search to launch applications, the promise of smarter, more accurate discovery is not just a convenience, but a necessity for a seamless user experience.
While the strategic shifts at Build 2025 are commendable, some questions linger.
The continued reliance on the Open Neural Network Exchange (ONNX) AI runtime at the heart of WinML, while ensuring compatibility, might leave some performance on the table, as suggested by the superior speed of Nvidia’s new WinML TensorRT EP.
This is a trade-off Microsoft seems willing to make for broad compatibility, but one that power users might notice.
And then there is Copilot itself.
Despite being central to Microsoft’s AI narrative, its integration still feels somewhat disjointed, particularly on desktops lacking Copilot+ features.
The vision of Copilot as a truly ubiquitous, locally-running assistant, unburdened by constant internet connectivity, remains a future aspiration rather than a present reality.
Nevertheless, Microsoft’s trajectory is clear.
The pivot from a somewhat restrictive, NPU-centric AI vision to a broad, open, and developer-friendly approach is a necessary adjustment in the breakneck pace of the AI race.
By working in lockstep with the ecosystem and addressing past missteps, Microsoft is positioning Windows and Azure to capitalize on the immense productivity potential of AI.
The journey is far from over, but Build 2025 signals a more mature, more inclusive, and ultimately, more promising path for AI on Windows.
Time will tell if this expansive vision truly delivers on the promise of an AI-accelerated experience for all.
-
Frank DiBernardo handles LNGFRM's Foodie and Miscellaneous writing tasks. He's always getting ideas from users, so don't be afraid to send an email to the editor.