I've inherited a Server-2008 SharePoint-2010 Dev environment, the SharePoint Snapin fails to load; warning ...

Add-PSSnapin : Incorrect Windows PowerShell version 3.0. Windows PowerShell 
version 2.0 is supported in the current console.

I followed all the documented remedies:

  • uninstall WMF 3.0 and KB2506146
  • execute PowerShell.exe with the "-version 2.0" parameter
  • remove the reference to .Net 4.0 from the PowerShell config

The SnapIn fails to load and still the same warning "Incorrect Windows PowerShell version..." So I confirm the version. It looks good...

PS C:\Users\Administrator> $PSVersionTable.PSVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
2      0      -1     -1

So I checked the SnapIn...

PS C:\Users\Administrator> Get-PSSnapIn -Registered

Name        : Microsoft.SharePoint.PowerShell
PSVersion   : 3.0
Description : Register all administration Cmdlets for Microsoft SharePoint Server

The PSVersion is 3.0??? The PSVersion for the SnapIn reads 1.0 on all other machines. And doesn't run in 3.0 because of the 4.0 .Net framework. How can I change this back? So that it targets the compatible version of PowerShell? Thanks for any help you can offer.

  • 1
    seems like somebody tried to "update" the server to SP2013, probably by manually moving some files. Check in gac for the aforementioned dll and review it version. That may give some clue. – SPArcheon May 5 '14 at 8:04
  • The DLL looks to be the correction version... C:\windows\assembly\gac_msil\Microsoft.SharePoint.PowerShell\ – SP Combatant May 5 '14 at 13:36
  • Where did the answer went? Did I saw a ghost? Wasn't this question answered? I recall you solved the problem by reinstalling the dll to gac - was I mistaken? Do you still need help? Will have a look at this then. – SPArcheon May 5 '14 at 14:42
  • ...forgot to mention - the "date modified" of Microsoft.SharePoint.PowerShell in the GAC is the same as all the other SP 2010 components, so i don't think anything has monkeyed with the library. What's left? The registry? – SP Combatant May 5 '14 at 17:29
  • Did you install SharePoint designer 2013? – eirikb Jun 19 '14 at 7:33

The registry determines the level of PS compatibility, in my case the value was 3.0, it should be 1.0. I corrected this value by editing the following key:


The initial cause of the problem was the installation of the Windows Management Framework 3.0 which installs with it PowerShell. Even after uninstalling, the registry remained incorrect and I had to edit the registry with the information above.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.