Nothing new, but it makes sense since this implementation preserves backwards compatibility. and the most critical part is proper use of ' necessary to specify that first instance of PowerShell should not parse quoted contents at all and pass arguments literally while preserving set of ' for final PowerShell to be able to ignore any rogue & ( %V variable is expanded by explorer.exe prior to any execution, so we don't have to worry about it).note, \ escaping double-quotes dictated by reg file syntax as line should be seen as where is what actually ends up in key value data.%Vpasses initial path for new command prompt (when file(s)/folder(s) is selected it will pass the location of item that was right-clicked on, if nothing is selected it is equal to working directory).a stands for ArgumentList that passes noexit option that prevents new PS window from closing upon start and Set-Location option is self-explanatory.v flag specifies Verb set to RunAs triggers elevation via UAC prompt.To summarize all research and improving Andrew Richards registry tweak, I got rid off annoying sub-menus by utilizing single runas verb for legacy command prompt and implementing elevated entry for PowerShell using Start-Process from non-elevated instance called by /C powershell \"start powershell -a '-noexit -command Set-Location ''%V''' -v RunAs\""
Ensure OS Entries are on the Extended Menu (Shift-Right Click) "MUIVerb"="PowerShell -noexit -command Set-Location '%V'" "ExtendedSubCommandsKey"="Directory\\ContextMenus\\MenuPowerShell" "MUIVerb"="Command Prompt /s /k pushd \"%V\"" "ExtendedSubCommandsKey"="Directory\\ContextMenus\\MenuCmd" reg file (create a new txt file, paste the content and rename the file extension to reg): Windows Registry Editor Version 5.00 Or apply Andrew Richards tweak to have both shown (cmd and PowerShell, also with entry to have elevate (running as admin) version),īy importing his.
Bring up command prompt windows 10 full#
Open regedit.exe, go to HKEY_CLASSES_ROOT\Directory\shell\cmd, 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.
0 kommentar(er)
