PowerShell 3.0 and SharePoint 2010 - by Tobias Burger

Status : 

  External<br /><br />
		This item may be valid but belongs to an external system out of the direct control of this product team.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 746908 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 6/6/2012 2:15:24 AM
Access Restriction Public


After installing the Management Framework RC on a SharePoint 2010 Server I can't use the "SharePoint 2010 Management Shell" anymore.

SharePoint uses .NET 3.5 and PS 3.0 uses .NET 4 and if I try to access the SP Object Model i get a an error, that Microsoft SharePoint is not supported by Version 4.0.30319.17626.
That's totally comprehensible, but I wonder what the future plans about product compatibilty between PS 3.0 and SP (vNext?) are?
Sign in to post a comment.
Posted by MarcDiller on 8/6/2013 at 6:23 AM
Any update? Does Sharepoint 2010 SP2 work with Powershell v3?
Posted by boled on 2/21/2013 at 9:13 AM
So what is the point of powershell 3.0 then if months later it isn't compatible with Sharepoint? I've seen loads of blurb about the increaced functionality of 3.0 but I've seen nothing about its incompatibility. What is it for?
Posted by johnlouros on 10/26/2012 at 12:49 PM
The workaround if quite simple. Just type

powershell -v 2

it loads PowerShell version 2, and from there you can mess with SharePoint. Just type


to get back to PowerShell 3
Posted by Andrew Wolfe on 9/25/2012 at 7:50 AM
You need to put some sort of huge comment on the WMF 3 download page to warn of this. Better still have the update installer detect and warn that there are SharePoint components on the Server. Simply not blaming the SharePoint team and saying it's down to them is very short sighted
Posted by fyreblazer on 6/13/2012 at 8:29 AM
Is there a workaround? Maybe point PS to .net 2.0?
Posted by Dan [MSFT] on 6/7/2012 at 12:34 PM
This is not an issue with Windows PowerShell. This is an issue with SharePoint 2010. The SharePoint team is aware of this compatibility issue and plans to address it in an upcoming release or service pack.