If this happens to you, feel free to create an issue at GitHub and one of our amazing community members might be able to help and create the link. The manifests can now create a link between the custom error code from the installer and a set of generic ones the Windows Package Manager understands. They may represent common types of errors like not enough storage or memory. Those 10-digit error codes are often specific to just a single package. You probably wouldn’t want to hunt down exactly what that error code was indicating either. If you are like me, you struggled to understand the 10-digit error code returned by an installer. It’s now possible to map cryptic error messages into something easier to understand.

It may not be exciting to you, but I love being able to run winget import packages.json and go grab a cup of coffee. Most of the video is just scrollbars after that while packages download, install, and upgrade seamlessly. In the first minute, it shows a couple of basic commands, but the key thing to note is the installer URLs exposing the architecture coming from the winget show command. You can see the same familiar experience in a silent video. If a native option is not available, the next best option will automatically be selected. The Windows Package Manager chooses the best available package based on your hardware architecture. We’ve been working to improve the experience for users on ARM64 devices like the Surface Pro X, the Lenovo X13s, or the Samsung Galaxy Book Go. It has been released to the Microsoft Store as an automatic update to the “App Installer” this morning if you’re running Windows 10 (1809+) or Windows 11. Today I have the pleasure of announcing the availability of Windows Package Manager 1.2. We’ve been busy improving the Windows Package Manager.

Windows 11 manager 1.2 0