Slashdot Mirror

← Back to Stories (view on slashdot.org)

Microsoft Replaces Command Prompt with PowerShell in Latest Windows 10 Build (softpedia.com)

Posted by msmash on from the replacing-things dept.

Bogdan Popa, writing for Softpedia:The latest Windows 10 insider build brings a change that puts the Windows PowerShell in the spotlight, as it replaces the super-popular Command Prompt in some essential parts of the operating system. 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.

6 of 280 comments (clear)

  1. Don't forget... by Pseudonymous+Powers · · Score: 4, Informative

    Every time you open a command prompt, don't forget you have to enter "set-executionpolicy unrestricted" before you can actually run anything.

    Usable!

    1. Re:Don't forget... by Anonymous Coward · · Score: 3, Informative

      or you set it globally, once, and you're done with it

    2. Re:Don't forget... by FreelanceWizard · · Score: 4, Informative

      Open Powershell as administrator and type:

      set-executionpolicy unrestricted -scope localmachine -force

      Alternatively, set it through Group Policy (Policies\Administrative Templates\Windows Components\Windows Powershell\Turn on Script Execution, set to "Allow all scripts").

      --
      The Freelance Wizard
    3. Re:Don't forget... by Anonymous Coward · · Score: 3, Informative

      Betty Sue (BS), will call the help desk and they will tell her to open Settings, go to Personalization, TaskBar, and turn the Powershell replaces CMD option off. Problem solved. Or does nobody realize that the option is right there in settings? I turned it off right away. If I want to start powershell I will. Normally I just want CMD.

  2. Re:I still don't want it by DrXym · · Score: 4, Informative
    You can't issue dos/cmd commands. The likes of "dir" are aliases onto things in powershell which superficially resemble the old commands but function differently.

    For example I can type "dir", but "dir /?" doesn't do a thing. So maybe the syntax is a bit different. Typing "dir -help" or "dir --help" issues an enormous error message that apparently I've done something wrong. Not helpful. Typing "help dir", tells me about something called "get-childitem" but essentially doesn't help at all except tell me to type "get-help Get-ChildItem -detailed". Eventually I get a wall of text which STILL doesn't correspond to the old syntax.

    Would it have really killed Microsoft to make "dir" function like "dir"? Maybe later on when I'm comfortable and familiar with the powershell I might want call get-childitem for something. But it is FAR more important to me during transition that the thing is familiar and all the various .bat / .cmd scripts that I have actually survive the transition.

    I should add that the command "ls" also aliases to "get-childitem". So Microsoft are equal-opportunity confounders.

  3. Re:It's hard to get over 25 years of habit by Anonymous Coward · · Score: 3, Informative

    Then just type in 'cmd' and you are set. They aren't removing the application.

    ...SNIP...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.

    From TFS...