New
#1
PowerShell vs CommandPrompt
All of a sudden I could not start PS app... so, I switched to CmdPrmpt. That got me thinking: (1) do I need both? (2) Should I even bother fixing PS?
PowerShell vs CommandPrompt
-
-
New #2
Hi, depends if you use it.
My understanding is that Powershell 2 is provided with Windows, so repairing it might involve removing it as a feature restarting and reinstating it (tick box):
or an in-place upgrade repair install - tutorial if needed - keeps all progs and data.
However, there's also Powershell 7 which installs separately:
How to Install PowerShell 7.1 in Windows 7, Windows 8, and Windows 10
(see post #4 e.g.)
-
New #3
What's the diff?
Both of them are factory installed in new devices with Windows OS, as far as I can remember way back to Vista. They both have easy usage, use same command language, always on Administrator format and have blackened window. Recently, I started wondering if CP works as well because it seldom finds integrity violation and never corrects fully. PS seems to have higher yield of finding violations and always corrects them fully, Odd, just as I started to be partial to PS, it stopped starting. Now there is another PS that needs to be installed separately? Is that also from Microsoft?
-
New #4
They offer similar and different functionality. Personally I would want powershell working, but I'm a systems engineer for a living and I work with Windows and I use powershell.
-
New #5
Well, apparently Windows is kind of phasing out Command prompt. I did not notice this prompt until now.
That means I have to fix PS. How do I proceed?
-
-
New #7
ain't broken
Turned out, my PS is not broken. PS app is, so I deleted it. Now, I start PS from START button, right-clicked. Should I uninstall CP?
-
New #8
No, why would you try to uninstall the command prompt. It's a core windows component, leave it alone.
-
Quote
Related Discussions
