The Powershell command

I read that the Powershell command is more powerful than the ordinary command prompt and I have been looking at various net sites including the official Microsoft web site but am unable to understand a lot of what the results are telling me. I have on occasion had to use the sfc /scannow and or DISM RestoreHealth command to fix my machines so is PowerShell better than the straight command prompt method?.
So I am open to any information on just what I can run in PowerShell that would be better than the ordinary command prompt as I have seen the forum queries mentioning using PowerShell to fix stuff.
Any help would be really helpful

John,

PowerShell makes no difference to running those commands or any other specific commands that can be used in both [PS, Cmd]. It is the commands that matter.

PowerShell is capable of running very sophisticated commands & command scripts that have no equivalent in the command prompt.
It is a well-structured command shell instead of being an unstructured hotch-potch of independent commands that started out decades ago and got modified without any central technical policy in control.
my ditty Batch file and PowerShell guides [post #7] - ElevenForum


All the best,
Denis

Try3 said:

PowerShell makes no difference to running those commands or any other specific commands that can be used in both [PS, Cmd]. It is the commands that matter.

Click to expand...

Ok Denis I have a better idea of it now I just wanted to make sure that what I have been using - the command prompt wasn't lacking when using the DISM commands. Thanks for your explanation

ICIT2LOL said:

... I am not intelligent to use scripting ...

Click to expand...

Balderdash.

You might find these explanations of equivalents useful. Rather than study it, you might want to just keep a note of it for use in an emergency.
List of PowerShell equivalents and alternatives to Cmd commands - WindowsClub
You have to concentrate on not being distracted by the adverts whenever you read any of their webpages.


All the best,
Denis

Ok Denis I will check out the link you have sent mate but all the same it sort of goes over my head a bit. I did do a little coding back in the Commodore64 days and it took me hours to figure out even simple functions of the computer that is why I said I am not clever enough to do things in the PowerShell mode.

Hey ICIT2LOL!

You might want to check out this on GitHub:


I have been using (sparingly) and updating from GitHub for a while now.
Works as intended.

​

John,

I'm quite sure that you do not want to check that thing on GitHub.


All the best,
Denis

Try3 said:

John,

I'm quite sure that you do not want to check that thing on GitHub.


All the best,
Denis

Click to expand...

An explanation my be helpful right?

Try3 said:

'm quite sure that you do not want to check that thing on GitHub.

Click to expand...

Well Denis I had a look but mate it did not make much sense to me with the coding and stuff like that.

ICIT2LOL,
I too got a Commodore 64, back somewhere around 1980, and found people using it for business, but not very successfully. I started writing business programs for Inventory, AR, AP, and payroll. But the little C-64 was just so dang slow! It just wasn't very good at number crunching.
It was a little bit better after I re-wrote the Kernel ROM, to eliminate all the Tape Commands and Safe Defaults.
Commodore Basic was fairly simple, but when I upgraded to the IBM PC, I learned DOS Batch Language, and started writing DOS color menus, and batch files. I never did learn IBM Basic, MS Basic or any other basic of the day.

There are several things I've wanted to do with my 'puter, that I just can't do in 'DOS Batch', but I've found a few 'Coders' that can do it in Powershell. And I greatly want to thank them for their help!

A command that I can actually run in a Batch file, to empty the Recycle Bin, for instance.

PowerShell Clear-RecycleBin -force -ErrorAction:Ignore

But, I've found out, that I do not want to try to run a DOS Batch command in 'Powershell'.

My own "Cleanup.bat" program wouldn't be what it is today, without the help I've gotten from guys on this Forum.
Thanks Y'all!
TM

I wonder why inbuilt Windows' Powershell can not be upgraded instead of using two versions

Both command prompt cmd.exe and powershell have access to all of the binaries on your computer. Beyond that they are very different. cmd is text based with limited logic and variables while powershell is object oriented and can easily leverage the dotNET framework for even more functionality.

MiguelAngel11 said:

I wonder why inbuilt Windows' Powershell can not be upgraded instead of using two versions

Click to expand...

To your question Windows Powershell is built on the dotNET framework which is Windows only and hence so is Windows Powershell (ending at 5.2). Microsoft Powershell 6.x and beyond is based on dotNET core which is a open sourced and cross platform (Win, Nix and Mac). It's basically a rewrite of the whole thing

TechnoMage2021 said:

My own "Cleanup.bat" program wouldn't be what it is today, without the help I've gotten from guys on this Forum.

Click to expand...

Ok Techno I am impressed and yes the Commodore was extremely slow and I only got to getting it to draw circles and the like and that is why I have not taken up the cudgel to try and write stuff it is now out of my league.

At the same time, as I was getting acquainted with the C-64, I was designing and building computers, in the research labs for CAT.
Every day was a new challenge and I loved it. I did all I could to make the lowly little C-64 and it's companion the C-1541 disk drive the very best they could be. That launched me into a very busy computer business.
I've always been about trying to get the very best out of everything I owned, whether a car, motorcycle or computer.
Although I did a lot of programming on the C-64, I did not carry that over to the IBM PC. Other than a few batch files, that is.

TechnoMage2021 said:

I've always been about trying to get the very best out of everything I owned, whether a car, motorcycle or computer.
Although I did a lot of programming on the C-64, I did not carry that over to the IBM PC. Other than a few batch files, that is.

Click to expand...

Am really impressed TechnoMage sounds like you are a bit of a fix all stuff where possible like myself.

neemobeer said:

Both command prompt cmd.exe and powershell have access to all of the binaries on your computer. Beyond that they are very different. cmd is text based with limited logic and variables while powershell is object oriented and can easily leverage the dotNET framework for even more functionality.


To your question Windows Powershell is built on the dotNET framework which is Windows only and hence so is Windows Powershell (ending at 5.2). Microsoft Powershell 6.x and beyond is based on dotNET core which is a open sourced and cross platform (Win, Nix and Mac). It's basically a rewrite of the whole thing

Click to expand...

Thanks for your answer. Noew it makes sense to me