Describe the feature or improvement you're requesting

It would be nice to include an option to also install the WinGet PowerShell module (Microsoft.WinGet.Client) after WinGet is installed.

Additional context

No response

One additional suggestion for this: Would you mind, changing $uri to "https://api.github.com/repos/microsoft/winget-cli/releases/latest" ?
Currently the code (which runs awesome!) installs pre-releases.

Originally posted by @obnys in #1 (comment)

WARNING! An error occurred during installation!

###################################################

WARNING: Something went wrong. If messages above don't help and the problem persists,
WARNING: Please open an issue at https://github.com/asheroto/winget-install/issues
WARNING: Line number : 434
WARNING: Error: Deployment failed with HRESULT: 0x80073CF6, Package could not be registered.

error 0xC0020036: windows.licensing failed to start ClipSvc. Try again and contact the package publisher if the problem
persists.

NOTE: For additional information, look for [ActivityId] 6531d6de-ce87-000a-5ee3-3e6587ced901 in the Event Log or use
the command line Get-AppPackageLog -ActivityID 6531d6de-ce87-000a-5ee3-3e6587ced901

Hello. I have winget, but I decided to run this script to test it and I get this error. The error appears if the system language is Russian. If the system language is English, then there is no problem. Sorry for bad English.

Script verson 3.0.0
Windows 22H2
UAC disable
Powershell 5.1
Run as admin

Describe the feature or improvement you're requesting

Waiting 5 seconds to exit when winget is already installed is not the best for automated installs, could we have a parameter to override this? Not sure why it would need 5 seconds after its essentially done everything?

Thank-you!

Additional context

No response

When installing on a new Windows 2022 server the installation completes successfully, but winget will not run.

The issue seems to be caused by a missing license file:

The issue has earlier been reported in winget repo:
microsoft/winget-cli#700

The issue seems to be caused by the change where the script now uses Add-AppxPackage instead of Add-AppxProvisionedPackage:

Add-AppxPackage doesn't support adding a license file.
The PowerShell script only downloads the license file from Winget but never uses it.

I have locally changed the above mentioned line to:
Add-AppxProvisionedPackage -Online -PackagePath $wingetPath -LicensePath $wingetLicensePath -ErrorAction SilentlyContinue

and it works on the server I tested on

What is the license for this project?

Script verson 1.0.1
Windows 22H2
UAC disable
Powershell 5.1
Run as admin

PS E:\Documents\scripts> winget-install.ps1

##########################################

Downloading & installing x64 VCLibs...

##########################################

##########################################

Downloading & installing x64 VCLibs...

##########################################

URL: https://aka.ms/Microsoft.VCLibs.x64.14.00.Desktop.appx

###########################################

Downloading & installing x64 UI.Xaml...

###########################################

Downloading: https://www.nuget.org/api/v2/package/Microsoft.UI.Xaml/2.7.3
Saving as: C:\Users\Akashdeep\AppData\Local\Temp\Microsoft.UI.Xaml.2.7.3.nupkg

###################################################

WARNING! An error occurred during installation!

###################################################

WARNING: Something went wrong. If messages above don't help and the problem persists,
WARNING: Please open an issue at https://github.com/asheroto/winget-install/issues
WARNING: Line number : 375
WARNING: Error: Unable to connect to the remote server

It seems there might be a limitation of using this script as the SYSTEM account. I don't know if this is a limitation of winget itself or the installer. If it's winget, you might consider to put a check in the install to check if it's being ran as SYSTEM. If not, could it be added?

I've tried to run the script on several PCs. Not had any issues historically until yesterday. Now I just can't get winget to install. I get the same output as the readme. Failed getting latest UI.Xaml... Using hardcoded version 2.8.4 etc

However, despite many reboots, I just cannot get winget to install anymore.

I've tried 3 different builds on Windows 10 (Windows 10 Education - 22H2)

1. Custom ISO updated to April 2023 (NTLite)
2. Custom ISO updated to July 2023 (NTLite)
3. Untouched ISO downloaded directly from VLSC - Updated July 2023

Also tried forcing the install using Chris Titus' script and I just get the message "Winget install failed".

Any ideas?

I hit this error during the last steps, where the script tries to install winget:

PS C:\WINDOWS\system32> winget-install
##################################################

Downloading Xaml nupkg file...

##################################################

Downloading https://www.nuget.org/api/v2/package/Microsoft.UI.Xaml/2.8.4
Saving as: C:\Users\MyUser\AppData\Local\Temp\Microsoft.UI.Xaml.2.8.4.nupkg.zip

Expanding: C:\Users\MyUser\AppData\Local\Temp\Microsoft.UI.Xaml.2.8.4.nupkg.zip
Into: C:\Users\MyUser\AppData\Local\Temp\Microsoft.UI.Xaml.2.8.4

##################################################

Downloading & installing x64 VCLibs...

##################################################

##################################################

Installing x64 XAML...

##################################################

Installing Appx Packages In: C:\Users\MyUser\AppData\Local\Temp\Microsoft.UI.Xaml.2.8.4\tools\AppX\x64\Release

Installing Appx Package: Microsoft.UI.Xaml.2.8.appx

Retrieving download URL for winget from GitHub...

##################################################

Downloading winget...

##################################################

Downloading:
https://github.com/microsoft/winget-cli/releases/download/v1.4.11071/Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle
Saving as: C:\Users\MyUser\AppData\Local\Temp\winget.msixbundle

Downloading:
https://github.com/microsoft/winget-cli/releases/download/v1.4.11071/5d9d44b170c146e1a3085c2c75fcc2c1_License1.xml
Saving as: C:\Users\MyUser\AppData\Local\Temp\license1.xml

##################################################

Installing winget...

##################################################

Installing package: C:\Users\MyUser\AppData\Local\Temp\winget.msixbundle

Something went wrong. Please try again or open an issue at https://github.com/asheroto/winget-install/issues
Line number: 251
Error: The parameter is incorrect.

Checklist

• I have performed the steps in the Troubleshooting section and confirm that the issue only occurs with this script.

• I have restarted my computer to confirm this is not a transitory problem.

• I have verified that I am using the latest version of winget-install.

• I have verified that this issue is NOT security related (please create security advisory if so).

• I have run the script with the -DebugMode argument and included the output below

What You Are Seeing?

Running the script on Windows 11 23H2 Enterprise multi-session (for Azure Virtual Desktop) Azure Marketplace image. The script returns this error:

winget requires Windows Server 2022 or newer on server platforms. Your version of Windows Server is not supported.

Running with -Force or -Debug returns same error.

I think the problem is the EditionID is ServerRdsh.

System Details

Azure Marketplace image:
Windows 11 (23H2) Enterprise multi-session + Microsoft 365 Apps - Gen2 (multi-session)
February Windows update installed
See Additional Context for details

Additional Context

PS C:> $osDetails = Get-CimInstance -ClassName Win32_OperatingSystem
PS C:> $osDetails
SystemDirectory Organization BuildNumber RegisteredUser SerialNumber Version

C:\Windows\system32 22631 00432-70000-00001-AA416 10.0.22631

PS C:> Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion"
SystemRoot : C:\Windows
BaseBuildRevisionNumber : 1
BuildBranch : ni_release
BuildGUID : ffffffff-ffff-ffff-ffff-ffffffffffff
BuildLab : 22621.ni_release.220506-1250
BuildLabEx : 22621.1.amd64fre.ni_release.220506-1250
CompositionEditionID : Enterprise
CurrentBuild : 22631
CurrentBuildNumber : 22631
CurrentMajorVersionNumber : 10
CurrentMinorVersionNumber : 0
CurrentType : Multiprocessor Free
CurrentVersion : 6.3
DisplayVersion : 23H2
EditionID : ServerRdsh
EditionSubManufacturer :
EditionSubstring :
EditionSubVersion :
InstallationType : Client
InstallDate : 1709571506
ProductName : Windows 10 Enterprise multi-session
ReleaseId : 2009
SoftwareType : System
UBR : 3155
PathName : C:\Windows
PendingInstall : 0
ProductId : 00432-70000-00001-AA416
DigitalProductId : {164, 0, 0, 0...}
DigitalProductId4 : {248, 4, 0, 0...}
InstallTime : 133540451065555457
PSPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion
PSParentPath : Microsoft.PowerShell.Core\Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT
PSChildName : CurrentVersion
PSDrive : HKLM
PSProvider : Microsoft.PowerShell.Core\Registry

Full Output With -DebugMode

No response

Describe the feature or improvement you're requesting

Hello! We know that when restarting in conhost from the terminal with -ForceClose param, the script window automatically closes after completion.

Now I'm see that this behavior exists even in normal mode without a restarting with -ForceClose param. So for example this won't work:

Perhaps it makes sense to add a -NoExit param that would disable automatic exit after completion.

Of course, this still probably won't work after restarting from Terminal in Conhost with -ForceClose param, but the script warns about this, so it's okay.

Additional context

No response

Thank you for this. Great and very helpful. Any idea why it does not work for server 2019 as-is? ( It should .. )
BTW the following GIST from @likamrat (Lior Kamrat) does work for server 2019 also.

https://gist.github.com/likamrat/cae833a6e5b3461709f14c093c21c293

But I don't like his use of the "https://store.rg-adguard.net/api/GetFiles" to get some of the downloads ... I thought I post it here in case it helps you figure out why yours does not work on server 2019?

what service do i need to enable for it to be working
im using RekOs 0.4v

Checklist

• I have performed the steps in the Troubleshooting section and confirm that the issue only occurs with this script.

• I have restarted my computer to confirm this is not a transitory problem.

• I have verified that I am using the latest version of winget-install.

• I have verified that this issue is NOT security related (please create security advisory if so).

• I have run the script with the -DebugMode argument and included the output below

What You Are Seeing?

While winget will install with this script with winrm. it is not useable.
any attempt to use winget via winrm will be unable to actually update source lists & unable to accept any source agreement.

someone documented an alternative method of setup here: microsoft/winget-cli#256 (comment)

it would be nice if this method could be included in the winget-install script as an alternative install method flag for people wanting to use winget via winrm.

System Details

windows 2k22 server latest

issue detected when setting up an os with packer which uses winrm to manage the VM its building out

Additional Context

No response

Full Output With -DebugMode

due to the packer setup its quite difficult for me to get these logs as the build fails and the VM is deleted

What You Are Seeing?

Hello again! :)

So if i use iex "& { $(iwr asheroto.com/winget) } -Force -ForceClose" command in Windows Terminal it's restarting in conhost and then it's immediately crash with error: there are no terminator "@>" in multiline comments. I can only assume that the problem is formatting, but I'm not sure.

In otherside there is no problem with &([ScriptBlock]::Create((irm asheroto.com/winget))) -Force -ForceClose command.

Video and photo examples. Is it the same for you?

System Details

Script verson 3.2.2
Windows 11 22H2
UAC disable
Powershell 5.1
Run as administrator

function getNewestLink($match){
$uri = "https://api.github.com/repos/microsoft/winget-cli/releases"
Write-Verbose "[$((Get-Date).TimeofDay)] Getting information from $uri"
$get = Invoke-RestMethod -uri $uri -Method Get -ErrorAction stop
Write-Verbose "[$((Get-Date).TimeofDay)] getting latest release"
$data = $get[0].assets | Where-Object name -Match $match
return $data.browser_download_url
}

$wingetUrl=getNewestLink("msixbundle")
$wingetLicenseUrl=getNewestLink("License1.xml")

What You Are Seeing?

Hello again. This time I had a problem during installation: "The modified resources are in use. Try closing Windows Terminal/PowerShell/Command Prompt and try again." This problem affects many other applications that interfere with installation: store, notepad, webexperience, and so on. These processes often hang in the background and have to be closed through the task manager. Restarting the PC does not always help.

I would like to suggest using the "-ForceApplicationShutdown" parameter with all Add-AppxPackage cmdlets to automatically shut down conflicting processes. More about this: https://learn.microsoft.com/en-us/powershell/module/appx/add-appxpackage?view=windowsserver2022-ps#-forceapplicationshutdown

What do you think about this?

System Details

Script verson 3.1.1
Windows 11 22H2
UAC disable
Powershell 5.1
Run as administrator

Checklist

• I have performed the steps in the Troubleshooting section and confirm that the issue only occurs with this script.

• I have restarted my computer to confirm this is not a transitory problem.

• I have verified that I am using the latest version of winget-install.

• I have verified that this issue is NOT security related (please create security advisory if so).

• I have run the script with the -DebugMode argument and included the output below

What You Are Seeing?

###############

Registering

###############

Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF3, Package failed updates, dependency or conflict validation.
Windows cannot install package Microsoft.DesktopAppInstaller_1.22.10582.0_x64__8wekyb3d8bbwe because this package depends on a framework that could not be found. Provide the framework
"Microsoft.UI.Xaml.2.8" published by "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version
8.2310.30001.0, along with this package to install. The frameworks with name "Microsoft.UI.Xaml.2.8" currently installed are: {}
NOTE: For additional information, look for [ActivityId] f6859c66-6b2d-0006-36da-85f62d6bda01 in the Event Log or use the command line Get-AppPackageLog -ActivityID
f6859c66-6b2d-0006-36da-85f62d6bda01
At C:\Program Files\WindowsPowerShell\Scripts\winget-install.ps1:829 char:13
+             Add-AppxPackage -RegisterByFamilyName -MainPackage Micros ...
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (Microsoft.Deskt...r_8wekyb3d8bbwe:String) [Add-AppxPackage], IOException
    + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageComman

System Details

Windows 10 Pro x64 22H2

Additional Context

Just started 2/27/24.

Full Output With -DebugMode

`Name Value

PSVersion 5.1.19041.3803
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.19041.3803
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Name : ConsoleHost
Version : 5.1.19041.3803
InstanceId : 6b9ff3ac-41c9-49c1-be6b-d61ef09a6d4a
UI : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture : en-US
CurrentUICulture : en-US
PrivateData : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled : True
IsRunspacePushed : False
Runspace : System.Management.Automation.Runspaces.LocalRunspace

winget-install 4.0.2
To check for updates, run winget-install -CheckForUpdate
VERBOSE: Perform operation 'Enumerate CimInstances' with following parameters, ''namespaceName' = root\cimv2,'className' = Win32_OperatingSystem'.
VERBOSE: Operation 'Enumerate CimInstances' complete.

#################

Prerequisites

#################

Downloading VCLibs...
VERBOSE: GET https://aka.ms/Microsoft.VCLibs.x64.14.00.Desktop.appx with 0-byte payload
VERBOSE: received 6764349-byte response of content type application/octet-stream
Downloading UI.Xaml...
VERBOSE: GET https://github.com/microsoft/microsoft-ui-xaml/releases/download/v2.7.3/Microsoft.UI.Xaml.2.7.x64.appx with 0-byte payload
VERBOSE: received 5070706-byte response of content type application/octet-stream

##########

winget

##########

VERBOSE: GET https://api.github.com/repos/microsoft/winget-cli/releases with 0-byte payload
VERBOSE: received 449422-byte response of content type application/json; charset=utf-8
Downloading winget license...
VERBOSE: GET https://github.com/microsoft/winget-cli/releases/download/v1.7.10582/5e4a105df01840b0bbf00985e4f57c1e_License1.xml with 0-byte payload
VERBOSE: received 2688-byte response of content type application/octet-stream
Downloading winget...
VERBOSE: GET https://aka.ms/getwinget with 0-byte payload
VERBOSE: received 258178004-byte response of content type application/octet-stream
Installing winget and its dependencies...
VERBOSE: Target Image Version 10.0.19045.3803

############

Complete

############

winget installed successfully.
Checking if winget is installed and working...

###############

Registering

###############

Add-AppxPackage : Deployment failed with HRESULT: 0x80073CF3, Package failed updates, dependency or conflict validation.
Windows cannot install package Microsoft.DesktopAppInstaller_1.22.10582.0_x64__8wekyb3d8bbwe because this package depends on a framework that could not be found. Provide the framework
"Microsoft.UI.Xaml.2.8" published by "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US", with neutral or x64 processor architecture and minimum version
8.2310.30001.0, along with this package to install. The frameworks with name "Microsoft.UI.Xaml.2.8" currently installed are: {}
NOTE: For additional information, look for [ActivityId] f6859c66-6b2d-0006-07de-85f62d6bda01 in the Event Log or use the command line Get-AppPackageLog -ActivityID
f6859c66-6b2d-0006-07de-85f62d6bda01
At C:\Program Files\WindowsPowerShell\Scripts\winget-install.ps1:829 char:13

•         Add-AppxPackage -RegisterByFamilyName -MainPackage Micros ...
  

•         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : WriteError: (Microsoft.Deskt...r_8wekyb3d8bbwe:String) [Add-AppxPackage], IOException
  • FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

VERBOSE: Operation completed for: Microsoft.DesktopAppInstaller_8wekyb3d8bbwe
winget command registered successfully.`

What You Are Seeing?

Hello, it's me again! :)
After running the script on a freshly installed system I get this result:

Even after installation via a script winget is still not initialized in the system. The problem can be solved by restarting the PC, but there is another way to solve this. Microsoft suggests using this command: Add-AppxPackage -RegisterByFamilyName -MainPackage Microsoft.DesktopAppInstaller_8wekyb3d8bbwe

After this the winget is ready for work instantly. So what do you think about this?

System Details

Script verson 3.0.1
Windows 22H2
UAC disable
Powershell 5.1
Run as administrator

Would be nice to add some code to get if WinGet is installed - and if so is it the latest version.

If WinGet is installed, and it's the latest version, just write it and exit.
If not installed or not latest version install/update.

What You Are Seeing?

Another day - another bug :)

If i set default terminal application as windows terminal and run windows powershell (x86) so Get-CurrentProcessModuleName function will stop working because MainModule and Modules fields are empty. Is it the same for you?

I think function must check several properties at once, but not only MainModule.

Windows PowerShell
(C) Корпорация Майкрософт (Microsoft Corporation). Все права защищены.

Установите последнюю версию PowerShell для новых функций и улучшения! https://aka.ms/PSWindows

PS C:\Users\uffemcev> function Get-CurrentProcessModuleName {
>>     <#
>>         .SYNOPSIS
>>             Gets the module name of the current PowerShell process.
>>
>>         .DESCRIPTION
>>             This function retrieves the window title of the current PowerShell host, finds the corresponding process, and returns the name of the main module of that process without the file extension.
>>
>>         .EXAMPLE
>>             $processName = Get-CurrentProcessModuleName
>>             This example shows how to use the function to get the module name of the current process and store it in a variable.
>>
>>         .NOTES
>>             This function assumes that the window title is unique to the current PowerShell session. If multiple windows have the same title, the function may not behave as expected.
>>     #>
>>
>>     $windowTitle = $host.ui.RawUI.WindowTitle
>>     $currentProcess = Get-Process | Where-Object { $_.MainWindowTitle -eq $windowTitle }
>>     $moduleNameWithExtension = $currentProcess.MainModule.ModuleName
>>     $moduleNameWithoutExtension = [System.IO.Path]::GetFileNameWithoutExtension($moduleNameWithExtension)
>>     return $moduleNameWithoutExtension
>> }
PS C:\Users\uffemcev> Get-CurrentProcessModuleName

PS C:\Users\uffemcev> $windowTitle = $host.ui.RawUI.WindowTitle
PS C:\Users\uffemcev> $currentProcess = Get-Process | Where-Object { $_.MainWindowTitle -eq $windowTitle }
PS C:\Users\uffemcev> $currentProcess

Handles  NPM(K)    PM(K)      WS(K)     CPU(s)     Id  SI ProcessName
-------  ------    -----      -----     ------     --  -- -----------
    809      43    92712      82484       0,08  11388   1 WindowsTerminal


PS C:\Users\uffemcev> $currentProcess | format-list *


Name                       : WindowsTerminal
Id                         : 11388
PriorityClass              : Normal
FileVersion                :
HandleCount                : 809
WorkingSet                 : 84463616
PagedMemorySize            : 94937088
PrivateMemorySize          : 94937088
VirtualMemorySize          : -1
TotalProcessorTime         : 00:00:00.0937500
SI                         : 1
Handles                    : 809
VM                         : 4294967295
WS                         : 84463616
PM                         : 94937088
NPM                        : 44152
Path                       :
Company                    :
CPU                        : 0,09375
ProductVersion             :
Description                :
Product                    :
__NounName                 : Process
BasePriority               : 8
ExitCode                   :
HasExited                  : False
ExitTime                   :
Handle                     : 3440
SafeHandle                 : Microsoft.Win32.SafeHandles.SafeProcessHandle
MachineName                : .
MainWindowHandle           : 1574456
MainWindowTitle            : Администратор: Windows PowerShell (x86)
MainModule                 :
MaxWorkingSet              : 1413120
MinWorkingSet              : 204800
Modules                    :

System Details

Script verson 3.2.2
Windows 11 22H2
UAC disable
Powershell 5.1
Run as administrator

I tried this on Server 2019 and all the steps completed successfully, but winget is not recognized as a command. I believe Winget should be located at "C:\Program Files\WindowsApps" but that folder does not exist. Winget isn't officially supported for Server OSes, but there are workarounds and just want to confirm your script will accommodate the workarounds for servers.