WinGet 1.11.510: Microsoft continues to maintain the old stable, quietly but consistently

While the developer community is already working on the new functions of preview version 1.12 of the Windows Package Manager, Microsoft is releasing an unspectacular but highly relevant maintenance update for the stable 1.11 line. The new version 1.11.510 does not bring any visible innovations, but concentrates on corrections in the machine room – quietly, but necessary. The fact that Microsoft is continuing to maintain the stable version, even though the preview is already at an advanced stage, indicates a long-term two-pronged strategy: stable reliability for companies and an experimental playground for developers.

As usual, the update was initially released as a “pre-release”. This allows Microsoft to test compatibility and stability in the field before the build is labeled “Latest” and distributed more widely. This is a very sensible approach, especially as the Windows Package Manager is increasingly being used in productive and automated environments – from DevOps scripts to in-house software distributions. From a technical perspective, the update addresses three points. Firstly, the internal redirects for vcpkg, Microsoft’s open source C package management system, have been adapted. Specifically, compatibility with older vcpkg versions has been restored, which is particularly relevant for developers with fixed build environments. Secondly, the use of static COM memory has been revised. This change has been backported from newer code branches into the stable version – a sign that Microsoft is incorporating concrete stability gains from the preview back into conservative builds. Although COM is a relic from earlier Windows times, it is still deeply anchored in the system – anyone who messes up here risks side effects far beyond package management.

The third fix concerns certificate pinning for the Microsoft Store. The list of valid certificate chains has been adjusted here, presumably in the course of certificate changes on Microsoft’s side. This is transparent for the user, but essential for security: correct handling of certificates protects against compromised connections and is a factor that should not be underestimated, especially in the context of automated installations. The fact that Microsoft is following suit here without making a big fuss shows a certain professionalism – even if the actual communication is, as is so often the case, rather spartan. It is noticeable that many users do not receive the new build immediately – which is less due to the update itself than to Microsoft’s distribution route. The package manager is closely linked to the App Installer, which in turn is updated via the Microsoft Store. This sometimes leads to delays, depending on the region, Windows version and update channel. Comments from the community show that not everyone receives the new version at the same time, which can certainly lead to confusion – especially in corporate environments that rely on consistent versions.

With version 1.11.510, Microsoft proves once again that maintenance does not have to be spectacular to be relevant. This is not about new functions, but about robustness, security and compatibility – in other words, exactly what a package manager is supposed to do at its core. Anyone using WinGet in a productive environment should install the update as soon as possible, if available. Although 1.11.510 is irrelevant for users of the preview version, it serves its purpose as a back-up for stable environments. Quiet but reliable – and that is sometimes worth more than any new function.

Source: DeskModder