Command Prompt not retiring. It will remain for decades

Starting with Windows 10 Insider Preview Build 14971, PowerShell replaces Command Prompt in the Win + X menu, and in the File menu of File Explorer. As Microsoft puts it in their blog post:

It (PowerShell) replaces Command Prompt (aka, “cmd.exe”) in the WIN + X menu, in File Explorer’s File menu, and in the context menu that appears when you shift-right-click the whitespace in File Explorer. Typing “cmd” (or “powershell”) in File Explorer’s address bar will remain a quick way to launch the command shell at that location.

For those who prefer to use Command Prompt, you can opt out of the WIN + X change by opening Settings > Personalization > Taskbar, and turning “Replace Command Prompt with Windows PowerShell in the menu when I right-click the Start button or press Windows key+X” to “Off”.

Further, from Build 14986, the folder context menu option “Open command window here” is hidden. Instead, “Open PowerShell window here” entry appears by default.

Replacing Control Panel with Settings in the Win + X menu is one of the other changes in the Insider Preview builds. Microsoft has already ported many of the Control Panel features into the Settings app, and eventually the classic Control Panel will be removed.

These changes led to a speculation that the classic Command Prompt is going to be retired (or already has been), and replaced by PowerShell. That’s how some magazines reported.

But, the truth is Command Prompt is going to be there for decades — until there’s almost nobody running Command scripts or tools.

command prompt not retiring

Rich Turner, a Sr. Program Manager at Microsoft has rejected the speculation through his blog post and tweets.

Also, read Rumors of Cmd’s death have been greatly exaggerated – Windows Command Line Tools For Developers by Rich Turner [MSFT]

About the author

Ramesh Srinivasan founded Winhelponline.com back in 2005. He is passionate about Microsoft technologies and has a vast experience in the ITeS industry — delivering support for Microsoft's consumer products. He has been a Microsoft MVP [2003 to 2012] who contributes to various Windows support forums.

2 thoughts on “Command Prompt not retiring. It will remain for decades

  1. [Version]
    Signature=$CHICAGO$

    [DefaultInstall]
    AddReg=Reg.Settings
    AddReg=Reg.Uninstall
    CopyFiles=Inf.Copy

    [DefaultUninstall]
    DelReg=Reg.Settings
    DelReg=Reg.Uninstall
    DelFiles=Inf.Copy

    [Reg.Settings]
    HKCR,Folder\Shell\Cmdhere
    HKCR,Folder\Shell\Cmdhere,,,”%MENUITEM%”
    HKCR,Folder\Shell\Cmdhere\command,,,”%11%\cmd.exe /k pushd %L”

    [Reg.Uninstall]
    HKLM,Software\Microsoft\Windows\CurrentVersion\Uninstall\%NAME%
    HKLM,Software\Microsoft\Windows\CurrentVersion\Uninstall\%NAME%,DisplayName,,”%NAME%”
    HKLM,Software\Microsoft\Windows\CurrentVersion\Uninstall\%NAME%,UninstallString,,”Rundll32.exe setupapi.dll,InstallHinfSection DefaultUninstall 132 %17%\Cmdhere.inf”

    [Inf.Copy]
    Cmdhere.inf

    [DestinationDirs]
    Inf.Copy=17

    [SourceDisksNames]
    55=%DISKNAME%

    [SourceDisksFiles]
    Cmdhere.inf=55

    [Strings]
    NAME = “Cmdhere”
    MENUITEM = “CMD &HERE”
    DISKNAME = “Setup Files”

    Here are the lines of the INF file Cmdhere.inf.
    Simply right click and choose “Install”.
    You can customize it in your own language, E.G. in ITALIAN, by rewriting the string MENUITEM:

    [Strings]
    NAME = “Cmdhere”
    MENUITEM = “PROMPT &dei COMANDI”
    DISKNAME = “Setup Files”

    I found this little INF file in internet a long time ago and it is still working nowadays.
    Thanks to his author, wich name I don’t remember anymore.

Leave a Comment