Linked by Thom Holwerda on Fri 18th Nov 2016 15:56 UTC

Command Prompt has been around for as long as we can remember, but starting with Windows 10 build 14971, Microsoft is trying to make PowerShell the main command shell in the operating system.

As a result, PowerShell officially replaces the Command Prompt in the Win + X menu, so when you right-click the Start menu, you’ll only be allowed to launch the more powerful app. Additionally, in File Explorer’s File menu and in the context menu that appears when pressing Shift + right-click in any folder, the old Command Prompt will no longer be available.

Typing cmd in the run dialog will launch PowerShell as well, so Microsoft has made a significant step towards phasing out the traditional Command Prompt.

It's funny - cmd has always been seen as a sort-of Baby's First Command Line, and compared to the shell that comes standard with any UNIX-based operating system, that was certainly true. However, now that Windows has a replacement that is much more capable than cmd, people will cry foul and hell over the possible deprecation of cmd.

Us nerds are fickle.

Thread beginning with comment 637308
To read all comments associated with this story, please click here.
Comment by Luminair
by Luminair on Fri 18th Nov 2016 23:14 UTC
Member since:

lost me at forwarding cmd.exe to powershell. the last thing linux and unix are about is removing your ability to use an old ubiquitous program

Reply Score: 5

RE: Comment by Luminair
by malxau on Sat 19th Nov 2016 01:54 in reply to "Comment by Luminair"
malxau Member since:

lost me at forwarding cmd.exe to powershell...

Heh, I'm itching to see what happens in the reverse direction, where PowerShell has to hand complex scripts back to cmd.exe because it has no chance of executing them itself. That core cmd code can't possibly go away.

Reply Parent Score: 2

RE: Comment by Luminair
by Hayoo! on Sat 19th Nov 2016 02:00 in reply to "Comment by Luminair"
Hayoo! Member since:

Windows is not a UNIX-like OS, so what's with the comparison with Linux and UNIX?

Reply Parent Score: 1

RE[2]: Comment by Luminair
by shotsman on Sat 19th Nov 2016 16:51 in reply to "RE: Comment by Luminair"
shotsman Member since:

The comparison is because MS has seen fit to allow a Linux shell to be used with their precious operating system.
All part of their new love affair with Linux. How long this will last I really have no idea.

Reply Parent Score: 2

RE: Comment by Luminair
by avgalen on Mon 21st Nov 2016 11:42 in reply to "Comment by Luminair"
avgalen Member since:

lost me at forwarding cmd.exe to powershell.

This is clearly something that shouldn't happen. cmd means cmd.exe and not powershell.exe. Clearly some manager gave the order "Replace everything related to commandprompt with powershell by default" and this got included.

Replacing it in the Win+X menu and Shift-Rightclick has been an option for a couple of years now and I can understand why they want to switch PowerShell to the default. I am going to have to change it back to cmd.exe until I figure out how to give "real" cmd commands to PowerShell though (like dir/a/s/b/on *20161121*.log)

Reply Parent Score: 2