PowerShell isn't Vista-ready, either

Summary:Microsoft's newly released PowerShell command-line shell and scripting language doesn't currently work with Windows Vista.

As a few other bloggers noted yesterday, Microsoft’s newly released PowerShell command-line shell and scripting language doesn’t currently work with Windows Vista.

According to the download site, PowerShell works with Windows XP Service Pack 2 and Windows Server 2003 SP1. The folks over at Bink.nu note that PowerShell is working with Vista Release Candidate 1. But the PowerShell version that will run on the gold version of Vista version is still “at least a few more weeks” away, the bloggers said.

Some corporate users who have been eagerly anticipating PowerShell are not happy.

“It took them five years to finish the product (Vista),” one tester, who requested anonymity, said to me today. “It’s not like they didn’t know it was coming.”

And before anyone says the final version of Vista isn’t available yet, it now is. Microsoft has made the Vista Business and Enterprise versions available to its volume licensees. The bits are not yet on MSDN, however.

Update: Courtesy of Jeffrey "PowerShell" Snover himself: "We've had many questions about when Windows PowerShell will be released for Windows Vista. We plan to release Windows PowerShell 1.0 by January 31st, 2007."


Topics: Windows


Mary Jo Foley has covered the tech industry for 30 years for a variety of publications, including ZDNet, eWeek and Baseline. She is the author of Microsoft 2.0: How Microsoft plans to stay relevant in the post-Gates era (John Wiley & Sons, 2008). She also is the cohost of the "Windows Weekly" podcast on the TWiT network. Got a tip? Se... Full Bio

Contact Disclosure

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Related Stories

The best of ZDNet, delivered

You have been successfully signed up. To sign up for more newsletters or to manage your account, visit the Newsletter Subscription Center.
Subscription failed.