Windows 10: Dev Home Installation failed via winget from PowerShell

MTuran · Feb 11, 2024

Hello Everyone:I was trying to install all updates/upgrades via PowerShell Winget, but it failed with below error message:--------------------------------------------------------Installing dependencies: This package requires the following dependencies: - Packages Microsoft.WindowsAppRuntime.1.4 1/4 Found Dev Home Preview [Microsoft.DevHome] Version 0.1001.389.0 This application is licensed to you by its owner. Microsoft is not responsible for, nor does it grant any licenses to, third-party packages. Installing dependencies: 1/1 Found Windows App Runtime [Microsoft.WindowsAppRunti

:)

Sumit (Volunteer Moderator) · Feb 11, 2024

powershell error running winget opens a "open with" window in windows 11

Troubleshooting here:

winget-cli/doc/troubleshooting at master · microsoft/winget-cli · GitHub

Specifically, something related to this:

The App Installer did not automatically add the PATH environment variable. You should add the path environment variable. The value to add is "%userprofile%\AppData\Local\Microsoft\WindowsApps". You can verify this by running %LOCALAPPDATA%\Microsoft\WindowsApps\winget from a command-prompt or & "$env:LOCALAPPDATA\Microsoft\WindowsApps\winget" from a powershell. If the command runs then, but not before, then you very likely have a missing PATH environment component.

Brink · Feb 11, 2024

Windows Package Manager (WinGet) 1.7.2782 Preview Windows 10 and 11

This is the fourth development build after the Windows Package Manager 1.6 build for Windows 10 (1809+) and Windows 11. This build will be released to Windows Insider Dev builds and Windows Package Manager Insiders. Experimental features are enabled in this release. Run winget features to see which experimental features are enabled or disabled. Add the following to your settings (winget settings) file to enable the experimental features. Code:

"experimentalFeatures": {
"directMSI": true
"windowsFeature": true
},
Click to expand...

Windows Package Manager also includes Winget configuration, which automatically handles the setup and configuration requirements for an ideal development environment on your Windows machine. WinGet configuration file helps with installing and managing software packages, applications, programming languages, frameworks, tools, or settings necessary for a project. Check out our session at Microsoft Build to learn how to get your machine to a ready-to-code state. A prerelease version of the Microsoft.WinGet.Client PowerShell module has been published to the PowerShell Gallery and will no longer be included as a release asset. To install the latest version of the PowerShell module, run the following command in PowerShell 7+. Install-Module -Name Microsoft.WinGet.Client The PowerShell module requires App Installer (winget) to be installed. The Repair-WinGetPackageManager cmdlet (work in progress) is designed to install or repair App Installer.
Click to expand...

What's Changed

Platform source should not be blocked by policy check by @yao-msft in #3725

Update docs for upgrade command by @KK-Designs in #3639

Honor 429 Retry-After by @msftrubengu in #3718

New Contributors

@KK-Designs made their first contribution in #3639

Full Changelog: v1.7.2722-preview...v1.7.2782-preview Source: https://github.com/microsoft/winget-...7.2782-preview

RickC · Feb 11, 2024

winget

Yes, installed through app store. It doesn't work in cmd, the new enhanced cmd or powershell.
Click to expand...

Go to Settings > Apps > Apps & features then, in the right-hand pane, click on the link for Manage app execution aliases.

If the winget client has installed properly then you should see this:

If you don't see this then either the installer hasn't added itself to the PATH environment variable or you haven't signed out/signed in (or both... there are issues reported with this first release).

Try installing it again:

https://github.com/microsoft/winget-...bwe.appxbundle

You should see this:

If it installs successfully then you should see this:

In a console (PowerShell or CMD), the command winget list should result in something like this:

Hope this helps...