Windows 10: cmd vs powershell

Discus and support cmd vs powershell in Windows 10 Support to solve the problem; Greetings. As a normal PC-geek I don't know how, when and why I should use Powershell instead of cmd. Or in another way, why has Microsoft changed cmd... Discussion in 'Windows 10 Support' started by Burgurne, Jun 17, 2017.

  1. Burgurne Win User

    cmd vs powershell


    Greetings.
    As a normal PC-geek I don't know how, when and why I should use Powershell instead of cmd. Or in another way, why has Microsoft changed cmd to Powershell in the right-click menu? What are the benefits?

    Or has Microsoft just done this to make fun of us, that don't know all the commands to Powershell ?*Sad

    I have found (and used) Brinks good guide to make the cmd rearrive at the menu instead of Powershell, but what am I missing by not learning Powershell??? *Redface

    :)
     
    Burgurne, Jun 17, 2017
    #1
  2. Mike-77 Win User

    Can't run Powershell or cmd.exe as administrator

    I'm not really an expert on PowerShell or cmd. Sometimes I'll have a problem with the computer, and when I look around for ways to fix it, sometimes need to use cmd, sometimes PowerShell. There's a good explanation about the differences between PowerShell
    and cmd here.
     
    Mike-77, Jun 17, 2017
    #2
  3. Facing some issues in CMD and PowerShell

    To resolve your concern, you may perform System File Checker. To do so, check this

    link
    .

    Let us know the results.

    Regards.
     
    Realyn Mar, Jun 17, 2017
    #3
  4. cmd vs powershell

    MS just wants more people to use it, thus it has brought it to the foreground.
    I always remove it, since mostly only malware uses it, especially ransomware.
    Powershell is a great tool for system admins, since it allows to do more and faster.
     
    TairikuOkami, Jun 17, 2017
    #4
  5. vram Win User
    I find PS has this lag to it on startup. The Windows pops up almost immediately, but there is a delay as to when you can start typing anything. Witnessed it on multiple PCs. I hate it for that reason alone.
     
  6. Mystere Win User
    If you don't know why you would use powershell vs cmd, then you probably only need cmd. However, there may be times (especially if you're following a tutorial on here) where they will give you commands that are powershell commands.

    There are many subsystems in Windows that have Powershell interfaces for command scripting. So you have to issue commands from Powershell for these.

    As an aside, you can enter most cmd commands in powershell and they'll work just fine. For a lot of people you can use them interchangeably.
     
    Mystere, Jun 17, 2017
    #6
  7. johnpd Win User
    Powershell is tremendously more powerful and complex. It requires a steep learning curve especially if you are not familiar with an object oriented programming language. There are some things in CMD prompt that do not work in Powershell. If you are using fairly basic commands and batch files, CMD will do although it can do some fairly complicated stuff as well. The biggest problem I have found with Powershell is finding appropriate documentation for it although there are thousands of examples on the net to which you can refer.

    JohnD
     
    johnpd, Jun 18, 2017
    #7
  8. Bree New Member

    cmd vs powershell

    That includes the command CMD itself, which will run a command prompt within the PowerShell window. Type EXIT to get back to PowerShell when you're done...
     
  9. pparks1 Win User
    You can run the same commands in powershell as you can in cmd, but you can also run a ton more powershell commands.

    I think MS changed it because
    1). More people are using powershell
    2). MS is encouraging those who don't use PS, to start using it.
     
    pparks1, Jun 18, 2017
    #9
  10. Bree New Member
Thema:

cmd vs powershell

Loading...
  1. cmd vs powershell - Similar Threads - cmd powershell

  2. Most windows executable commands not recognized by CMD and PowerShell.

    in Windows 10 Gaming
    Most windows executable commands not recognized by CMD and PowerShell.: Out of nowhere commands which involve executables like explorer.exe, msedge.exe, mspaint.exe, where, etc. are not working in command prompt or PowerShell. The output of the command prompt seem to be quite simple: ```C:\Users\grass>where 'where' is not recognized as an...
  3. Most windows executable commands not recognized by CMD and PowerShell.

    in Windows 10 Software and Apps
    Most windows executable commands not recognized by CMD and PowerShell.: Out of nowhere commands which involve executables like explorer.exe, msedge.exe, mspaint.exe, where, etc. are not working in command prompt or PowerShell. The output of the command prompt seem to be quite simple: ```C:\Users\grass>where 'where' is not recognized as an...
  4. how to connect to Wi-Fi with cmd/powershell script

    in Windows 10 Gaming
    how to connect to Wi-Fi with cmd/powershell script: i'm trying to create command to connect to my Wi-Fi via automation script, however my Wi-Fi demand user name and password to connectWindows Security Login pop up when connecting to wireless NetworkI tried to Add a new wireless profile to the system: netsh wlan add profile...
  5. how to connect to Wi-Fi with cmd/powershell script

    in Windows 10 Software and Apps
    how to connect to Wi-Fi with cmd/powershell script: i'm trying to create command to connect to my Wi-Fi via automation script, however my Wi-Fi demand user name and password to connectWindows Security Login pop up when connecting to wireless NetworkI tried to Add a new wireless profile to the system: netsh wlan add profile...
  6. Can't run almost any commands in cmd/powershell

    in Windows 10 Gaming
    Can't run almost any commands in cmd/powershell: Basically, adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + adb + ~~~ + CategoryInfo :...
  7. Can't run almost any commands in cmd/powershell

    in Windows 10 Software and Apps
    Can't run almost any commands in cmd/powershell: Basically, adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + adb + ~~~ + CategoryInfo :...
  8. Fix Process exited with code 1 error in Windows Terminal, PowerShell or CMD

    in Windows 10 News
    Fix Process exited with code 1 error in Windows Terminal, PowerShell or CMD: [ATTACH]While running a command in Windows Terminal, Command Prompt or PowerShell, if you get Process exited with code 1 error message, you can follow these suggestions to get it resolved. Process exited with code 1 error in Windows Terminal, PowerShell or CMD To fix Process...
  9. CMD and PowerShell Closing after a couple of seconds

    in Windows 10 Network and Sharing
    CMD and PowerShell Closing after a couple of seconds: My pc is fine i didnt download any viruses, Didnt mess with system files nor modify it. After a normal restart, A message that pops up for half a second saying "This app wont work on this computer" Or something like that The messages appears and disappears too fast its hard...
  10. CMD and PowerShell Closing after a couple of seconds

    in Windows 10 Software and Apps
    CMD and PowerShell Closing after a couple of seconds: My pc is fine i didnt download any viruses, Didnt mess with system files nor modify it. After a normal restart, A message that pops up for half a second saying "This app wont work on this computer" Or something like that The messages appears and disappears too fast its hard...