Microsoft shipped Windows App SDK 2.2 this July, bringing real-time AI video upscaling and a new storage API for unpackaged desktop apps to the stable channel. The release works on Windows 10 version 1809 and later, a deliberate choice that lets developers modernize native code without waiting for an operating system upgrade — or a hypothetical Windows 12.

The update is part of a broader strategy to decouple app-platform capabilities from the Windows release cycle, a shift that is already changing how teams build and deploy Windows software today.

What’s Inside the SDK 2.2 Release

Windows App SDK 2.2 introduces two notable additions:

  • VideoScaler: a real-time, AI-driven video upscaling API that can improve low-resolution content using on-device machine learning. The feature targets scenarios like media playback, video conferencing, and legacy app enhancement.
  • ApplicationData.GetForUnpackaged(): a WinRT method that gives unpackaged desktop applications — those deployed as plain .exe files rather than MSIX packages — direct access to application-data storage locations. Previously, this was cumbersome for traditional Win32 apps that wanted to use modern Windows capabilities.

The SDK is delivered via NuGet as the Microsoft.WindowsAppSDK package, with the stable version set at 2.2.0. The Windows SDK build associated with this release is 10.0.28000.2270, according to Microsoft Learn documentation. Developers can also install Visual Studio project templates to jump-start integration.

Under the hood, the SDK still depends on runtime components that applications must bundle or rely on from the system. That runtime supports X64, X86, and Arm64 architectures, and it can be deployed alongside an app or installed as a framework package.

What the SDK Means for Developers, IT Admins, and Users

For Developers: Modernize Without a Rewrite

Developers maintaining conventional desktop applications now have a clear path to adopt newer UI frameworks (like WinUI 3), app lifecycle management, notifications, and windowing — all while preserving their existing Win32 code. They can keep their .exe deployment model and selectively bring in APIs from the Windows App SDK.

This incremental approach is far more practical than a platform-mandated, ground-up rewrite. For example, a line-of-business app written in WinForms can add AI video enhancements or use modern storage patterns without abandoning decades of legacy logic. The payoff is a gradual UX refresh that doesn’t force a risky big-bang migration.

Crucially, the SDK is independent of the OS version an end user runs. Developers can target Windows App SDK 2.2 APIs, test them on a Windows 10 1809 machine, and still leverage the same code on Windows 11. This broadens the addressable market and reduces the pressure to wait for a major Windows release to ship new features.

For IT Administrators: A New Dependency to Manage

The Windows App SDK runtime is not bundled with the OS. For unpackaged or externally located packaged apps, IT teams must ensure the correct runtime is installed on target machines. This means adding the runtime installer to deployment workflows, software distribution systems, and gold images.

The runtime follows its own servicing cadence separate from Windows updates. Administrators should treat it like any other application dependency — version-controlled, tested during patching cycles, and documented alongside the app’s own prerequisites. Compatibility is broad (Windows 10 1809+), but runtime installation paths vary across architectures, and testing on all deployed platforms is essential before a wide rollout.

For Users: Smoother Apps, Sooner

End users won’t interact with the SDK directly, but they will experience its benefits. Applications that adopt VideoScaler can deliver clearer video calls or upscaled legacy media on capable hardware. Unpackaged apps gain the ability to store data in a consistent, secure location — reducing clutter and permission issues. Because the SDK reaches back to older Windows 10 builds, these improvements can arrive on devices that haven’t been upgraded to the latest Windows 11 release.

How App Platforms Disconnected from Windows Releases

The Windows app platform has been on a journey from tight OS coupling to independence. For years, major new APIs demanded the latest Windows version: DirectX upgrades required a new OS, and modern UI stacks like UWP were locked to Windows 10. That model frustrated developers who needed to support mixed-version fleets and dragged out adoption cycles.

Microsoft began unwinding this with the Windows App SDK (formerly Project Reunion), aiming to unify Win32 and UWP APIs and ship them outside of the OS. The SDK absorbed components like WinUI 3, push notifications, and app lifecycle management, releasing them on a faster cadence through NuGet. By version 1.0, it supported Windows 10 1809 and above, signaling a commitment to backward compatibility.

Version 2.0, released in 2025, continued that trend and established parallel servicing branches (stable, preview, experimental). SDK 2.2 now builds on that foundation with AI and storage additions that further close the gap between traditional desktop apps and more modern packaging models. The result is a platform that evolves without waiting for a new Windows SKU.

Preparing for the Future Without Speculating on Windows 12

Despite rumors of a “Windows 12” that would reshape development, Microsoft has not announced such a product. The more immediate, tangible shift is the Windows App SDK’s growing capability set and its separation from the OS upgrade cycle. For most teams, planning for an unconfirmed next-gen Windows is a distraction; the actionable work is already here.

What Developers Should Do Now

  • Evaluate the SDK’s fit: Is your app a candidate for incremental modernization? Can you adopt WinUI 3, AI upscaling, or better storage management without a full rewrite? Start a proof-of-concept targeting SDK 2.2.
  • Design with feature detection: If you compile with the latest Windows SDK but run on older Windows, use runtime checks before calling newer APIs. Graceful fallbacks keep the app functional across all supported OS versions.
  • Plan for runtime deployment: For unpackaged or externally packaged apps, integrate the runtime installer into your setup flow. Test on each architecture and OS baseline.
  • Leverage existing code: Keep Win32 interop intact; don’t assume everything must move to WinUI 3 overnight. Mix and match where it makes sense.

What IT Administrators Should Do Now

  • Add the runtime to your software library: Download the latest stable runtime installer and make it available through your distribution tools. Track its version alongside your OS patch levels.
  • Test on your oldest supported build: Ensure apps using SDK 2.2 function correctly on Windows 10 1809. Validate any AI features that may require specific hardware.
  • Update deployment documentation: Clearly separate OS requirements from SDK runtime requirements. This prevents confusion during upgrades and troubleshooting.

What Everyone Should Do About Windows 12 Rumors

Ignore them for now. Until Microsoft publishes an official Windows 12 product announcement, an SDK, a supported-version matrix, and API documentation, any productivity claims are speculation. The real platform innovating is happening in the Windows App SDK, which ships on a predictable schedule and works on the Windows 10 and 11 install base you already manage.

The Road Ahead: AI, Hardware, and Developer Tooling

The AI capabilities in SDK 2.2 highlight a coming wave of machine-learning-driven APIs. As features like VideoScaler become common, apps will increasingly depend on GPUs and NPUs. Developers should design for hardware variability: detect accelerator availability, scale quality or latency accordingly, and always provide a CPU fallback to avoid breaking the experience on lower-end devices.

Microsoft’s recent developer announcements also point to broader workflow improvements. Native Coreutils for Windows, experimental Intelligent Terminal work, planned WSL Containers tooling, and Windows Developer Configurations aim to reduce environment setup time and cross-platform friction. These investments signal that the toolchain — not just the runtime — is getting attention, and they can pay off immediately for teams targeting today’s Windows.

Looking ahead, the next Windows App SDK release will likely continue down the path of more AI integration and tighter packaging flexibility. The SDK’s independent rhythm means those capabilities could arrive in months, not years, and they will work on the devices your users already own. That is the platform story to watch.