Windows App SDK Archives

Winsage

June 25, 2026

Making Windows a developer platform, again

Setting up a PC with the base Dev Config has been streamlined for developers, utilizing the Winget configuration service to install applications, execute updates, and apply developer settings on Windows. Users can access setup scripts by cloning a GitHub repository or downloading a zip archive, with clear instructions provided by Microsoft. The installation may require a reboot during the Windows Subsystem for Linux (WSL) installation, but the script resumes automatically afterward. The process installs applications such as PowerShell, Git, GitHub command-line interfaces, Windows App SDK, Visual Studio Code, and language support for Node.js, Python, and .NET. It also includes developer-friendly fonts and a theme engine for Windows Terminal, along with options for customizing File Explorer and the Windows Task Bar. After WSL installation, developers can use WSL Comfort scripts to install additional tools and personalize their Windows Terminal experience. This utility has two phases: the Windows component configures WSL and Ubuntu, while the Linux component fine-tunes the WSL environment, allowing for zsh and starship terminal display tools. It also integrates popular command-line interfaces and supports the Homebrew package installer, targeting existing Ubuntu instances without needing a new Linux distribution installation.

Winsage

June 15, 2026

Microsoft is reportedly testing Copilot+ AI features with discrete GPUs instead of NPUs — a feature available on Windows App SDK with a Windows Insider Experimental Channel build and Developer Mode turned on

Copilot PCs were introduced by Microsoft in 2024 to integrate advanced AI capabilities into personal computing. An experimental Windows App SDK is now available on GitHub, allowing users to run Language Model APIs on supported Nvidia GeForce RTX 30-series GPUs with a minimum of 6GB of VRAM. This capability requires a Windows Insider Experimental Channel and Developer Mode activation, enabling local AI inferencing on devices without dedicated NPU hardware. Microsoft's shift from promoting Copilot+ PCs may be influenced by fluctuating RAM prices and aims to make AI functionalities more accessible to a broader user base. In 2024, a research firm noted that consumer interest in AI PCs was driven by the need to upgrade to available models, a trend continuing into 2026 due to a shortage of memory and storage chips, resulting in rising computer prices and declining sales of PCs and components. Projections indicate that entry-level laptops may disappear by 2028. The lack of consumer interest in NPU-equipped PCs could impede the adoption of Copilot+ features, prompting Microsoft to expand AI functionalities to non-Copilot+ devices to enhance its user base and differentiate Windows 11 from competitors like macOS and Linux.

Winsage

June 12, 2026

Microsoft tests Windows AI features on RTX GPUs, not just NPUs

Microsoft is expanding the availability of its Copilot+ features to users with Nvidia RTX GPUs, allowing older PCs to utilize advanced AI tools such as text summarization, image upscaling, and code generation. This change is facilitated by the experimental release of the Windows App SDK 2.2, which enables AI functionalities to run on dedicated Nvidia RTX GPUs. Features include text rewriting, editing, and advanced capabilities in the Microsoft Photos app. Users must download the experimental version of WinAppSDK 2.2, have an Nvidia GeForce RTX 30 series GPU with at least 6GB of VRAM, and enable Developer Mode on their PC. This shift reflects a broader strategy to leverage local AI models while still using cloud resources, aiming to democratize access to AI capabilities across a wider range of devices.

Winsage

June 11, 2026

Microsoft is bringing AI features to more Windows 11 PCs — just in case you were under the impression that AI was being cut back

Microsoft is testing a new feature that allows developers to implement local language models on non-Copilot+ PCs running Windows 11. The Language Model APIs can now operate on any Windows 11 device with a compatible Nvidia GPU, specifically targeting GeForce RTX 30 series and newer models with at least 6 GB of video RAM. This initiative aims to democratize access to AI capabilities across a broader range of Windows 11 PCs, although not all PCs will gain access to exclusive Copilot+ AI functionalities.

Winsage

June 4, 2026

Microsoft is rewriting Windows 11 shell in native code, killing the web slop slowing your PC

Microsoft is enhancing Windows 11 by reducing reliance on web-based components, which have caused performance issues. The user interface framework WinUI will now be referred to simply as "WinUI," indicating no plans for a WinUI 4, to reassure developers. Microsoft is integrating WinUI into the Windows 11 shell more rapidly, moving away from web components. A specialized team is focused on creating "100% native" Windows applications, starting with an overhaul of the Start menu from React Native to WinUI components. Performance, memory optimization, and quality control are top priorities for the WinUI team. A new system compositor is being introduced to improve UI performance, and enterprise-focused DataGrid and Charting controls are being added to WinUI. Microsoft is expanding open-source development for WinUI, allowing public testing and contributions. Migration support between WinForms and WinUI is being enhanced for legacy applications. An experimental project called Microsoft UI Reactor is introduced to simplify native application development using C#. This shift towards native development aims to improve performance and efficiency for all Windows users.

Winsage

June 2, 2026

Microsoft outs new Windows 11 native command-line utility. Revolutionizes native app making.

Microsoft has announced the general availability of Coreutils for Windows, introducing a native suite of Linux-style command-line utilities designed to enhance cross-platform development workflows. Coreutils includes essential commands for file, shell, and text manipulation, such as ls, cp, mv, rm, cat, and pwd, and will function similarly to its GNU counterpart, allowing seamless use across Windows, Linux, macOS, containers, and the Windows Subsystem for Linux (WSL). Microsoft has excluded certain utilities that rely on POSIX-specific functionality to avoid disrupting Windows operations. Additionally, Microsoft introduced "Windows Development Skills," a set of AI-powered tools aimed at improving the development and maintenance of Windows applications, built on WinUI 3 and the Windows App SDK, and available through a dedicated GitHub repository.

Winsage

May 29, 2026

Microsoft admits modern Windows 11 apps actually resize worse than the old ones, fix coming this summer

Microsoft is working on a solution to address the black tearing issue during window resizing in WinUI 3 applications on Windows 11, with a rollout expected to begin this summer. March Rogers, Microsoft’s Partner Director of Design, confirmed that the Windows team is testing smooth resizing code on native inbox applications before extending the update to the Windows App SDK. The transition to WinUI 3 aims to replace inefficient web applications and improve user experience, with significant components like the Start menu and system-level dialog boxes being upgraded to WinUI 3. Additionally, Microsoft has launched Windows App SDK 2.0 to encourage third-party developers to adopt native app development, addressing previous issues such as bugs and lack of visual features.

Winsage

May 29, 2026

Microsoft admits modern Windows 11 apps actually resize worse than the old ones, fix coming this summer

Microsoft is working to improve the user experience of WinUI 3 applications by addressing the issue of black tearing during window resizing. A fix is planned to be rolled out over the summer, as confirmed by March Rogers, Microsoft’s Partner Director of Design. Currently, WinUI 3 apps exhibit noticeable tearing during resizing, unlike UWP applications that resize smoothly. The Windows team is testing the smooth resizing code on native inbox apps before its broader rollout. Additionally, Microsoft is transitioning away from web-based architectures to enhance native app development, with plans to migrate the Windows 11 Start menu and system-level dialog boxes to WinUI 3. The company aims to rebuild trust with third-party developers through the Windows App SDK 2.0, which introduces new features and simplifies the development process for native applications.

Winsage

May 13, 2026

Microsoft aims to speed Windows with ‘leap forward’ in WinUI 3 perf

Microsoft has announced a 25 percent improvement in the performance of WinUI 3, specifically in File Explorer components. There has been a 41 percent reduction in memory allocations and a 45 percent decrease in function calls. Some optimizations may involve breaking changes, which will initially be optional for developers. The enhancements are intended to become the default in future iterations of WinUI and the Windows App SDK. Despite these improvements, developers have expressed concerns about WinUI 3's performance, noting it is slower than WPF and UWP. The reliance on WinRT interop for component actions is seen as a significant factor hindering speed. Additionally, there are historical tensions regarding the adoption of Microsoft's frameworks within the Windows and Office teams, leading to skepticism about their reliability.

Winsage

May 7, 2026

Microsoft admits Windows 11 is still built on 90s-era Win32, and no one saw it coming

Users engage with the Win32 API when right-clicking files or launching desktop applications in Windows 11, a technology that has persisted since Windows 95. Microsoft’s Chief Technology Officer, Mark Russinovich, noted that the longevity of Win32 was unexpected, as it was not part of the company's original vision for the future. Despite attempts to replace Win32 over the past two decades, many users still have more Win32 applications than modern alternatives. Microsoft has introduced several frameworks to replace Win32, including MFC, WinForms, WPF, WinRT, and UWP, but none have fully succeeded. Developers have shown a preference for RAM-intensive web applications over native ones due to concerns about the stability of Microsoft's frameworks. Microsoft has introduced WebView2 to embed web technologies in desktop applications, leading to increased memory usage. In response to user needs, Microsoft is shifting back to native applications with WinUI 3, aiming to modernize Windows 11 while retaining access to Win32 infrastructure. The company is gradually replacing legacy Win32 UI elements with WinUI 3 components, improving performance and user experience.