cmd vs Powershell  

77 members have voted

  1. 1. Which would you like to see in Windows 8?

    • Powershell default, cmd alternative
    • cmd default, Powershell alternative (Currently in Windows 7)
    • Powershell default, no cmd at all
    • cmd default, no Powershell at all


Recommended Posts

  On 30/10/2011 at 22:15, n4cer said:

cmd can't be removed as it would break existing scripts and applications that call cmd.

Though PowerShell has aliases for many cmd built-in commands, the cmdlets for which the aliases are mapped do not support the switches of the cmd commands (e.g., you can't do "dir /w" in PowerShell). Variable syntax is also different (e.g., %windir% in cmd vs $env:windir in PowerShell).

PowerShell is getting ever increasing usage as the underpinning for Windows administration and troubleshooting functionality. While it should see greater exposure, such as adding it to the Ribbon and the context menu ("Open PowerShell here"), cmd should not be removed to elevate PowerShell unless the use cases for cmd are covered by PowerShell. It's not like cmd is the only shell besides PowerShell that currently ships with Windows. Its presence doesn't diminish PowerShell.

Nor is it meant to.

Add-on command shells have existed for NT-based flavors of Windows from the beginning (two of the more well-known were the Hamilton C Shell, a straight-up port of the Bourne Again Shell (bash) to NT, and 4NT (and 4NT alternative TakeCommand) from JP Software) - PowerShell isn't meant to take away from that. (Bash certainly hasn't taken away the usefulness of other shells anywhere else - including Linux distributions, MacOS, or even UNIX, where bash began.) The reason, in fact, for the popularity of bash as a shell is the fact that the same commands are usable regardless of the underlying OS. PowerShell, unlike bash, is designed expressly for Windows - it's far from OS-neutral. Most of the documentation for PowerShell is on the *server* side of Windows (that is despite the reality that PowerShell is usable by Windows 7 today) - generally, unless you have a niche usage that PowerShell fits, you likely won't be running PowerShell on Windows 7 (though you certainly can).

  On 30/10/2011 at 20:42, Taranaich said:

So install Bash. You can do that.

Cmd maybe, but don't think you've actually tried PowerShell or you wouldn't be saying that. It's quite powerful. Bash is good yes,but looking over what Bash has built in, nothing really jumps out as being something that others can't do or just doesn't apply.. most of it's goodies come from external programs or scripting languages, most of which are available to other shells.

True. The very attraction of bash is that it is OS-neutral - it works the same regardless of the underlying operating system. (Have we forgotten one of the very first NT CMD alternatives, the Hamilton C Shell? It was, in fact, a direct port of bash (which stands for the Bourne Again Shell, which itself was a fork of ash) to NT 3.1/9x. The Hamilton C Shell was one of my favorite *jaw-dropper* programs during the Windows 95 beta, because it was an NT program that ran *untouched/unaltered* on 9x.) Most CMD alternatives (including PowerShell) are designed to fill in niches.

  On 30/10/2011 at 17:38, htcz said:

Why invoke cmd just to ping an asset?

And the link you posted to........is that really a reason to use cmd over Powershell? :rolleyes: come on....

Let me ask you a question. You made a poll here, right? Then you ask everyone's opinion, when someone gives it you just come with all your love for Powershell. I know the differences between CMD and Powershell and that's why I posted my goddamn opinion.

I don't think really think people understand what powershell is. In some ways its more powerful then bash and other ways its more awkward. But I do think it really is getting better/ more powerful with each version. In Windows 8 server powershell knowledge looks like it almost most know.

Windows needs a more powerful default command interpreter. Powershell is worlds ahead of the stock "cmd", and seems to effectively rival things like BASH in *nix by allowing complex scripting and greater access to system resources.

The old school cmd needs to go away, especially since Powershell can run all the normal commands anyway.

  On 30/10/2011 at 19:51, Aethec said:

It seems many people here don't understand what CMD is.

Short explanation: CMD is a console window that provides basic functionality for changing the current directory (cd), showing the files and folders (dir) and a few other things (copy, auto-completion, command history...). The most important thing it does is to enable you to open files, give arguments to executables, and provide input and output for console applications.

What you're doing by calling "robocopy C:\SomeFolder C:\SomeOtherFolder" is launching robocopy.exe using "C:\SomeFolder" and "C:\SomeOtherFolder" as parameters. "tree C:\" just calls tree.com with "C:\" as a parameter. "ping google.com" calls ping.exe with "google.com" as parameter. And so on.

These programs (not commands - check your C:\Windows\System32 folder) can be used exactly the same way in PowerShell, and their output will look exactly the same.

In fact, if Microsoft set the default background color to black in PowerShell and removed the "PS" at the beginning of each line, most people wouldn't notice the difference. You would still be able to use the programs you use now.

Great post :)

  On 30/10/2011 at 20:01, Joey S said:

cmd and Powershell are like kids toys by comparison

cmd of course but Powershell.........Powershell and bash can compete pretty good with each other :)

  On 30/10/2011 at 20:42, Taranaich said:

Cmd maybe, but don't think you've actually tried PowerShell or you wouldn't be saying that. It's quite powerful. Bash is good yes,but looking over what Bash has built in, nothing really jumps out as being something that others can't do or just doesn't apply.. most of it's goodies come from external programs or scripting languages, most of which are available to other shells.

Another good post.

Lets not make this a bash vs Powershell thread :p

  On 30/10/2011 at 20:53, ThePitt said:

wtf is powershell?

I already posted this: http://en.wikipedia.org/wiki/Windows_PowerShell

  On 30/10/2011 at 21:20, pupdawg21 said:

Powershell is NOT a replacement for CMD and ALL commands do not work in the same manner or using the same syntax in the 2 environments. Many of the most commonly used ones do however.

As Aethec said, from CMD you are actually calling other programs. (stated in %PATH) so in a sense you can use all the commands in CMD in Powershell as well. There might be some conflicts with Powershell commands but thats why I stated that if a program calls cmd then executes a command, Powershell should start up in a cmd compatibility mode.

  On 30/10/2011 at 22:15, n4cer said:

cmd can't be removed as it would break existing scripts and applications that call cmd.

Though PowerShell has aliases for many cmd built-in commands, the cmdlets for which the aliases are mapped do not support the switches of the cmd commands (e.g., you can't do "dir /w" in PowerShell). Variable syntax is also different (e.g., %windir% in cmd vs $env:windir in PowerShell).

I already commented on this :) If a program calls cmd then executes a command, Powershell should start up in a cmd compatibility mode. This way it is backwards compatible.

  On 30/10/2011 at 22:15, n4cer said:

PowerShell is getting ever increasing usage as the underpinning for Windows administration and troubleshooting functionality. While it should see greater exposure, such as adding it to the Ribbon and the context menu ("Open PowerShell here"), cmd should not be removed to elevate PowerShell unless the use cases for cmd are covered by PowerShell. It's not like cmd is the only shell besides PowerShell that currently ships with Windows. Its presence doesn't diminish PowerShell.

That would be the only thing neccesary

  On 31/10/2011 at 00:28, bruNo_ said:

Let me ask you a question. You made a poll here, right? Then you ask everyone's opinion, when someone gives it you just come with all your love for Powershell. I know the differences between CMD and Powershell and that's why I posted my goddamn opinion.

Obviously since you have no argument, you simply state it is your opinion. While I do find your opinion valid, there is no base to it therfore I can not agree with it.

  On 31/10/2011 at 09:55, DonC said:

I'd use powershell by default if it:

1. Started up as quickly as cmd

2. Had a convenient and reliable phrase in the start menu. PowerPoint gets in the way!

1. It will get better :)

2. Put "powers" and it is the first thing to come up. Come on, another lame excuse.

  On 31/10/2011 at 00:39, Melfster said:

I don't think really think people understand what powershell is. In some ways its more powerful then bash and other ways its more awkward. But I do think it really is getting better/ more powerful with each version. In Windows 8 server powershell knowledge looks like it almost most know.

That's because PowerShell is not as well documented as the CMD interpreter - which makes sense, as CMD goes all the way back to the beginning of Windows NT itself.

PowerShell was designed as an alternative shell (similar to bash/bsh/ash/csh) for housekeeping/scripted commands primarily for the *server* side of Windows (specifically, Server 2003) - while it (like all the NT-based shell alternatives, from Microsoft and everyone else) is also usable on the desktop (XP and later, in the case of PowerShell), the documentation on the desktop side of things is rather sparse, compared to the server side of PowerShell's documentation.

(BSH is the original Bourne Shell, and has basically been superseded by bash.)

  On 31/10/2011 at 05:44, osuwildlifer said:

if you do it that way, the cmd window disappears as soon as the pings finish.

You ping, you see the response on the screen, and then the screen goes away. I can see special case scenarios where you may want the command window to persist, but for just finding out if a resource is reachable, what is the issue?

  On 05/11/2011 at 19:51, surrealvortex said:

You ping, you see the response on the screen, and then the screen goes away. I can see special case scenarios where you may want the command window to persist, but for just finding out if a resource is reachable, what is the issue?

The issue on all systems I've ever done that on is that the cmd window disappears too quickly to read the results. Is that not the case in your situation??

  On 05/11/2011 at 23:29, osuwildlifer said:

The issue on all systems I've ever done that on is that the cmd window disappears too quickly to read the results. Is that not the case in your situation??

ping address -t

;) Ping won't stop until you use Ctrl+C

Dunno about the people saying PS takes longer to load. It loads just as quick as CMD on my system at work. I'm constantly between the two, honestly. I think because I've been using CMD so long, that its just out of natural habit.

  On 05/11/2011 at 23:58, osuwildlifer said:

Ha! Well, you didn't specify that ;-) And the person who posted that method as a suggestion didn't either.

You can run any command from the search bar using either CMD or PS:

cmd /k ping google.com
powershell -noexit -command ping google.com

It opens a new CMD window and executes the command, but doesn't close afterwards.

Fun thing to do: Launch powershell.exe from CMD, or cmd.exe from PowerShell.

  On 07/11/2011 at 17:02, Aethec said:

You can run any command from the search bar using either CMD or PS:

cmd /k ping google.com
powershell -noexit -command ping google.com

It opens a new CMD window and executes the command, but doesn't close afterwards.

I can see in PATH being stored a variable that if you call CMD or command it executes powershell -noexit -command %s in Windows 8/

  On 08/11/2011 at 10:39, osuwildlifer said:

^ nice! Didn't know you could do that. (Y)

What he posted or calling cmd from Powershell and Powershell from cmd?

  • 11 months later...
  On 24/10/2012 at 23:12, Nicole Hamilton said:

Thank you for remembering my Hamilton C shell.

But a correction, if I may: Hamilton C shell is not a port of anything. I wrote every line from scratch myself for this product and first released it in December 1988, about 7 months before Brian Fox released his bash shell. It's much, much faster than bash on Windows for several reasons. First, I have a better compiler front end; it's faster at parsing statements and generating an optimized internal representation. Second, it's still the only multi-threaded Unix-style shell in existence. Third, it's written explicitly for Windows. It goes straight to the underlying Win32 API for everything. I don't even use the C runtime anywhere performance counts. I definitely don't use a big slow DLL like Cygwin uses to try to map Unix system calls onto Windows.

Also, news for those who might have been interested but were concerned about cost: For personal use, it's now just $89 and that covers all your personal devices. There's also a fully functional free demo version.

I would wager that the big reason that folks liked Cygwin was due to the backing of it by RedHat, Inc. (RHI).

However, you're right, Cygwin is huge and horribly unwieldy.

The Hamilton C Shell and other command shells, such as 4NT and TakeCommand, (and PowerShell, of course) are far from unwieldy.

I first read about the Hamilton C Shell back in the early days of NT, and I was referring specifically to your NT port of the Shell.

  On 27/10/2012 at 17:50, reaper1576 said:

I'm to used to DOS but I do need to learn how to use PowerShell. Anyone got any good links to stuff for learning PowerShell?

There are several Microsoft Press books on using PowerShell - the biggest criticism I have for *all* of them is that they are designed for server admins. (There is not a single PowerShell book for desktop admins, or even desktop usage - despite PowerShell itself having been included with desktop Windows since XP Service Pack 3, and addable to desktop Windows since XP Service Pack 2. What little I know about using PowerShell - which is very little - comes from Windows Server 2008R2/2012.)

For that matter, I'd like to be able to add a separate PowerShell prompt (ala Server 2012) to the QuickTask power users' menu, instead of having to right-click on a contextual menu in Explorer.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Shouldn't using "High Performance" mode prevent c-states from initializing? Maybe AMD hasn't built a proper power plan for their x3d processors like they used to for their ryzen chips.
    • Vivetool also has a GUI. Literally took me three clicks to enable this from there.
    • Microsoft Weekly: OneDrive horror stories, ramblings about Start menu, and more by Taras Buria This week's news recap is here, delivering you a roundup of the most important Microsoft stories, including a bunch of odd stuff and bugs in Windows, OneDrive horror stories, ramblings about the Start menu, a couple of new Windows 11 preview builds, important news from AMD, and a lot more. Quick links: Windows 10 and 11 Windows Insider Program Updates are available Reviews are in Gaming news Windows 11 and Windows 10 Here, we talk about everything happening around Microsoft's latest operating system in the Stable channel and preview builds: new features, removed features, controversies, bugs, interesting findings, and more. And, of course, you may find a word or two about older versions. Microsoft released a new out-of-band update to fix boot issues on certain Surface devices. The company announced certain Windows 365 updates, such as VBS and HVCI support (by default) and app provisioning in Windows 365 instead of entire cloud PCs. Microsoft is also removing legacy drivers from Windows Update in a new "strategic move." This is the default Windows 365 wallpaper On the negative side, we have the latest Patch Tuesday updates breaking the DHCP Server in all Windows Server editions. Also, there is some bad news for PC users with Windows Hello cameras: after the April 2025 Patch Tuesday updates, Windows Hello does not work in the dark. The change was quietly introduced to address security issues. Windows Goodbye That is not all, though. As it turned out, solid-state drives from WD could still block your computer from installing Windows 11 version 24H2, which was released in October 2024. Also, Microsoft's Family Safety feature is now blocking Chrome, for some reason. Here is an editorial from Usama Jawad (welcome back) about how, four years after the initial release, Windows 11 still does not offer strong enough reasons to upgrade from the outgoing Windows 10. Also, Usama shared his thoughts about the Start menu and why he had stopped caring about its changes altogether. Speaking of the Start menu, check out our overview of what users wanted from Microsoft and what the company delivered in the redesigned Start menu, which was recently announced. Windows Insider Program Here is what Microsoft released for Windows Insiders this week: Builds Canary Channel Build 27881 This week's Canary build introduced context menu improvements, new accessibility features, Settings app tweaks, and more. Dev Channel Nothing in the Dev Channel this week Beta Channel Nothing in the Beta Channel this week Release Preview Channel Build 26100.4482 (KB5060829) This build improves File Explorer and search performance, adds some changes to default browser settings, and fixes multiple bugs. Some hidden stuff in the recent Windows 11 preview builds includes a new adaptive battery saver. This feature dynamically adapts battery saver mode according to your workflow, but in its current form, it is not fully operational. Even though Microsoft acknowledged its existence, the adaptive part still needs improvements. Another useful change in the recent builds is the return of a clock in the notification center. This time, however, Microsoft makes it more customizable, and you can toggle it on or off. Also, the company is moving more Control Panel bits to the Settings app and adding a rather unexpected customization feature that will let you select where system indicators (flyouts and sliders) appear on the screen. Microsoft started rolling out a new update for the Snipping Tool app. The latest release lets you save screen recordings as GIFs. Shortly after that, we posted a guide with a bit more detail about the feature. Updates are available This section covers software, firmware, and other notable updates (released and coming soon) from Microsoft and third parties, delivering new features, security fixes, improvements, patches, and more. Microsoft is working on a Dashboard redesign for PowerToys. Developers published an early look at what is coming to the app in future updates, revealing a better-organized page with quick links, a shortcut overview, and a list of available modules. This week's Office updates are rather mixed. OneDrive, for one, is having problems finding files. Microsoft acknowledged the issue, which affects users on Windows, iOS, Android, and the web. Unfortunately, that is not the only negative story about OneDrive. A new report from a frustrated user revealed a scary tale of Microsoft locking them out of an account full of invaluable content. Outlook also has some issues, this time, with opening emails, and Microsoft 365 will soon disable outdated protocols for file access. Finally, Copilot in Excel received a major update for context awareness, which made the assistant more useful when answering questions about data. This week's browser updates include several releases. Firefox announced a new method for pinning and unpinning tabs. It is now available for testing in the Nightly channel. Microsoft Edge was updated with fixes for two security vulnerabilities (high severity) originating from Chromium. Finally, here is this week's Microsoft 365 Roadmap with an overview of all the new stuff that Microsoft added to the website. Here are other updates and releases you may find interesting: Microsoft 365 security in the spotlight after Washington Post hack. Microsoft expands European sovereign cloud offerings with new data and key controls. Microsoft Defender XDR received TITAN-powered Security Copilot recommendations. Microsoft reportedly plans more layoffs. Watchdog found Microsoft guilty of confusing advertising when it comes to Copilot. Here are the latest drivers and firmware updates released this week: AMD released a new chipset driver for Ryzen processors under version 7.06.02.123, which followed a security update for TPM-Pluton. Nvidia 576.80 WHQL with fixes for the RTX 5090 FE, new game support, and a long list of fixes. You can get some extra performance on certain AMD Ryzen chips with a simple system tweak. Surface Pro 11 and Surface Laptop 7 received big firmware updates with multiple fixes and improvements. Reviews are in Here is the hardware and software we reviewed this week This week, Steven Parker reviewed the TerraMaster D4 SSD, a palm-sized DAS with up to 32TB of storage that you can connect over USB4. This thing is rather impressive, and for a modest price tag, it delivers a tiny footprint, great looks, full RAID support in TOS 6, quick connection, and more. On the gaming side Learn about upcoming game releases, Xbox rumors, new hardware, software updates, freebies, deals, discounts, and more. AMD and Microsoft announced some big news this week. The two companies revealed a new multi-year partnership, which secures AMD as the future maker of chips for Xbox consoles and other hardware. Sarah Bond announced the partnership in a new video on the official Xbox media channels. Turn 10 Studios announced a new Forza Motorsport update. Update 21 brings IndyCar content, Career mode expansion, Featured Tours, new reward cars, and more. It is now available on Xbox and PC via the Microsoft Store and Steam. Minecraft is another Microsoft-owned game that received a big update this week. The long-anticipated graphics overhaul is finally here with directional lighting, volumetric fog, improved shadows, reflections, godrays, and a lot more. In addition, Mojang released Chase the Skies, the latest content drop, which adds happy ghasts, new music disks, a locator bar for players, environmental fog in the overworld, new background music, and all sorts of small gameplay changes. Microsoft announced new games for Game Pass. The latest additions include FBC: Firebreak, Crash Bandicoot 4: It's About Time, Start Trucker, Wildfrost, Rematch, Call of Duty: WWII, Rise of the Tomb Raider, and more. As usual, some games are leaving the subscription. Valve released a big update for the Steam overlay. The latest version introduced major upgrades to CPU and VRAM usage, temperatures, and other important metrics that you might want to track when playing games on your gaming rig. Deals and freebies Also, be sure to check out this week's Weekend PC Game Deals article, which features rhythm bundles, fishing festivals, DRM-free summer sales, and more. Other gaming news includes the following: Take-Two confirmed Borderlands 4 will not cost $80 for the base game. The Coalition expanded the Gears of War: Reloaded beta after its rocky start. Ara: History Untold 1.4 update delivered overhauls to AI, map generation, combat, and more. Star Citizen Alpha 4.2 update lands with radiation hazards, dynamic rain, and more. This link will take you to other issues of the Microsoft Weekly series. You can also support Neowin by registering a free member account or subscribing for extra member benefits, along with an ad-free tier option. Microsoft Weekly image background by steve_a_johnson on Pixabay
  • Recent Achievements

    • First Post
      Johnny Mrkvička earned a badge
      First Post
    • Week One Done
      viraltui earned a badge
      Week One Done
    • One Month Later
      serfegyed earned a badge
      One Month Later
    • Dedicated
      firey earned a badge
      Dedicated
    • Dedicated
      fettermanj earned a badge
      Dedicated
  • Popular Contributors

    1. 1
      +primortal
      634
    2. 2
      ATLien_0
      230
    3. 3
      Michael Scrip
      218
    4. 4
      Xenon
      149
    5. 5
      Steven P.
      140
  • Tell a friend

    Love Neowin? Tell a friend!