[Bug]: current setup will not work inside winrm. about winget-install

[asheroto]

Hello,

any attempt to use winget via winrm will be unable to actually update source lists & unable to accept any source agreement.

Can you please provide a few examples/commands or screenshots?

Without the logs I'm not sure at what point the script fails. The script your provided is essentially what this script does at some point, it's similar but not quite the exact same.

Can you please try to get the script output? You can call the script and get the script output by doing this...

&([ScriptBlock]::Create((irm asheroto.com/winget))) -Force -DebugMode *> C:\winget-install.log

which will save the log to c:\winget-install.log in text format.

Or if you have the script locally you can just append *> c:\winget-install.log (space before the *) and it will output to that location as well.

[ITJamie]

Sorry just to clarify. The install script works and installs, however winget is currently not possible to run via winrm when it's installed in the standard layout. So while the install works its just not usable from winrm

The link above shows an alternate method of install that puts all of the winget requirements into a single directory which then allows winget to run and install packages from winrm.

So my request is to have a flag in the winget install script to install winget in the alternative fashion of having all the requirements in one folder and update the windows path.

[asheroto]

Ah I see. I'm trying to figure out what the difference is in the script. Maybe I can just add a line or two.

It looks like it operates the same as the script in the link you mentioned, but it does not do this...

cmd /c setx /M PATH "%PATH%;$ENV:PROGRAMFILES\WinGet"

Can you check on your winrm instance and see if winget is installed to that folder and this command corrects the issue after running this script?

I'm thinking maybe it's the setx because that changes the path.