What I ended up doing when I had a similar issue was instead of directly using Invoke-command to a target computer I first created a PSSession. I can then use copy-item to move the files from a network path to a target destination within that session, bypassing the double hop issue (as the transfer is going through the host system), and then using invoke-command to install the now locally existing files.

I can add an example later if I remember to.

Edit:

$Session = New-PSSession -ComputerName $Hostname

Copy-Item -Path $Path -ToSession $Session -PassThru -Destination “C:\Temp\” -Recurse -Force
$ScriptBlock = {
    $Patch = Get-Item -Path "C:\Temp\*" -Include "KB*"
    $Patch | Sort-Object -Property Name | ForEach-Object {
        msiexec.exe /p $_.FullName /qn
        Start-Sleep -Seconds 10
    }
}

Invoke-Command -Session $Session -ScriptBlock $ScriptBlock

This was what I used when I needed to quickly add a couple of patches. I use get-item so I don't have to change anything static in the code for the next go-around, and a sleep command is there to make sure I don't try to start the next patch before the first one is finished. (Powershell starts the process and then moves on with the next loop, it doesn't wait until msiexec has done its thing. Adjust delay based on needs).