PowerShell script exchange
Post Reply
Product Manager
Posts: 19068
Liked: 1943 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

No snap-ins have been registered for Windows PowerShell

Post by veremin » 3 people like this post


While adding Veeam Backup and Replication snap-in, PowerShell returns the following error:

“No snap-ins have been registered for Windows PowerShell version”


The issue is typically caused by presence of two PowerShell instances (32-bit and 64-bit ones) inside 64-bit operating systems and is related to one of the following situations:
  • • Snap-in has been incorrectly registered (or has not been registered at all) for the improper PS instance either automatically or by user via instautil
    • User tries to add 64-bit snap-in from 32-bit PowerShell instance
    • 64-bit PowerShell shortcut is wrongly pointed to SysWOW64
    • Usage of Windows 2008 (R2) with default Powershell 2.0 (there are a lot of weird issues related to it)
    • etc.

Several possible approaches are suggested:
  • • Opening VB&R snap-in via icon in VB&R GUI, Menu -> PowerShell (as described here)
    • Manually registering snap-in
    • Checking corresponding registry hive and manually re-creating missing entities (as described here)
    • Updating default Powershell 2.0 in case of Windows Server 2008 (R2)
    • Reinstalling the latest Update, along with PS snap-in
    • Reinstalling everything from scratch (mostly applicable for those who are on free product version, as there is no historical data, configurable infrastructure, etc. ; might be a tough call for those who are on paid product versions)
More information

If neither of the suggested solutions does the trick for you or you have further questions, open a support case, as follows:

Posts: 11
Liked: never
Joined: Apr 23, 2019 3:43 pm
Full Name: David Lee

Re: No snap-ins have been registered for Windows PowerShell

Post by eeldivad »

I notice we don't need to register the snapin for newer versions of Powershell. I'm using Powershell 5. This might work for older versions too. I simply copy all files/subfolders of c:\Program Files\Veeam\Backup and Replication\Console
to another server anywhere you like. Then use import-module directly with Veeam.Backup.PowerShell.dll

import-module D:\scripts\Powershell\modules\Veeam\Veeam.Backup.PowerShell.dll

Now if you run get-module, you will see Veeam.Backup.Powershell listed

To get the list of commands available just run
get-command -module Veeam.Backup.Powershell

I haven't tested all the functions but they seem to work fine for me

Posts: 75
Liked: 10 times
Joined: Nov 11, 2016 8:56 am
Full Name: Oliver

Re: No snap-ins have been registered for Windows PowerShell

Post by oliverL »

Merry Christmas! :-)

I've been checking differet ISO Images but i can't find the Setup-File for the Powershell Module, atleast in the Backup Folder there is no BPS-File.

Where can i get a download link? Or is it possible to extract the Snapin from the Powershell Module?

I wanna create a Dokumentation Function so that i can create a report about the current Veeam Server with its Job etc. pp.

Veeam Software
Posts: 1279
Liked: 430 times
Joined: Sep 25, 2019 10:32 am
Full Name: Oleg Feoktistov

Re: No snap-ins have been registered for Windows PowerShell

Post by oleg.feoktistov »

Hi Oliver and Merry Christmas!

Starting from v9 Veeam PS Snap-in is integrated in VBR installation package.
So, with the current version, if you want to create your custom function out of Veeam powershell cmdlets, you would need a server with VBR instance running.
Anyway, internet abounds with various Veeam reports. I'm sure you can find the one fitting your goal. :wink:


Veeam Software
Posts: 471
Liked: 265 times
Joined: Jun 24, 2019 1:39 pm
Full Name: Chris Arceneaux
Location: Kentucky, USA

Re: No snap-ins have been registered for Windows PowerShell

Post by chris.arceneaux »

Adding to what Oleg mentioned, you can also install the Veeam PS Snap-in on a different server by installing the Veeam Backup & Replication Console. The screenshot below was taken from our PowerShell documentation.


Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests