WinGet Preview 1.11.220 Integrates Official DSCv3 Release Support

Testers can now explore DSCv3 integration in WinGet, as Microsoft has issued preview build 1.11.220 with this experimental feature.

Microsoft pushed out an update to the preview channel for its Windows Package Manager (WinGet), bringing the version number to 1.11.220. Available now via the project’s GitHub releases page, this build introduces initial, experimental backing for the recently finalized Desired State Configuration version 3 (DSCv3). This integration hints at WinGet’s expanding role beyond simple package installation into more complex system setup and management.

DSCv3 Integration Details

Desired State Configuration serves as Microsoft’s framework for infrastructure management using code, enabling administrators to define and maintain specific system states. DSCv3 marks a technical shift.

It’s an open-source, cross-platform application developed in Rust, utilizing JSON or YAML for configurations rather than the MOF (Managed Object Format) files common in earlier, PowerShell-centric versions.

While the WinGet team flags the DSCv3 capability as experimental within this preview, its inclusion allows developers and IT professionals to start evaluating how the package manager leverages this new configuration approach. Notably, DSCv3 offers compatibility pathways for existing PowerShell DSC resources via specific adapters, facilitating a smoother transition for those managing established environments.

Preview Refinements and Other Changes

Beyond the headline DSCv3 feature, version 1.11.220 incorporates several technical adjustments aimed at improving stability and function. The release notes mention corrections for version comparison logic within PowerShell commandlets and fixes specific to ARM64 system builds.

Shadow stack protection, a CPU hardware-level security feature designed to mitigate certain control-flow hijacking attacks, has also been enabled for the tool in this release.

Additional refinements address the sequence of applying registry entries during updates, enhance how failures are handled when reading MSIX package data, and improve the reliability of installer downloads through the WinGet COM API. As part of the overall v1.11 plan, Microsoft has also confirmed the removal of support for 32-bit ARM platforms going forward.

Stable Channel Status and Installation Routes

While preview users explore v1.11.220, the current stable WinGet version remains 1.10.390, issued on April 3, primarily as a servicing update. Features that became stable during the 1.10 cycle included support for private REST sources using Entra ID authentication and expansions to the COM API for source management.

Most users receive WinGet updates automatically via the Microsoft Store’s App Installer package. Accessing preview builds requires participation in the Windows Insider program or the dedicated Windows Package Manager Insider program, though specific releases can also be manually downloaded from GitHub.

Users on older Windows 10 versions might need the VC++ v14 Desktop Framework Package. Further details on the tool are available in the official documentation and the main WinGet CLI repository.

Markus Kasanmascheff
Markus Kasanmascheff
Markus has been covering the tech industry for more than 15 years. He is holding a Master´s degree in International Economics and is the founder and managing editor of Winbuzzer.com.
0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
0
We would love to hear your opinion! Please comment below.x
()
x