I reported here back on November 28, 2016, that MS swapped the command line prompt for PowerShell. This affects the Start and File Explorer context menus in Insider Preview build 14971. This change continues in recent builds as well. However, there are well-documented fixes to restore cmd.exe throughout the OS. But recently certain sources suggest that cmd.exe is doomed. That’s untrue, says Microsoft Senior Program Manager Rich Turner in an MS Developer blog post. Published January 4, it’s entitled “Rumors of Cmd’s death have been greatly exaggerated.” Thus “CMD.exe NOT going away in Win10” is a fair and truthful claim. This tagline from the blog post says it more emphatically:
How’s this for emphasis?
Why Say “CMD.exe NOT Going Away in Win10?”
To explain his emphatic rejection, Turner offers the following points (reproduced verbatim from his blog post):
- Much of the automated system that builds and tests Windows itself is a collection of many Cmd scripts that have been
created over many years, without which we couldn’t build Windows itself!
- Cmd is one of the most frequently run executables on Windows with a similar number of daily launches as File Explorer,
Edge and Internet Explorer!
- Many of our customers and partners are totally dependent on Cmd, and all it’s quirks, for their companies’ existence!
I hope this clarification renders this tempest in a teapot moot. Anyway, it’s hard to assert that CMD.exe is on its way out, in the face of the preceding claims. And FWIW, my own testing confirms that what works at the command line in Windows 10 (mostly) works completely unaltered inside PowerShell equally well. So please: let’s drop this issue and tackle another controversy instead! For example, I’m ready for a frank and candid discussion about the huge number of reports of freezing and instability in Window 10’s Current Branch release. What about you?