Skip to main content
Question

Remoting into Veeam 13.1 server with Configuration "PowerShell.7" are unable to import the module Veeam.Backup.PowerShell

  • October 9, 2026
  • 1 comment
  • 9 views

We remote into the Veeam server to do our choirs, but since we upgraded to 13.1 we have a problem. We can’t use PowerShell 5 since because of the requirements of Veeam. Remoting into the Veeam server using a PowerShell.7 configuration fails with “ParentContainsErrorRecordException: Exception calling "ImportByDll" with "1" argument(s): "Dependency resolution failed for component C:\Program
Files\Veeam\Backup and Replication\Console\Veeam.Backup.PowerShell.dll with error code -2147450750. Detailed error:
Hostpolicy must be initialized and corehost_main must have been called before calling
corehost_resolve_component_dependencies. “

If I do a $psversiontable in the session it says PSVersion=7.6.3

What I do:
Enter-PSSession -computername veamserver -ConfigurationName “PowerShell.7” -Credential $mycred
import-module Veeam.Backup.PowerShell

    1 comment

    Forum|alt.badge.img+3
    • ddomask
    • Veeam Product Management
    • October 9, 2026

    HI ​@agregersen

    Regrettably, this is a limitation from Microsoft with PSRemoting (over WinRM) & PowerShell 7.

    The relevant PowerShell issue was reported already in 2019 to Microsoft and was closed without a resolution:

    https://github.com/PowerShell/PowerShell/issues/11238 

    Unfortunately, unless Microsoft changes how .NET hosting works within WinRM—which appears unlikely—we cannot continue to support WinRM and PSSession as a transport for pwsh remoting. The available alternatives are to switch PSRemoting to SSH transport or to avoid PSRemoting entirely and use the pwsh module directly from the client connecting to the remote VBR.

    Can you describe your workflow a bit more and if it’s feasible to use our native Connect-VBRServer cmdlet instead of doing PSRemoting?

    0x0D 0x0A
      Terms & ConditionsAccessibility statement