Windows PowerShell Home
PowerShell 3.0 does not run on Windows Vista, only Windows 7
as Won't Fix
9/22/2011 12:04:08 AM
User(s) can reproduce this bug
Since when did Microsoft support only the latest released OS? Previously it supported OSes two generations older but at least one release behind must be supported? Windows 7 is the latest release, therefore PowerShell 3.0 and WinRM 3.0 must be supported on Windows Vista which is a current product and in full mainstream support.
How often does this happen?
Have you seen this problem before in this product?
No, this is new to the most recent version
PowerShell 3.0 CTP refuses to install on Windows Vista
PowerShell 3.0 must be supported on at least Vista SP2 and above.
to post a comment.
Please enter a comment.
on 3/1/2012 at 10:45 PM
The PowerShell 3.0 Beta supports Windows Server 2008 (R1) which shares its codebase with Vista. But it refuses to install on Vista, which leads me to believe that this is a stupid business decision to make Vista customers upgrade to Windows 7. They lose credibility but get a little more sales. Vista is in MAINSTREAM support till April. I see no reason why Windows Server 2008 SP2 (not R2 but original release) is supported by PowerShell 3.0 but not Windows Vista SP2.
on 2/16/2012 at 11:50 PM
Then will Microsoft please clarify the final list of supported operating systems for PowerShell 3.0?
on 1/25/2012 at 5:52 PM
There is a misconception here based on the release of a CTP dictating what will be supported when the final release comes. This is what happened with PowerShell v2: There was a CTP that only supported the latest OS (Vista and Server 2008), a few months before the final release date was set, there was a CTP for all currently supported OSs (XP, Vista, Server 2003 and Server 2008), then when the final release was out (v2 with Windows 7/Server 2008 R2), a short time after, a final release was out for the currently supported OS.
on 10/21/2011 at 8:48 PM
@Mark E. Schill, we don't know when Windows 8 or PowerShell 3.0 is going to be released. It may be in or before April 2012. I think as long as Windows 7 is the latest release version, one release earlier should be supported. There is no technical reason either why Windows Management Framework shouldn't be able to run on Vista SP2.
on 10/5/2011 at 8:53 AM
@Thomas Lee, or maybe the community can give strong feedback to the team so they will listen. The more feedback you give, the higher the chances of them supporting Windows 7 as well as Vista.
on 9/26/2011 at 2:17 AM
I think this is one of those things that the community is just going to have to accept. I can't see msft going back on this.
on 9/23/2011 at 2:30 AM
Our entire IT infrastructure is currently XP-based, with PowerShell 2.0 deployed everywhere and more and more used for admin stuff as a replacement for other scripting means (dare I say: CMD batch files?)
Not having 3.0 available for XP will hinder this transition to "everything in PowerShell).
Unless we can be very careful to write 3.0 code that's 2.0-compatible.
on 9/22/2011 at 8:20 PM
That's still more than 6 months from now. Please note that not everyone has deployed Windows 7 yet. I think Microsoft is ignoring Windows Vista customers just because it has a low usage share.
Mark E. Schill
on 9/22/2011 at 2:16 PM
According to Microsoft @ http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=Windows+Vista&Filter=FilterNO Windows Vista mainstream support will end on 04/12/2012 so by the time that PowerShell 3.0 is released Windows Vista actually won't be supported.
to post a workaround.
Please enter a workaround.
© 2013 Microsoft