Windows 10: Is there a way to add the "Open command prompt" back tin the file Menu

After the creator's update they removed the Open command prompt under file in the file explorer. Is there a way to add it back?

:)

 

Lumia " The Future is Here "

This is a support forum, not a complaints department.

I suggest you directly submit your complaints about hardware to Nokia and software to Microsoft.



Also it often helps to read reviews when switching platforms to make sure it suits your needs. From what you've said the Lumia 820 clearly doesn't suit you.

 

Lumia " The Future is Here "

psychomania: This is a support forum, not a complaints department.



psychomania: Also it often helps to read reviews when switching platforms to make sure it suits your needs. From what you've said the Lumia 820 clearly doesn't suit you.



What RSXforever wrote was a kind of review, that can help other people to judge, if Lumia is the right phone for them.

 

Interesting. You do know that you can do anything in a powershell prompt that you can in command prompt, right?

 

Just trying something like

for %i in ("*.mp4") do echo "%~ni"

returns an error.

I don't wanna learn a new language.

 

If you like, you could add it back to the context menu.

Open command window here - Add in Windows 10 - Windows 10 Customization Tutorials

Open command window here as administrator - Add in Windows 10 - Windows 10 Customization Tutorials

 

Thank you. Better than nothing I guess.

 

...and on the Win+X menu (or right-click on Start).
Show Command Prompt or Windows PowerShell on Win+X menu in Windows 10

 

PowerShell commands are often ridiculously verbose.

 

@GoodTimesAhead


Just FWIW.....if anyone must have a command prompt and feel stuck with Powershell, simply type cmd in Powershell and hit enter. You'll be at a regular Command Prompt. It's only another way of getting there, not the best, but an easy way. If the OP doesn't like/want to use Powershell, this an alternative. Just a suggestion.

 

If you put those commands in a .cmd (or even .bat) file, then execute them, they will work because Powershell will execute .cmd and .bat files with cmd.exe

If you want to type them into the shell natively, then just type cmd and you're in a cmd prompt within Powershell.

 

I don’t think there’s a way to get this option back. No one’s found anything yet and I’ve also tried a few things myself.

Instead, what you could do is make the “Open Windows PowerShell” Explorer file menu option open the command prompt by changing the data value of the “HKLM\SOFTWARE\Classes\Directory\shell\Powershell\command” (“HKCR\Directory\shell\Powershell\command”) registry value from
Code: powershell.exe -noexit -command Set-Location '%V'[/quote] to
Code: cmd.exe /s /k pushd "%V"[/quote] It will still say “Open Windows PowerShell” though.

But as the best work around to this problem, I encourage any one reading this to pick up the newer language.

PowerShell commands are often ridiculously verbose. I’d say this is a good thing anyway, but maybe you say this because you often see people write and share PowerShell commands in their most verbose form. PowerShell lines can often be reduced quite a lot. You can be as verbose or as implicit as you want.

For example, the command prompt command
Code: for %i in ("*.mp4") do echo "%~ni"[/quote] translates to following in PowerShell
Code: Get-ChildItem -Path '*.mp4' | ForEach-Object -MemberName BaseName | Out-Default[/quote] It’s longer than the command prompt command in its verbose form, but it can also be written in short form as
Code: ls *.mp4 | % BaseName[/quote] Additionally, it is expected you’d use tab completion and never fully type out commands.

 

Is the goal to have the quickest link to powershell? Consider pinning the icon to the task bar like browsers, file explorer etc.

 

Thanks for emphasizing what I posted in #8.

 

I suspect that you are correct. *Smile

When I was studying W2K8, we did some PowerShell exercises.
In one of the exercises, we had to add a new user/password/group to AD and the PS command was enormous.

Verbose is good in scripts, because it:

• Doesn't matter how long it takes type it in correctly
• Makes it easier to figure out what the script does at a later date

I copy complicated CLI commands from the web examples (in both Linux & Windows) when I need to use them.

I wouldn't have guessed that those two PS commands were identical (if you hadn't made it obvious that they were). *Smile