winget installing program in new windows | PowerShell | Page 1

hollow herald Jan 10, 2023, 4:07 PM

#

Trying to install some packages with winget inside a script but for some reason it just opens a new powershell window for each winget command which it doesnt if i just type it out myself
issue being it continues on with the rest of the script but like 2 seconds after that there is a restart command so it cant finish

try{
    winget install "7zip.7zip" --source "winget" --silent --accept-package-agreements --accept-source-agreements
    winget install "Foxit PDF Reader" --source "msstore" --silent --accept-package-agreements --accept-source-agreements
    winget install "Google.Chrome" --source "winget" --silent --accept-package-agreements --accept-source-agreements
    winget install "Oracle.JavaRuntimeEnvironment" --source "winget" --silent --accept-package-agreements --accept-source-agreements
}
#installeert via ninite als winget faalt
catch {
    Invoke-WebRequest -Uri "https://ninite.com/7zip-adoptjavax8-chrome-foxit/ninite.exe" -OutFile "H:\Temp\Ninite.exe"
    Start-Process "H:\Temp\Ninite.exe" -Wait
}

echo badger Jan 10, 2023, 10:52 PM

#

win get is not likely to throw an exception, so try will likely never get hit
You can capture the output like this

$stdout = &  winget install  x --source y ......

you get a verbose log as a text file, that you can parse when using this option https://learn.microsoft.com/en-us/windows/package-manager/winget/troubleshooting

Debugging and troubleshooting issues with the winget tool

Provides information on logging and winget diagnostics.

hollow herald Jan 16, 2023, 11:06 AM

#

echo badger win get is not likely to throw an exception, so try will likely never get hit Yo...

it does when its not installed
which ive found to be the issue of it opening in new windows as well
right before this it has install-module WingetTools but it doesnt do that hence it seems to use some older version that executes it in new windows

echo badger Jan 17, 2023, 2:22 AM

#

hollow herald it does when its not installed which ive found to be the issue of it opening in ...

it just opens a new powershell window for each winget command which it doesnt if i just type it out myself
if you want to mimic typing winget --help then use either

& winget @('--help')
# or
start-process 'winget' -NoNewWindow -ArgumentList @('--help')

You're erroring is that winget isn't installed?
Here's how I'd handle it. when winget isn't installed, it exits on the very first line $binWget =

Or you could use -ea continue|ignore then throw your own exception.

function Invoke-WinGet {
    [CmdletBinding()]
    <#
    .synopsis
        call winget, when not installed: exits early throwing an error
    #>
    param(
       [object[]]$ArgsList
    )
    # If someone writes an alias or function named winget, normally it can
    # cause your code to call the function
    # I used 'Application' because that means a native command, like .exe or .cmd
    # filtering out any aliases or functions with the same name.
    $binWget = Get-Command -Name 'winget' -CommandType Application -ea stop
    'Invoking: winget {0}' -f @(
       $ArgsList -join ' '
    ) | Write-verbose

    & $binWget @ArgsList
}

Invoke-WinGet -Verbose -ArgsList @('--help')
# or
start 'winget' -ArgumentList @('list', '--help') -NoNewWindow

#

right before this it has install-module WingetTools
using $x = command causes it to wait for command to finish
start-process exits immediately unless you use -wait

#

and use -NoNewWindow otherwise they likely won't install in order, or in the same session

#winget installing program in new windows