PowerShell instead of Commandline in Creators Update

[RejZoR]

Ok, can someone tell me the point of PowerShell replacing old CMD in right click Start menu? I wouldn't mind it if god damn syntaxes weren't totally different than in CMD.

Tried to flash my GTX 980 the other day, open the thing as admin, like before and blue window shows up. So I said, ok, they changed the color. Tried to execute the utility and it refused. Then I looked well and I see it's not CMD but PoweShell. And now I have no clue how to use the damn thing. Luckily I could dig up old CMD from Search, but it's dumb, because CMD is now digged somewhere and PowerShell is where CMD used to be.

How do you frigging use this damn thing?

 

[Solaris17]

welllllllll powershell can use 99% of cmd.

otherwise you dont really need to "dig up" cmd in search since its pretty simple to type CMD.

if you are seriously that bothered you could have probably googled for 20seconds and found out you can change it just like before.

right click on task bar click "taskbar settings" toggle this setting.

 

[Kursah]

PowerShell can process many CLI commands but does have its own syntax as you are finding.

I use it a lot at a management level for carious workstation and sever tasks. Pretty much anything Windows does in the GUI is a powershell command.

I recommend you look up some info on Google and also look into the book, Learn PowerShell in 30-days Worth of Lunches. That'll give you a great start to properly using and understanding PowerShell. Its extremely powerful and useful...the caveat is learning it and understanding what it wants.

You should be able to set it back to CLI in personalization settings if you don't want to learn it. CLI is still food enough for most folks...not sure why they felt the need to do that...ironically I have my menus set to display PowerShell instead of CLI.

http://m.windowsitpro.com/windows-10/pro-tip-replace-command-prompt-powershell-windows-x-menu

 

[RejZoR]

I just needed CLI (CMD) for stuff that has no interface, like flashing tools. And now I have to learn some new shit for no reason because someone thought shoving PowerShell there by default would make sense. Aaaah, I guess I'll just stick a CMD shortcut into Start menu (which is already crowded but oh well).

 

[Frick]

I just needed CLI (CMD) for stuff that has no interface, like flashing tools. And now I have to learn some new shit for no reason because someone thought shoving PowerShell there by default would make sense. Aaaah, I guess I'll just stick a CMD shortcut into Start menu (which is already crowded but oh well).

Or you do as Solaris say and change the option for it.

Or you do as normal, god-fearing people do and assign it a shortcut, like ctrl+alt+x or something. Or you do as even more normal people do, hit Win, type cmd, ctrl+shift enter.

 

[RejZoR]

Missed the part about replacement. I've now done so. Thx

 

[Frick]

Missed the part about replacement. I've now done so. Thx

Still, when I discovered keyboard shortcuts my life changed. I can't live without ctrl+alt+a opening a text editor. Should definitely have been a more touted Windows feature.

 

[jboydgolfer]

its the small changes that you've got to love in windows 10

 

[RejZoR]

Still, when I discovered keyboard shortcuts my life changed. I can't live without ctrl+alt+a opening a text editor. Should definitely have been a more touted Windows feature.

Ctrl+Alt+A does nothing on my system... hm

 

[Solaris17]

its the small changes that you've got to love in windows 10

People that get upset about this are going to be in for a rude awakening when they find out commands have started to be depreciated since vista and powershell has been the planned replacement for CMD since 8.1.

 

[Frick]

Ctrl+Alt+A does nothing on my system... hm

In Windows 10, dig up the start menu folder.
C:\ProgramData\Microsoft\Windows\Start Menu
C:\Users\userxx\AppData\Roaming\Microsoft\Windows\Start Menu

Right click->Properties, the field keyboard shortcut, assign whatever. The format is ctrl+alt+letter/number. Has been avaliable since ... Windows XP I believe? You can do the same with icons on the desktop (not ones in folders though). It is soooo nice to have. If you use stuff alot it is a lifesaver.

 

[StefanM]

Check out How to Add 'Open command window here as administrator' context menu in Windows 10
(and probably the myriad of other tutorials linked there)

 

[DeathtoGnomes]

Check out How to Add 'Open command window here as administrator' context menu in Windows 10
(and probably the myriad of other tutorials linked there)

There is a ton of good info there.

 

[Mindweaver]

Also, you can hold the windows key then press R to get Run, then type CMD. I was the same at first, but now I've been using it for awhile now. I use it a lot with my Exchange servers... Well, it has a powershell module called Exchange Management Shell which pushed me to learn Powershell outside of Exchange.

 

[Kursah]

Interestingly enough my personal laptop just got the update...and still has Command Prompt listed, not PowerShell...

Edit: Not that it matters...I use both regularly.

 

[jboydgolfer]

People that get upset about this are going to be in for a rude awakening when they find out commands have started to be depreciated since vista and powershell has been the planned replacement for CMD since 8.1.

In a sense I guess I'm lucky in a way, I was an early adopter/tester for windows 10 pre-release. My transition from win7 to win10 has been Kind of like an old man getting into the tub very slowly.

I haven't really been disappointed as of yet with any of the changes from 7 to 10, at least not like I was with Windows 8. Something that I think a lot of people fail to realize is that an operating system is not unlike someone's bed or their favorite chair. It's a very "routine driven experience/environment ", and even the smallest change to that routine ( even if it's more convenient or faster or more sensible)can be very unwelcome to certain users. For instance there's things that I do in windows that I know take longer then possibly using a shortcut command or something like that, but I do it anyway, and furthermore I prefer it that way. I think you'll find a lot of people are that way when it comes to their operating system. Humans are irrational and we surround ourselves with irrational behavior, even when it's not in our best interest.

I personally don't agree with bitching about the changes ,because that's kind a like bitching about the change of the price of gas ,or the clothing that is currently in fashion. Change is always going to occur, and there's a very good chance people aren't going to like all of the changes that do occur and to expect otherwise is silly.it just demonstrates my earlier reference to how humans are irrational

 

[Mussels]

i thought i was the only one that cared about this

welllllllll powershell can use 99% of cmd.

otherwise you dont really need to "dig up" cmd in search since its pretty simple to type CMD.

if you are seriously that bothered you could have probably googled for 20seconds and found out you can change it just like before.

right click on task bar click "taskbar settings" toggle this setting.

i love you

 

[Derek12]

For what I use cmd (ipconfig, ping, diskpart...) PowerShell works just fine

 

[Nokiron]

I just needed CLI (CMD) for stuff that has no interface, like flashing tools. And now I have to learn some new shit for no reason because someone thought shoving PowerShell there by default would make sense. Aaaah, I guess I'll just stick a CMD shortcut into Start menu (which is already crowded but oh well).

Powershell is approximately 5 billion times better than the command-prompt though.

 

[RejZoR]

Clearly isn't if I can't run a damn program without any real switches. Just because I wasn't using its syntax. Which they just by default assume everyone knows and understands. Opposed to decades of MS-DOS synataxes.

I mean, all I wanted to do is run NVFlash and flash a BIOS. So, "nvflash oc.rom". And it did nothing... so, there's that.

 

[Mussels]

Clearly isn't if I can't run a damn program without any real switches. Just because I wasn't using its syntax. Which they just by default assume everyone knows and understands. Opposed to decades of MS-DOS synataxes.

I mean, all I wanted to do is run NVFlash and flash a BIOS. So, "nvflash oc.rom". And it did nothing... so, there's that.

for most people its enough - for us, theres an off button (that i never would have found without this thread)

 

[RejZoR]

How do you translate CMD commands into PwrShell syntax? I mean, how would it look like if you wanted to run something this simple?

 

[Nokiron]

Clearly isn't if I can't run a damn program without any real switches. Just because I wasn't using its syntax. Which they just by default assume everyone knows and understands. Opposed to decades of MS-DOS synataxes.

I mean, all I wanted to do is run NVFlash and flash a BIOS. So, "nvflash oc.rom". And it did nothing... so, there's that.

Powershell is a scripting environment, the command prompt is a legacy environment. It's built on modern principles which is why the same commands rarely overlap.
You have to learn some basic stuff like you did with the command prompt at first. I highly recommend it, if you ever do work in an IT enviroment Powershell is absolutely the only option.

That legacy prompt will inevitably be replaced.

I have never used nvflash so I don't know the commands, but i'm pretty sure you only have to do it like this

.\nvflash oc.rom

 

[RejZoR]

This is so silly...

In CMD, the command was:
nvflash bios.rom

In PowerShell, it's:
.\nvflash bios.rom

What's the point of .\ in front!? Does it have any other function or is it there just to annoy us?

 

[W1zzard]

What's the point of .\ in front!? Does it have any other function or is it there just to annoy us?

. means "current directory", \ is the directory separator, so "start something inside current directory".

I guess $PATH no longer includes current directory, which is not a bad idea, and has been like that on unix for half a decade