I just downloaded the latest PowerShell 6.2.0 Preview 3 and its just like CMD, so what is the real difference and what the advantage of it? I assume the one I downloaded is newer than the one in Windows 10 1607.
Some cmd functions got removed and only works with PS. When i compiled 1607 LTSB with NTLite i checked remove PS thinking cmd is still viable, months later "aw crap" was my respond to that mistake. Edit: I remember bit was also for security reasons. I don't remember exactly but was something about PS scripts is easier to exploit and execute than cmd bat. Not that i have solid information but i think PS security should be more steady these days.
Unless you're someone like me who already knows CMD and powershell offers nothing that I need. If I had a career in programming, sure powershell would be good to know. But why write a script in powershell if you can do the same with CMD and it'll run faster? So it really needs to be decided on a case by case basis. Not only is powershell much more powerful, it's much more slower.
Definitely, but I just can't seem to motivate on that. Good old cmd has been around since the mountains, hard to give up what you're used to.
Powershell lets you use wild cards easily in some instances such as this Code: powershell -command "get-childitem -path C:\windows\winsxs -include *defender* -recurse | remove-item -recurse -force -confirm:$false"
There are far too may differences to post here, but in short the major difference is PowerShell is built on .NET and thus can take any Windows task and add automation and logic to it. This is eons beyond what cmd (command-line) can do. PowerShell offers complete automation, data manipulation, full administrative control of Exchange, Active Directory, Citrix, etc. locally and across networks, code-wrapping, namespace and kernal access and control, etc. PowerShell is heavily driven on internal error handling which can negligibly affect processing speed. Moreover, each time PowerShell is loaded, it automatically loads all cmdlets and modules into the active session. The list goes on.
According to the most recent white-papers on malware attacks, over 60% occurred by running the PowerShell script/commands from cmd, not from a PowerShell shell.
I personally like and use tccle from JPSoft. I have been using their command shell since the days of 4dos. My day job is supporting technical applications under unix, but I am doing more support these days of Windows applications, so I have been learning Powershell. It is indeed a very powerful tool, and in some ways a more useful scripting language under Windows than even Perl. I attempted to switch over and use powershell instead of tccle, but I ran into too many road blocks. YMMV
I agree!!! TCC/LE is absolutely amazing, it deserves a lot more attention, I always thought Microsoft should have hired Rex Conn years and years and years ago!! Nice to see another TCC/LE fan here...