Powershell : Could not load file or assembly winscp.dll

AeroX wrote:

If the .NET DLL is in the same directory as your PowerShell script you can load it using the below method instead of registering the assembly.

$ScriptPath = $(Split-Path -Parent $MyInvocation.MyCommand.Definition)
[Reflection.Assembly]::LoadFrom( $(Join-Path $ScriptPath "WinSCPnet.dll") ) | Out-Null

martin wrote:

Thanks you for sharing the details. I have documented this on:
https://winscp.net/eng/docs/message_net_operation_not_supported

But anyway, I was able to register even a blocked assembly on Windows 8. What version of Windows are you using?

Johan Nieuwhoff wrote:

martin wrote:

Thanks you for sharing the details. I have documented this on:
https://winscp.net/eng/docs/message_net_operation_not_supported

But anyway, I was able to register even a blocked assembly on Windows 8. What version of Windows are you using?

That's because Windows 8 is loaded with powershell 3.0. I found out that powershell 1.0 is not able to handle it. It also might be something with .Net 4.5 (which is required for powershell 3.0).
So, make sure u are using the latest powershell

[Reflection.Assembly]::LoadFrom("C:\Program Files (x86)\WinSCP\WinSCP.dll") | Out-Null

[Reflection.Assembly]::LoadFrom("C:\Program Files (x86)\WinSCP\WinSCPnet.dll") | Out-Null

Add-Type -Path "C:\Program Files (x86)\WinSCP\WinSCPnet.dll"

namerg wrote:

1. When i load winSCP.dll and execute a powershell script i get the following error as a windows pop up: Incompatible external console protocol version 5.

2. When i load the WinSCPnet.dll and execute a powershell script i get the following message error in the command prompt: Could not load file or assembly 'file:///C:\Program Files (x86)\WinSCP\WinSCPnet.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515).

perry99 wrote:

For some reason powershell thinks, the DLL is remote, even if it is on a local drive, and I didn't find a way to "unblock" the specific file.

GreenLion wrote:

hi guys,

i ran into the same prolbem and solved it with another approach.

mainly i found out that with VS 2013 (Powershell extension from codeplex) is not very near to the native Powershell enviroment.
so i had to load the assembly differently foreach enviroment.

i handled it like so:

$setDevEnviromentVS = $true
#Load WinSCP assembly according DEV Enviroment
   if($setDevEnviromentVS)
   {
      [System.Reflection.Assembly]::LoadFrom('.\_components\winscp572\WinSCPnet.dll')
   }
   else
   {
      dd-Type -Path '\\<UNC>Apps\winscp572\WinSCPnet.dll'
   }

so with this code - you can run the script either from VS or from ISE.

HTH

Anonymous wrote:

I was trying to execute from network drive and kept on getting this error.
I none of the above solution did not work for me, although from your coding, I just changed it to
[System.Reflection.Assembly]::UnsafeLoadFrom('.\_components\winscp572\WinSCPnet.dll')

This UnsafeLoadFrom did the trick for me.
below is the copy from MSDN.

If an application has been copied from the web, it is flagged by Windows as being a web application, even if it resides on the local computer. You can change that designation by changing the file properties, or you can use the <loadFromRemoteSources> element to grant the assembly full trust. As an alternative, you can use the UnsafeLoadFrom method to load a local assembly that the operating system has flagged as having been loaded from the web.

martin wrote:

This is covered here:
https://winscp.net/eng/docs/message_net_operation_not_supported