Get back “Open command window here” context menu option in Windows 10

Windows 10 Creators Update removes the “Open Command Prompt here” context menu entry and replaces it with “Open PowerShell window here”. Microsoft, in an effort to bring the best command line experiences to the forefront for all power users, has made PowerShell as the de facto command shell.

You may also be knowing that since the preview build 14971, “Command Prompt” and “Command Prompt (Admin)” entries in the Win+X menu (the menu which appears when you right-click Start) were replaced with PowerShell links.

Quoting Microsoft:

It (PowerShell) replaces Command Prompt (aka, “cmd.exe”) in the WIN + X menu, in File Explorer’s File menu, and in the context menu that appears when you shift-right-click the whitespace in File Explorer. Typing “cmd” (or “powershell”) in File Explorer’s address bar will remain a quick way to launch the command shell at that location. For those who prefer to use Command Prompt, you can opt out of the WIN + X change by opening Settings > Personalization > Taskbar, and turning “Replace Command Prompt with Windows PowerShell in the menu when I right-click the Start button or press Windows key+X” to “Off”.

For more information, check out the 14971 Preview Build announcement post.

Although you’re able to run the old commands in the PowerShell window, you need to use the “.exe” suffix when running certain commands. For instance, running the “SC” command under PowerShell window gives different results than what you get when running the same command from a regular Command Prompt shell.

“SC” is understood as the alias for “Set-Content” PowerShell cmdlet. So to manage services using the SC (SC.EXE) command in the PowerShell window, you’ll need to type the file extension — .EXE. Whereas the regular Command Prompt (CMD.exe) shell knows SC is nothing but SC.EXE, assuming no file of the same name and with a .COM extension exists in the path.

Add Command Prompt to the Context menu

If you’re fond of the old Command Prompt (cmd.exe), you can add the traditional “Open Command window here” option back in the context menu for file system folders and drives, using a Registry edit.

Copy the following lines to Notepad, and save it with a .REG extension, say cmdhere.reg. Double-click the file to apply the registry settings.

Windows Registry Editor Version 5.00


@="cmd.exe /s /k pushd \"%V\""


@="cmd.exe /s /k pushd \"%V\""


@="cmd.exe /s /k pushd \"%V\""

Alternately, you can download the REG file.


This adds the “Open command window here” option to the right-click menu for folders and drives, which when clicked, opens a Command Prompt window at the current drive or directory path.

add cmd here to right-click menu

One small request: If you liked this post, please share this?

One "tiny" share from you would seriously help a lot with the growth of this blog. Some great suggestions:
  • Pin it!
  • Share it to your favorite blog + Facebook, Reddit
  • Tweet it!
So thank you so much for your support, my reader. It won't take more than 10 seconds of your time. The share buttons are right below. :)

About the author

Ramesh Srinivasan founded back in 2005. He is passionate about Microsoft technologies and he has been a Microsoft Most Valuable Professional (MVP) for 10 consecutive years from 2003 to 2012.

58 thoughts on “Get back “Open command window here” context menu option in Windows 10”

  1. Thanks for the info and reg file!
    I’m hoping somebody would stop Microsoft making a mess in every update for God’s sake!

  2. Microsoft has given the fix for returning CMD back into the Start menu, but not for the Windows Explorer context.
    Your .reg and explanation is very welcome.

  3. I downloaded the file, and it works perfectly. I personally think they should both be there. It should’ve been like that for a long time, in my opinion.

  4. Thanks, now I don’t have to open cmd from the menu and browse there through commands anymore. I don’t get why Microsoft decided to remove this, powershell can’t do everything that command prompt can.

  5. thank you so muchhh!!!you help me so much guys i’ve been checking all day and i finally found it here in this website lifesaver love you guys!!!

  6. Your regedit works perfectly. The system should have been like this from Microsoft. Add new features, don’t delete the old ones!
    Powershell does not do ‘dir’ correctly.

  7. Thanks for the .reg file. I had to log out of my standard account and the log into my admin account for the .reg file to work.

  8. I’ve created a .reg file with the contents shown above, run the reg file and confirmed that the registry contains these entries. Yet the context menu for any directory in File Explorer does NOT contain an entry for a command window.

  9. The zip package worked excellently. Thanks a lot sir. Shame on you MS for “forcing” stuffs on us! Shameful act from MS.

  10. Also you can add this parameter:
    After each “NoWorkingDirectory”=”” line, so this menu option will have cmd.exe icon and get easier to distinguish in context menu.

  11. Agree with SagePtr, but I used
    Maybe cmd wasn’t in my path for some reason. The “,0” is probably optional

  12. Others in other places on the web trying to help with complex 10 step registry edits, including permissions changes which I know from past experience are problematic for even some who are willing to edit the registry when it’s straight forward. I followed and double-checked my steps, twice and they did not deliver! Your Reg delivered (THANKS), and thank you for including an UNDO in case I ever need that. I do wish Microsoft would allow me to have a stasis on my PC, as I’m happy with it as-is. The problem is while MS did an extensive check on my PC to upgrade to Windows 10 they don’t do anything like that on any subsequent upgrades since that change years ago. As a result Microsoft has taken their upgrades over a year past when my manufacturer, DELL, said my PC was no longer compatible with Win10 as it was in June 2020. Thanks again!
    Dean Pennington


Leave a Comment