darkoperator / darkoperator/Posh-SSH
New-SFTPSession : Could not load file or assembly 'Renci.SshNet, Version=2024.0.0.0, Culture=neutral, PublicKeyToken=1cee9f8bde3db106' or one of its dependencies. The system cannot find the file specified.
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1.1k
- Forks
- 222
- PR merge metrics
- No merged PRs in 30d
Description
It appears the latest PoSH-SSH is still looking for the 2024 version of the Renci.SshNET assembly. On my Azure Server 2025, the latest Renci.SshNet assembly is already version 2025.0.0.1, can PoSH-SSH be udpated to use this version?
New-SFTPSession : Could not load file or assembly 'Renci.SshNet, Version=2024.0.0.0,
Culture=neutral, PublicKeyToken=1cee9f8bde3db106' or one of its dependencies. The system
cannot find the file specified.
FullName Location
Renci.SshNet, Version=2025.0.0.1, Culture=neutral, PublicKeyToken=1cee9f8bde3db106 C:\Program Files\WindowsPowerShell\Modules\posh-ssh\3.2.6\Assembly\Renci.SshNet.dll
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating how Posh-SSH loads the assembly at C:\Program Files\WindowsPowerShell\Modules\posh-ssh\3.2.6\Assembly\Renci.SshNet.dll and compare that behavior with the reported 2025.0.0.1 assembly. Verify New-SFTPSession on Azure Server 2025, and consider the issue done when the module loads the available assembly without the reported version error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100