About a year ago, [WayBack] Rumors of Cmd’s death have been greatly exaggerated – Windows Command Line Tools For Developers got published as a response to confusing posts like these:
- [WayBack] Say goodbye to the MS-DOS command prompt | Computerworld
- [WayBack] Follow-up: MS-DOS lives on after all | Computerworld
But I still think it’s a wise idea to switch away from the Cmd and to PowerShell as with PowerShell you get way more consistent language features, far better documentation, truckloads of new features (of which I like the object pipeline and .NET interoperability most) and far fewer quirks.
It’s time as well, as by now, Windows 7 has been EOL for a while, and Windows 8.x is in extended support: [WayBack] Windows lifecycle fact sheet – Windows Help:
Client operating systems Latest update or service pack End of mainstream support End of extended support Windows XP Service Pack 3 April 14, 2009 April 8, 2014 Windows Vista Service Pack 2 April 10, 2012 April 11, 2017 Windows 7* Service Pack 1 January 13, 2015 January 14, 2020 Windows 8 Windows 8.1 January 9, 2018 January 10, 2023 Windows 10, released in July 2015** N/A October 13, 2020 October 14, 2025
Which means the PowerShell version baseline on supported Windows versions is at least 4.0: [Archive.is] windows 10 powershell version – Google Search and [WayBack] PowerShell versions and their Windows version – 4sysops
PowerShell and Windows versions ^
PowerShell Version Release Date Default Windows Versions PowerShell 2.0 October 2009 Windows 7 Windows Server 2008 R2 (**) PowerShell 3.0 September 2012 Windows 8 Windows Server 2012 PowerShell 4.0 October 2013 Windows 8.1 Windows Server 2012 R2 PowerShell 5.0 April 2014 (***) Windows 10
So try PowerShell now. You won’t regret it.
–jeroen
via: [WayBack] Very interesting clear-up post and comments on CMD, command.com, PowerShell in past and future DOS/Windows versions and Unix shells altogether. – Ilya S – Google+