How do I change “Open with Powershell” to “Open with Command Prompt” when shift-rightclicking in...
Shift-rightclicking an empty spot in Explorer displays "Open with PowerShell" instead of "Open with Command Prompt" since the Creators Update (2017-04). How can I get the old behaviour back where it shows "Open with Command Prompt"?
I tried changing the setting "Show PowerShell instead of Command Prompt when rightclicking the Start Menu or pressing Windows + X" to off, but that didn't change the shift+rightclick menu.
windows-10 windows-10-v1703
add a comment |
Shift-rightclicking an empty spot in Explorer displays "Open with PowerShell" instead of "Open with Command Prompt" since the Creators Update (2017-04). How can I get the old behaviour back where it shows "Open with Command Prompt"?
I tried changing the setting "Show PowerShell instead of Command Prompt when rightclicking the Start Menu or pressing Windows + X" to off, but that didn't change the shift+rightclick menu.
windows-10 windows-10-v1703
add a comment |
Shift-rightclicking an empty spot in Explorer displays "Open with PowerShell" instead of "Open with Command Prompt" since the Creators Update (2017-04). How can I get the old behaviour back where it shows "Open with Command Prompt"?
I tried changing the setting "Show PowerShell instead of Command Prompt when rightclicking the Start Menu or pressing Windows + X" to off, but that didn't change the shift+rightclick menu.
windows-10 windows-10-v1703
Shift-rightclicking an empty spot in Explorer displays "Open with PowerShell" instead of "Open with Command Prompt" since the Creators Update (2017-04). How can I get the old behaviour back where it shows "Open with Command Prompt"?
I tried changing the setting "Show PowerShell instead of Command Prompt when rightclicking the Start Menu or pressing Windows + X" to off, but that didn't change the shift+rightclick menu.
windows-10 windows-10-v1703
windows-10 windows-10-v1703
edited Jul 30 '18 at 18:25
Peter Mortensen
8,336166184
8,336166184
asked Apr 21 '17 at 16:12
nelson2tm
2631312
2631312
add a comment |
add a comment |
6 Answers
6
active
oldest
votes
Open regedit.exe, go to HKEY_CLASSES_ROOTDirectoryshellcmd
, take ownership of the key, add your user account full permissions and change the name of the DWORD from HideBasedOnVelocityId
to ShowBasedOnVelocityId
to enable the command prompt entry again.
Or apply Andrew Richards tweak to have both shown (cmd and PowerShell, also with entry to have elevate (running as admin) version),
by importing his .reg file (create a new txt file, paste the content and rename the file extension to reg):
Windows Registry Editor Version 5.00
; Command Prompt
[HKEY_CLASSES_ROOTDirectoryshell1MenuCmd]
"MUIVerb"="Command Prompts"
"Icon"="cmd.exe"
"ExtendedSubCommandsKey"="Directory\ContextMenus\MenuCmd"
[HKEY_CLASSES_ROOTDirectorybackgroundshell1MenuCmd]
"MUIVerb"="Command Prompts"
"Icon"="cmd.exe"
"ExtendedSubCommandsKey"="Directory\ContextMenus\MenuCmd"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuCmdshellopen]
"MUIVerb"="Command Prompt"
"Icon"="cmd.exe"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuCmdshellopencommand]
@="cmd.exe /s /k pushd "%V""
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuCmdshellrunas]
"MUIVerb"="Command Prompt Elevated"
"Icon"="cmd.exe"
"HasLUAShield"=""
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuCmdshellrunascommand]
@="cmd.exe /s /k pushd "%V""
; PowerShell
[HKEY_CLASSES_ROOTDirectoryshell2MenuPowerShell]
"MUIVerb"="PowerShell Prompts"
"Icon"="powershell.exe"
"ExtendedSubCommandsKey"="Directory\ContextMenus\MenuPowerShell"
[HKEY_CLASSES_ROOTDirectorybackgroundshell2MenuPowerShell]
"MUIVerb"="PowerShell Prompts"
"Icon"="powershell.exe"
"ExtendedSubCommandsKey"="Directory\ContextMenus\MenuPowerShell"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuPowerShellshellopen]
"MUIVerb"="PowerShell"
"Icon"="powershell.exe"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuPowerShellshellopencommand]
@="powershell.exe -noexit -command Set-Location '%V'"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuPowerShellshellrunas]
"MUIVerb"="PowerShell Elevated"
"Icon"="powershell.exe"
"HasLUAShield"=""
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuPowerShellshellrunascommand]
@="powershell.exe -noexit -command Set-Location '%V'"
; Ensure OS Entries are on the Extended Menu (Shift-Right Click)
[HKEY_CLASSES_ROOTDirectoryshellcmd]
"Extended"=""
[HKEY_CLASSES_ROOTDirectorybackgroundshellcmd]
"Extended"=""
[HKEY_CLASSES_ROOTDirectoryshellPowershell]
"Extended"=""
[HKEY_CLASSES_ROOTDirectorybackgroundshellPowershell]
"Extended"=""
The 2nd method in your answer is good. But for someone who has no idea what to do with the .reg, just copy the file text into a .txt file & rename the file <name>.reg & double click it to run. Even though there is error message, the operation is success
– KharoBangdo
Sep 5 '17 at 4:41
2
How to restore from these reg keys?
– vee
Jan 13 '18 at 14:41
I'd rather prefer all of them to be sub menus of a single menu item. In original article there are also GIT bash items, makes default menu too cluttered.
– Pavel
Jan 20 '18 at 16:00
1
This answer didn't work for me until I applied the solution to all three of these registry paths:HKEY_CLASSES_ROOTDirectoryBackgroundshellcmd
,HKEY_CLASSES_ROOTDirectoryshellcmd
, andHKEY_CLASSES_ROOTDriveshellcmd
as directed here
– Terrance
Sep 5 '18 at 13:47
1
That .reg file works like a charm.
– MC Emperor
Sep 14 '18 at 22:03
|
show 4 more comments
This is extremely easy to acomplish
- In the Taskbar and Start Menu Properties window, go to the Navigation tab and uncheck the Replace Command Prompt with Windows
PowerShell option.
- Click Apply for the change to take effect.
Source: Replace Command Prompt With PowerShell On Power User Menu In Windows 10
Additional Source: Show Command Prompt or PowerShell in Win+X Power User Tasks Menu in Windows 10
Additional Source: Microsoft Replaces Command Prompt With PowerShell As Windows 10 Default Shell
13
This only changes the Windows + x menu, not the "Open with" menu when shift + rightclicking an empty spot in Explorer.
– nelson2tm
Apr 21 '17 at 17:12
1
no Ramhound this doesn't work. you ONLY change what shows up in WinX menu on right click on start button, not doing a rightclick inside Windows/File Explorer
– magicandre1981
Nov 3 '17 at 15:13
add a comment |
As a quick alternative to the other answers, you can type cmd
on the address bar of Explorer to open a command prompt cd
'd to the current directory. (If you are more of a keyboard person, you can use the Ctrl + L
shortcut to focus the address bar and then type cmd
.)
This works for powershell
too.
add a comment |
To hit all of the locations where Windows has changed this, you can use the following registry file after taking ownership of each key in question.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINESOFTWAREClassesDirectorybackgroundshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
"HideBasedOnVelocityId"=-
[HKEY_LOCAL_MACHINESOFTWAREClassesDirectorybackgroundshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
"ShowBasedOnVelocityId"=-
[HKEY_LOCAL_MACHINESOFTWAREClassesDirectoryshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
"HideBasedOnVelocityId"=-
[HKEY_LOCAL_MACHINESOFTWAREClassesDirectoryshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
"ShowBasedOnVelocityId"=-
[HKEY_CLASSES_ROOTDriveshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
"HideBasedOnVelocityId"=-
[HKEY_CLASSES_ROOTDriveshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
"ShowBasedOnVelocityId"=-
I would just take ownership of the [HKCRDirectory]
and [HKCRDrive]
keys recursively and force permission inheritance.
add a comment |
This hides powershell from the Shift-Right Click context menu and makes cmd visible.
Using a simple text editor such as Notepad, save the following code to a file with the .REG extension (e.g. MyImport.reg
). Then double-click the saved file and follow the prompts to import it into the Registry:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOTDirectoryBackgroundshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDirectoryBackgroundshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDirectoryshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDirectoryshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDriveshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDriveshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
Without explaining what this does and how to use it, this is not an answer. Please edit your post to clarify.
– Twisty Impersonator
Dec 20 '18 at 11:35
done!..........
– Riccardo La Marca
Dec 20 '18 at 11:44
1
Better, however see my edit for more of what I was expecting (not all users will know how to import content into the Registry).
– Twisty Impersonator
Dec 20 '18 at 12:33
add a comment |
In Windows 10 this is now included in the taskbar settings.
3
"This only changes the Windows + x menu, not the "Open with" menu when shift + rightclicking an empty spot in Explorer." -nelson2tm
– Matt M.
Apr 10 '18 at 21:18
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1201988%2fhow-do-i-change-open-with-powershell-to-open-with-command-prompt-when-shift%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
Open regedit.exe, go to HKEY_CLASSES_ROOTDirectoryshellcmd
, take ownership of the key, add your user account full permissions and change the name of the DWORD from HideBasedOnVelocityId
to ShowBasedOnVelocityId
to enable the command prompt entry again.
Or apply Andrew Richards tweak to have both shown (cmd and PowerShell, also with entry to have elevate (running as admin) version),
by importing his .reg file (create a new txt file, paste the content and rename the file extension to reg):
Windows Registry Editor Version 5.00
; Command Prompt
[HKEY_CLASSES_ROOTDirectoryshell1MenuCmd]
"MUIVerb"="Command Prompts"
"Icon"="cmd.exe"
"ExtendedSubCommandsKey"="Directory\ContextMenus\MenuCmd"
[HKEY_CLASSES_ROOTDirectorybackgroundshell1MenuCmd]
"MUIVerb"="Command Prompts"
"Icon"="cmd.exe"
"ExtendedSubCommandsKey"="Directory\ContextMenus\MenuCmd"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuCmdshellopen]
"MUIVerb"="Command Prompt"
"Icon"="cmd.exe"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuCmdshellopencommand]
@="cmd.exe /s /k pushd "%V""
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuCmdshellrunas]
"MUIVerb"="Command Prompt Elevated"
"Icon"="cmd.exe"
"HasLUAShield"=""
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuCmdshellrunascommand]
@="cmd.exe /s /k pushd "%V""
; PowerShell
[HKEY_CLASSES_ROOTDirectoryshell2MenuPowerShell]
"MUIVerb"="PowerShell Prompts"
"Icon"="powershell.exe"
"ExtendedSubCommandsKey"="Directory\ContextMenus\MenuPowerShell"
[HKEY_CLASSES_ROOTDirectorybackgroundshell2MenuPowerShell]
"MUIVerb"="PowerShell Prompts"
"Icon"="powershell.exe"
"ExtendedSubCommandsKey"="Directory\ContextMenus\MenuPowerShell"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuPowerShellshellopen]
"MUIVerb"="PowerShell"
"Icon"="powershell.exe"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuPowerShellshellopencommand]
@="powershell.exe -noexit -command Set-Location '%V'"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuPowerShellshellrunas]
"MUIVerb"="PowerShell Elevated"
"Icon"="powershell.exe"
"HasLUAShield"=""
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuPowerShellshellrunascommand]
@="powershell.exe -noexit -command Set-Location '%V'"
; Ensure OS Entries are on the Extended Menu (Shift-Right Click)
[HKEY_CLASSES_ROOTDirectoryshellcmd]
"Extended"=""
[HKEY_CLASSES_ROOTDirectorybackgroundshellcmd]
"Extended"=""
[HKEY_CLASSES_ROOTDirectoryshellPowershell]
"Extended"=""
[HKEY_CLASSES_ROOTDirectorybackgroundshellPowershell]
"Extended"=""
The 2nd method in your answer is good. But for someone who has no idea what to do with the .reg, just copy the file text into a .txt file & rename the file <name>.reg & double click it to run. Even though there is error message, the operation is success
– KharoBangdo
Sep 5 '17 at 4:41
2
How to restore from these reg keys?
– vee
Jan 13 '18 at 14:41
I'd rather prefer all of them to be sub menus of a single menu item. In original article there are also GIT bash items, makes default menu too cluttered.
– Pavel
Jan 20 '18 at 16:00
1
This answer didn't work for me until I applied the solution to all three of these registry paths:HKEY_CLASSES_ROOTDirectoryBackgroundshellcmd
,HKEY_CLASSES_ROOTDirectoryshellcmd
, andHKEY_CLASSES_ROOTDriveshellcmd
as directed here
– Terrance
Sep 5 '18 at 13:47
1
That .reg file works like a charm.
– MC Emperor
Sep 14 '18 at 22:03
|
show 4 more comments
Open regedit.exe, go to HKEY_CLASSES_ROOTDirectoryshellcmd
, take ownership of the key, add your user account full permissions and change the name of the DWORD from HideBasedOnVelocityId
to ShowBasedOnVelocityId
to enable the command prompt entry again.
Or apply Andrew Richards tweak to have both shown (cmd and PowerShell, also with entry to have elevate (running as admin) version),
by importing his .reg file (create a new txt file, paste the content and rename the file extension to reg):
Windows Registry Editor Version 5.00
; Command Prompt
[HKEY_CLASSES_ROOTDirectoryshell1MenuCmd]
"MUIVerb"="Command Prompts"
"Icon"="cmd.exe"
"ExtendedSubCommandsKey"="Directory\ContextMenus\MenuCmd"
[HKEY_CLASSES_ROOTDirectorybackgroundshell1MenuCmd]
"MUIVerb"="Command Prompts"
"Icon"="cmd.exe"
"ExtendedSubCommandsKey"="Directory\ContextMenus\MenuCmd"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuCmdshellopen]
"MUIVerb"="Command Prompt"
"Icon"="cmd.exe"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuCmdshellopencommand]
@="cmd.exe /s /k pushd "%V""
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuCmdshellrunas]
"MUIVerb"="Command Prompt Elevated"
"Icon"="cmd.exe"
"HasLUAShield"=""
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuCmdshellrunascommand]
@="cmd.exe /s /k pushd "%V""
; PowerShell
[HKEY_CLASSES_ROOTDirectoryshell2MenuPowerShell]
"MUIVerb"="PowerShell Prompts"
"Icon"="powershell.exe"
"ExtendedSubCommandsKey"="Directory\ContextMenus\MenuPowerShell"
[HKEY_CLASSES_ROOTDirectorybackgroundshell2MenuPowerShell]
"MUIVerb"="PowerShell Prompts"
"Icon"="powershell.exe"
"ExtendedSubCommandsKey"="Directory\ContextMenus\MenuPowerShell"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuPowerShellshellopen]
"MUIVerb"="PowerShell"
"Icon"="powershell.exe"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuPowerShellshellopencommand]
@="powershell.exe -noexit -command Set-Location '%V'"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuPowerShellshellrunas]
"MUIVerb"="PowerShell Elevated"
"Icon"="powershell.exe"
"HasLUAShield"=""
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuPowerShellshellrunascommand]
@="powershell.exe -noexit -command Set-Location '%V'"
; Ensure OS Entries are on the Extended Menu (Shift-Right Click)
[HKEY_CLASSES_ROOTDirectoryshellcmd]
"Extended"=""
[HKEY_CLASSES_ROOTDirectorybackgroundshellcmd]
"Extended"=""
[HKEY_CLASSES_ROOTDirectoryshellPowershell]
"Extended"=""
[HKEY_CLASSES_ROOTDirectorybackgroundshellPowershell]
"Extended"=""
The 2nd method in your answer is good. But for someone who has no idea what to do with the .reg, just copy the file text into a .txt file & rename the file <name>.reg & double click it to run. Even though there is error message, the operation is success
– KharoBangdo
Sep 5 '17 at 4:41
2
How to restore from these reg keys?
– vee
Jan 13 '18 at 14:41
I'd rather prefer all of them to be sub menus of a single menu item. In original article there are also GIT bash items, makes default menu too cluttered.
– Pavel
Jan 20 '18 at 16:00
1
This answer didn't work for me until I applied the solution to all three of these registry paths:HKEY_CLASSES_ROOTDirectoryBackgroundshellcmd
,HKEY_CLASSES_ROOTDirectoryshellcmd
, andHKEY_CLASSES_ROOTDriveshellcmd
as directed here
– Terrance
Sep 5 '18 at 13:47
1
That .reg file works like a charm.
– MC Emperor
Sep 14 '18 at 22:03
|
show 4 more comments
Open regedit.exe, go to HKEY_CLASSES_ROOTDirectoryshellcmd
, take ownership of the key, add your user account full permissions and change the name of the DWORD from HideBasedOnVelocityId
to ShowBasedOnVelocityId
to enable the command prompt entry again.
Or apply Andrew Richards tweak to have both shown (cmd and PowerShell, also with entry to have elevate (running as admin) version),
by importing his .reg file (create a new txt file, paste the content and rename the file extension to reg):
Windows Registry Editor Version 5.00
; Command Prompt
[HKEY_CLASSES_ROOTDirectoryshell1MenuCmd]
"MUIVerb"="Command Prompts"
"Icon"="cmd.exe"
"ExtendedSubCommandsKey"="Directory\ContextMenus\MenuCmd"
[HKEY_CLASSES_ROOTDirectorybackgroundshell1MenuCmd]
"MUIVerb"="Command Prompts"
"Icon"="cmd.exe"
"ExtendedSubCommandsKey"="Directory\ContextMenus\MenuCmd"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuCmdshellopen]
"MUIVerb"="Command Prompt"
"Icon"="cmd.exe"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuCmdshellopencommand]
@="cmd.exe /s /k pushd "%V""
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuCmdshellrunas]
"MUIVerb"="Command Prompt Elevated"
"Icon"="cmd.exe"
"HasLUAShield"=""
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuCmdshellrunascommand]
@="cmd.exe /s /k pushd "%V""
; PowerShell
[HKEY_CLASSES_ROOTDirectoryshell2MenuPowerShell]
"MUIVerb"="PowerShell Prompts"
"Icon"="powershell.exe"
"ExtendedSubCommandsKey"="Directory\ContextMenus\MenuPowerShell"
[HKEY_CLASSES_ROOTDirectorybackgroundshell2MenuPowerShell]
"MUIVerb"="PowerShell Prompts"
"Icon"="powershell.exe"
"ExtendedSubCommandsKey"="Directory\ContextMenus\MenuPowerShell"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuPowerShellshellopen]
"MUIVerb"="PowerShell"
"Icon"="powershell.exe"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuPowerShellshellopencommand]
@="powershell.exe -noexit -command Set-Location '%V'"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuPowerShellshellrunas]
"MUIVerb"="PowerShell Elevated"
"Icon"="powershell.exe"
"HasLUAShield"=""
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuPowerShellshellrunascommand]
@="powershell.exe -noexit -command Set-Location '%V'"
; Ensure OS Entries are on the Extended Menu (Shift-Right Click)
[HKEY_CLASSES_ROOTDirectoryshellcmd]
"Extended"=""
[HKEY_CLASSES_ROOTDirectorybackgroundshellcmd]
"Extended"=""
[HKEY_CLASSES_ROOTDirectoryshellPowershell]
"Extended"=""
[HKEY_CLASSES_ROOTDirectorybackgroundshellPowershell]
"Extended"=""
Open regedit.exe, go to HKEY_CLASSES_ROOTDirectoryshellcmd
, take ownership of the key, add your user account full permissions and change the name of the DWORD from HideBasedOnVelocityId
to ShowBasedOnVelocityId
to enable the command prompt entry again.
Or apply Andrew Richards tweak to have both shown (cmd and PowerShell, also with entry to have elevate (running as admin) version),
by importing his .reg file (create a new txt file, paste the content and rename the file extension to reg):
Windows Registry Editor Version 5.00
; Command Prompt
[HKEY_CLASSES_ROOTDirectoryshell1MenuCmd]
"MUIVerb"="Command Prompts"
"Icon"="cmd.exe"
"ExtendedSubCommandsKey"="Directory\ContextMenus\MenuCmd"
[HKEY_CLASSES_ROOTDirectorybackgroundshell1MenuCmd]
"MUIVerb"="Command Prompts"
"Icon"="cmd.exe"
"ExtendedSubCommandsKey"="Directory\ContextMenus\MenuCmd"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuCmdshellopen]
"MUIVerb"="Command Prompt"
"Icon"="cmd.exe"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuCmdshellopencommand]
@="cmd.exe /s /k pushd "%V""
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuCmdshellrunas]
"MUIVerb"="Command Prompt Elevated"
"Icon"="cmd.exe"
"HasLUAShield"=""
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuCmdshellrunascommand]
@="cmd.exe /s /k pushd "%V""
; PowerShell
[HKEY_CLASSES_ROOTDirectoryshell2MenuPowerShell]
"MUIVerb"="PowerShell Prompts"
"Icon"="powershell.exe"
"ExtendedSubCommandsKey"="Directory\ContextMenus\MenuPowerShell"
[HKEY_CLASSES_ROOTDirectorybackgroundshell2MenuPowerShell]
"MUIVerb"="PowerShell Prompts"
"Icon"="powershell.exe"
"ExtendedSubCommandsKey"="Directory\ContextMenus\MenuPowerShell"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuPowerShellshellopen]
"MUIVerb"="PowerShell"
"Icon"="powershell.exe"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuPowerShellshellopencommand]
@="powershell.exe -noexit -command Set-Location '%V'"
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuPowerShellshellrunas]
"MUIVerb"="PowerShell Elevated"
"Icon"="powershell.exe"
"HasLUAShield"=""
[HKEY_CLASSES_ROOTDirectoryContextMenusMenuPowerShellshellrunascommand]
@="powershell.exe -noexit -command Set-Location '%V'"
; Ensure OS Entries are on the Extended Menu (Shift-Right Click)
[HKEY_CLASSES_ROOTDirectoryshellcmd]
"Extended"=""
[HKEY_CLASSES_ROOTDirectorybackgroundshellcmd]
"Extended"=""
[HKEY_CLASSES_ROOTDirectoryshellPowershell]
"Extended"=""
[HKEY_CLASSES_ROOTDirectorybackgroundshellPowershell]
"Extended"=""
edited Jul 30 '18 at 18:26
Peter Mortensen
8,336166184
8,336166184
answered Apr 22 '17 at 6:30
magicandre1981
81.1k20124203
81.1k20124203
The 2nd method in your answer is good. But for someone who has no idea what to do with the .reg, just copy the file text into a .txt file & rename the file <name>.reg & double click it to run. Even though there is error message, the operation is success
– KharoBangdo
Sep 5 '17 at 4:41
2
How to restore from these reg keys?
– vee
Jan 13 '18 at 14:41
I'd rather prefer all of them to be sub menus of a single menu item. In original article there are also GIT bash items, makes default menu too cluttered.
– Pavel
Jan 20 '18 at 16:00
1
This answer didn't work for me until I applied the solution to all three of these registry paths:HKEY_CLASSES_ROOTDirectoryBackgroundshellcmd
,HKEY_CLASSES_ROOTDirectoryshellcmd
, andHKEY_CLASSES_ROOTDriveshellcmd
as directed here
– Terrance
Sep 5 '18 at 13:47
1
That .reg file works like a charm.
– MC Emperor
Sep 14 '18 at 22:03
|
show 4 more comments
The 2nd method in your answer is good. But for someone who has no idea what to do with the .reg, just copy the file text into a .txt file & rename the file <name>.reg & double click it to run. Even though there is error message, the operation is success
– KharoBangdo
Sep 5 '17 at 4:41
2
How to restore from these reg keys?
– vee
Jan 13 '18 at 14:41
I'd rather prefer all of them to be sub menus of a single menu item. In original article there are also GIT bash items, makes default menu too cluttered.
– Pavel
Jan 20 '18 at 16:00
1
This answer didn't work for me until I applied the solution to all three of these registry paths:HKEY_CLASSES_ROOTDirectoryBackgroundshellcmd
,HKEY_CLASSES_ROOTDirectoryshellcmd
, andHKEY_CLASSES_ROOTDriveshellcmd
as directed here
– Terrance
Sep 5 '18 at 13:47
1
That .reg file works like a charm.
– MC Emperor
Sep 14 '18 at 22:03
The 2nd method in your answer is good. But for someone who has no idea what to do with the .reg, just copy the file text into a .txt file & rename the file <name>.reg & double click it to run. Even though there is error message, the operation is success
– KharoBangdo
Sep 5 '17 at 4:41
The 2nd method in your answer is good. But for someone who has no idea what to do with the .reg, just copy the file text into a .txt file & rename the file <name>.reg & double click it to run. Even though there is error message, the operation is success
– KharoBangdo
Sep 5 '17 at 4:41
2
2
How to restore from these reg keys?
– vee
Jan 13 '18 at 14:41
How to restore from these reg keys?
– vee
Jan 13 '18 at 14:41
I'd rather prefer all of them to be sub menus of a single menu item. In original article there are also GIT bash items, makes default menu too cluttered.
– Pavel
Jan 20 '18 at 16:00
I'd rather prefer all of them to be sub menus of a single menu item. In original article there are also GIT bash items, makes default menu too cluttered.
– Pavel
Jan 20 '18 at 16:00
1
1
This answer didn't work for me until I applied the solution to all three of these registry paths:
HKEY_CLASSES_ROOTDirectoryBackgroundshellcmd
, HKEY_CLASSES_ROOTDirectoryshellcmd
, and HKEY_CLASSES_ROOTDriveshellcmd
as directed here– Terrance
Sep 5 '18 at 13:47
This answer didn't work for me until I applied the solution to all three of these registry paths:
HKEY_CLASSES_ROOTDirectoryBackgroundshellcmd
, HKEY_CLASSES_ROOTDirectoryshellcmd
, and HKEY_CLASSES_ROOTDriveshellcmd
as directed here– Terrance
Sep 5 '18 at 13:47
1
1
That .reg file works like a charm.
– MC Emperor
Sep 14 '18 at 22:03
That .reg file works like a charm.
– MC Emperor
Sep 14 '18 at 22:03
|
show 4 more comments
This is extremely easy to acomplish
- In the Taskbar and Start Menu Properties window, go to the Navigation tab and uncheck the Replace Command Prompt with Windows
PowerShell option.
- Click Apply for the change to take effect.
Source: Replace Command Prompt With PowerShell On Power User Menu In Windows 10
Additional Source: Show Command Prompt or PowerShell in Win+X Power User Tasks Menu in Windows 10
Additional Source: Microsoft Replaces Command Prompt With PowerShell As Windows 10 Default Shell
13
This only changes the Windows + x menu, not the "Open with" menu when shift + rightclicking an empty spot in Explorer.
– nelson2tm
Apr 21 '17 at 17:12
1
no Ramhound this doesn't work. you ONLY change what shows up in WinX menu on right click on start button, not doing a rightclick inside Windows/File Explorer
– magicandre1981
Nov 3 '17 at 15:13
add a comment |
This is extremely easy to acomplish
- In the Taskbar and Start Menu Properties window, go to the Navigation tab and uncheck the Replace Command Prompt with Windows
PowerShell option.
- Click Apply for the change to take effect.
Source: Replace Command Prompt With PowerShell On Power User Menu In Windows 10
Additional Source: Show Command Prompt or PowerShell in Win+X Power User Tasks Menu in Windows 10
Additional Source: Microsoft Replaces Command Prompt With PowerShell As Windows 10 Default Shell
13
This only changes the Windows + x menu, not the "Open with" menu when shift + rightclicking an empty spot in Explorer.
– nelson2tm
Apr 21 '17 at 17:12
1
no Ramhound this doesn't work. you ONLY change what shows up in WinX menu on right click on start button, not doing a rightclick inside Windows/File Explorer
– magicandre1981
Nov 3 '17 at 15:13
add a comment |
This is extremely easy to acomplish
- In the Taskbar and Start Menu Properties window, go to the Navigation tab and uncheck the Replace Command Prompt with Windows
PowerShell option.
- Click Apply for the change to take effect.
Source: Replace Command Prompt With PowerShell On Power User Menu In Windows 10
Additional Source: Show Command Prompt or PowerShell in Win+X Power User Tasks Menu in Windows 10
Additional Source: Microsoft Replaces Command Prompt With PowerShell As Windows 10 Default Shell
This is extremely easy to acomplish
- In the Taskbar and Start Menu Properties window, go to the Navigation tab and uncheck the Replace Command Prompt with Windows
PowerShell option.
- Click Apply for the change to take effect.
Source: Replace Command Prompt With PowerShell On Power User Menu In Windows 10
Additional Source: Show Command Prompt or PowerShell in Win+X Power User Tasks Menu in Windows 10
Additional Source: Microsoft Replaces Command Prompt With PowerShell As Windows 10 Default Shell
edited Apr 21 '17 at 17:22
answered Apr 21 '17 at 16:54
Ramhound
19.5k156085
19.5k156085
13
This only changes the Windows + x menu, not the "Open with" menu when shift + rightclicking an empty spot in Explorer.
– nelson2tm
Apr 21 '17 at 17:12
1
no Ramhound this doesn't work. you ONLY change what shows up in WinX menu on right click on start button, not doing a rightclick inside Windows/File Explorer
– magicandre1981
Nov 3 '17 at 15:13
add a comment |
13
This only changes the Windows + x menu, not the "Open with" menu when shift + rightclicking an empty spot in Explorer.
– nelson2tm
Apr 21 '17 at 17:12
1
no Ramhound this doesn't work. you ONLY change what shows up in WinX menu on right click on start button, not doing a rightclick inside Windows/File Explorer
– magicandre1981
Nov 3 '17 at 15:13
13
13
This only changes the Windows + x menu, not the "Open with" menu when shift + rightclicking an empty spot in Explorer.
– nelson2tm
Apr 21 '17 at 17:12
This only changes the Windows + x menu, not the "Open with" menu when shift + rightclicking an empty spot in Explorer.
– nelson2tm
Apr 21 '17 at 17:12
1
1
no Ramhound this doesn't work. you ONLY change what shows up in WinX menu on right click on start button, not doing a rightclick inside Windows/File Explorer
– magicandre1981
Nov 3 '17 at 15:13
no Ramhound this doesn't work. you ONLY change what shows up in WinX menu on right click on start button, not doing a rightclick inside Windows/File Explorer
– magicandre1981
Nov 3 '17 at 15:13
add a comment |
As a quick alternative to the other answers, you can type cmd
on the address bar of Explorer to open a command prompt cd
'd to the current directory. (If you are more of a keyboard person, you can use the Ctrl + L
shortcut to focus the address bar and then type cmd
.)
This works for powershell
too.
add a comment |
As a quick alternative to the other answers, you can type cmd
on the address bar of Explorer to open a command prompt cd
'd to the current directory. (If you are more of a keyboard person, you can use the Ctrl + L
shortcut to focus the address bar and then type cmd
.)
This works for powershell
too.
add a comment |
As a quick alternative to the other answers, you can type cmd
on the address bar of Explorer to open a command prompt cd
'd to the current directory. (If you are more of a keyboard person, you can use the Ctrl + L
shortcut to focus the address bar and then type cmd
.)
This works for powershell
too.
As a quick alternative to the other answers, you can type cmd
on the address bar of Explorer to open a command prompt cd
'd to the current directory. (If you are more of a keyboard person, you can use the Ctrl + L
shortcut to focus the address bar and then type cmd
.)
This works for powershell
too.
answered Aug 29 '18 at 0:27
Raphael
1413
1413
add a comment |
add a comment |
To hit all of the locations where Windows has changed this, you can use the following registry file after taking ownership of each key in question.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINESOFTWAREClassesDirectorybackgroundshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
"HideBasedOnVelocityId"=-
[HKEY_LOCAL_MACHINESOFTWAREClassesDirectorybackgroundshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
"ShowBasedOnVelocityId"=-
[HKEY_LOCAL_MACHINESOFTWAREClassesDirectoryshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
"HideBasedOnVelocityId"=-
[HKEY_LOCAL_MACHINESOFTWAREClassesDirectoryshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
"ShowBasedOnVelocityId"=-
[HKEY_CLASSES_ROOTDriveshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
"HideBasedOnVelocityId"=-
[HKEY_CLASSES_ROOTDriveshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
"ShowBasedOnVelocityId"=-
I would just take ownership of the [HKCRDirectory]
and [HKCRDrive]
keys recursively and force permission inheritance.
add a comment |
To hit all of the locations where Windows has changed this, you can use the following registry file after taking ownership of each key in question.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINESOFTWAREClassesDirectorybackgroundshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
"HideBasedOnVelocityId"=-
[HKEY_LOCAL_MACHINESOFTWAREClassesDirectorybackgroundshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
"ShowBasedOnVelocityId"=-
[HKEY_LOCAL_MACHINESOFTWAREClassesDirectoryshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
"HideBasedOnVelocityId"=-
[HKEY_LOCAL_MACHINESOFTWAREClassesDirectoryshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
"ShowBasedOnVelocityId"=-
[HKEY_CLASSES_ROOTDriveshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
"HideBasedOnVelocityId"=-
[HKEY_CLASSES_ROOTDriveshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
"ShowBasedOnVelocityId"=-
I would just take ownership of the [HKCRDirectory]
and [HKCRDrive]
keys recursively and force permission inheritance.
add a comment |
To hit all of the locations where Windows has changed this, you can use the following registry file after taking ownership of each key in question.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINESOFTWAREClassesDirectorybackgroundshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
"HideBasedOnVelocityId"=-
[HKEY_LOCAL_MACHINESOFTWAREClassesDirectorybackgroundshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
"ShowBasedOnVelocityId"=-
[HKEY_LOCAL_MACHINESOFTWAREClassesDirectoryshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
"HideBasedOnVelocityId"=-
[HKEY_LOCAL_MACHINESOFTWAREClassesDirectoryshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
"ShowBasedOnVelocityId"=-
[HKEY_CLASSES_ROOTDriveshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
"HideBasedOnVelocityId"=-
[HKEY_CLASSES_ROOTDriveshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
"ShowBasedOnVelocityId"=-
I would just take ownership of the [HKCRDirectory]
and [HKCRDrive]
keys recursively and force permission inheritance.
To hit all of the locations where Windows has changed this, you can use the following registry file after taking ownership of each key in question.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINESOFTWAREClassesDirectorybackgroundshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
"HideBasedOnVelocityId"=-
[HKEY_LOCAL_MACHINESOFTWAREClassesDirectorybackgroundshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
"ShowBasedOnVelocityId"=-
[HKEY_LOCAL_MACHINESOFTWAREClassesDirectoryshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
"HideBasedOnVelocityId"=-
[HKEY_LOCAL_MACHINESOFTWAREClassesDirectoryshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
"ShowBasedOnVelocityId"=-
[HKEY_CLASSES_ROOTDriveshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
"HideBasedOnVelocityId"=-
[HKEY_CLASSES_ROOTDriveshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
"ShowBasedOnVelocityId"=-
I would just take ownership of the [HKCRDirectory]
and [HKCRDrive]
keys recursively and force permission inheritance.
answered Oct 17 '17 at 17:50
palswim
1,71672951
1,71672951
add a comment |
add a comment |
This hides powershell from the Shift-Right Click context menu and makes cmd visible.
Using a simple text editor such as Notepad, save the following code to a file with the .REG extension (e.g. MyImport.reg
). Then double-click the saved file and follow the prompts to import it into the Registry:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOTDirectoryBackgroundshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDirectoryBackgroundshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDirectoryshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDirectoryshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDriveshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDriveshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
Without explaining what this does and how to use it, this is not an answer. Please edit your post to clarify.
– Twisty Impersonator
Dec 20 '18 at 11:35
done!..........
– Riccardo La Marca
Dec 20 '18 at 11:44
1
Better, however see my edit for more of what I was expecting (not all users will know how to import content into the Registry).
– Twisty Impersonator
Dec 20 '18 at 12:33
add a comment |
This hides powershell from the Shift-Right Click context menu and makes cmd visible.
Using a simple text editor such as Notepad, save the following code to a file with the .REG extension (e.g. MyImport.reg
). Then double-click the saved file and follow the prompts to import it into the Registry:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOTDirectoryBackgroundshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDirectoryBackgroundshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDirectoryshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDirectoryshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDriveshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDriveshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
Without explaining what this does and how to use it, this is not an answer. Please edit your post to clarify.
– Twisty Impersonator
Dec 20 '18 at 11:35
done!..........
– Riccardo La Marca
Dec 20 '18 at 11:44
1
Better, however see my edit for more of what I was expecting (not all users will know how to import content into the Registry).
– Twisty Impersonator
Dec 20 '18 at 12:33
add a comment |
This hides powershell from the Shift-Right Click context menu and makes cmd visible.
Using a simple text editor such as Notepad, save the following code to a file with the .REG extension (e.g. MyImport.reg
). Then double-click the saved file and follow the prompts to import it into the Registry:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOTDirectoryBackgroundshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDirectoryBackgroundshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDirectoryshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDirectoryshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDriveshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDriveshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
This hides powershell from the Shift-Right Click context menu and makes cmd visible.
Using a simple text editor such as Notepad, save the following code to a file with the .REG extension (e.g. MyImport.reg
). Then double-click the saved file and follow the prompts to import it into the Registry:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOTDirectoryBackgroundshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDirectoryBackgroundshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDirectoryshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDirectoryshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDriveshellcmd]
"ShowBasedOnVelocityId"=dword:00639bc8
[HKEY_CLASSES_ROOTDriveshellPowershell]
"HideBasedOnVelocityId"=dword:00639bc8
edited Dec 20 '18 at 12:32
Twisty Impersonator
17.8k146495
17.8k146495
answered Dec 20 '18 at 11:03
Riccardo La Marca
44110
44110
Without explaining what this does and how to use it, this is not an answer. Please edit your post to clarify.
– Twisty Impersonator
Dec 20 '18 at 11:35
done!..........
– Riccardo La Marca
Dec 20 '18 at 11:44
1
Better, however see my edit for more of what I was expecting (not all users will know how to import content into the Registry).
– Twisty Impersonator
Dec 20 '18 at 12:33
add a comment |
Without explaining what this does and how to use it, this is not an answer. Please edit your post to clarify.
– Twisty Impersonator
Dec 20 '18 at 11:35
done!..........
– Riccardo La Marca
Dec 20 '18 at 11:44
1
Better, however see my edit for more of what I was expecting (not all users will know how to import content into the Registry).
– Twisty Impersonator
Dec 20 '18 at 12:33
Without explaining what this does and how to use it, this is not an answer. Please edit your post to clarify.
– Twisty Impersonator
Dec 20 '18 at 11:35
Without explaining what this does and how to use it, this is not an answer. Please edit your post to clarify.
– Twisty Impersonator
Dec 20 '18 at 11:35
done!..........
– Riccardo La Marca
Dec 20 '18 at 11:44
done!..........
– Riccardo La Marca
Dec 20 '18 at 11:44
1
1
Better, however see my edit for more of what I was expecting (not all users will know how to import content into the Registry).
– Twisty Impersonator
Dec 20 '18 at 12:33
Better, however see my edit for more of what I was expecting (not all users will know how to import content into the Registry).
– Twisty Impersonator
Dec 20 '18 at 12:33
add a comment |
In Windows 10 this is now included in the taskbar settings.
3
"This only changes the Windows + x menu, not the "Open with" menu when shift + rightclicking an empty spot in Explorer." -nelson2tm
– Matt M.
Apr 10 '18 at 21:18
add a comment |
In Windows 10 this is now included in the taskbar settings.
3
"This only changes the Windows + x menu, not the "Open with" menu when shift + rightclicking an empty spot in Explorer." -nelson2tm
– Matt M.
Apr 10 '18 at 21:18
add a comment |
In Windows 10 this is now included in the taskbar settings.
In Windows 10 this is now included in the taskbar settings.
edited Jul 30 '18 at 18:27
Peter Mortensen
8,336166184
8,336166184
answered Dec 12 '17 at 21:38
George
1075
1075
3
"This only changes the Windows + x menu, not the "Open with" menu when shift + rightclicking an empty spot in Explorer." -nelson2tm
– Matt M.
Apr 10 '18 at 21:18
add a comment |
3
"This only changes the Windows + x menu, not the "Open with" menu when shift + rightclicking an empty spot in Explorer." -nelson2tm
– Matt M.
Apr 10 '18 at 21:18
3
3
"This only changes the Windows + x menu, not the "Open with" menu when shift + rightclicking an empty spot in Explorer." -nelson2tm
– Matt M.
Apr 10 '18 at 21:18
"This only changes the Windows + x menu, not the "Open with" menu when shift + rightclicking an empty spot in Explorer." -nelson2tm
– Matt M.
Apr 10 '18 at 21:18
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1201988%2fhow-do-i-change-open-with-powershell-to-open-with-command-prompt-when-shift%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown