How to enable "Open PowerShell Here" context menu in Windows 10

open_powershell_here.md

After checking multiple tutorials I had to take pieces from each of the following to get this to work on my Win10 system:

• https://www.howtogeek.com/165268/how-to-add-open-powershell-here-to-the-context-menu-in-windows/
• https://www.tenforums.com/tutorials/60175-open-powershell-window-here-context-menu-add-windows-10-a.html

Basically it uses the steps from the first article, but under the background path from the second article. Neither article on its own worked for me.

Steps:

1. Open regedit and go to path HKEY_CLASSES_ROOT\Directory\background\shell.

2. Create new key powershellmenu.

3. Change the Default value of the powershellmenu key to Open in PowerShell. (or whatever)

4. Create new key command under powershellmenu.

5. Change the Default value of the command key to:

   C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe -NoExit -Command Set-Location -LiteralPath '%L'

6. Right-click on powershellmenu key and select Permissions, then set permissions to Full control for the Administrators group. (or whatever group/user)

Then try right-clicking in some folder and it should work.

Change %L to %V. That's how I got it to work.

Thanks for this. But I also had to change %L to %V for it to work, so you may want to update the instructions.

Thank you so much. Also, I wonder how could we insert PowerShell icon left on it? It looks great when the programs have their icon. Thank you.

Thank you so much. Also, I wonder how could we insert PowerShell icon left on it? It looks great when the programs have their icon. Thank you.

Right-click on powershellmenu key and select New > String Value, rename it to Icon and change the value to C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe

also had to change %L to %V to get it running, cheers for the nice instructions though!

Change %L to %V and thank you so much.

I had to change the data in command (default) to
PowerShell -windowstyle hidden -Command "Start-Process cmd -ArgumentList '/s,/k,pushd,%V && start PowerShell && exit' -Verb RunAs"
if chocolatey is installed a lazy sysadmin could also simply run:
choco install powershellhere

Thanks bro, it really helped me out!

@jtcmedia Thank you!

A helpful powershell script (pillaged from superuser) to accomplish the same thing:

'Directory',
'Directory\Background',
'Drive' | ForEach-Object {
  $Path = "Registry::HKEY_CLASSES_ROOT\$_\shell\PowerShellHere";
  New-Item -Path $Path -Name 'command' -Force | Out-Null;
  Set-ItemProperty -Path "$Path\command" -Name '(default)' -Value 'PowerShell -NoExit -NoLogo -Command Set-Location "%V"';
  Set-ItemProperty -Path $Path -Name '(default)' -Value 'PowerShell';
  Set-ItemProperty -Path $Path -Name 'Icon' -Value "${Env:WinDir}\System32\WindowsPowerShell\v1.0\powershell.exe,0";
}

(remember to run as admin)

@CiaranWelsh

Hey there, tried that still can't see it added in context menu. Weird. Do you know how to undo the changes of that script? I'd like to start again in a VM (which I only realized should be where I test stuff like this first...) Sadly I forgot to backup regedit before this script... I'd really appreciate it

Great thanks, if anyone needs detailed steps to add-remove powershell here, you can check here also
How to Add or Remove "Open PowerShell Here" to context menu
But I really like Powershell script, provided by CiarenWalsh
Thanks

use this as the command value this is work powershell.exe -noexit -command Set-Location -literalPath '%V'

I followed the instructions above and the powershell appears in right click menu but unfortunately this error message appear when I click on it.
any help ?

Follow this steps again, if any error come the. Reply i will help you.
https://w3code.tech/blog/open-powershell-here/

powershell.exe -noexit -command Set-Location -literalPath '%V'

Which windows version are you using now?

…

On Fri, Jul 8, 2022, 5:56 PM Ahmed-Ibrahim-Elsayed ***@***.***> wrote: ***@***.**** commented on this gist. ------------------------------ I followed the instructions above and the powershell appears in right click menu but unfortunately this error message appear when I click on it. any help ?[](url [image: Screenshot 2022-07-08 142437] <https://user-images.githubusercontent.com/107076909/177991845-1bbab035-b868-4f94-aaec-86a8310da2cb.png> ) — Reply to this email directly, view it on GitHub <https://gist.github.com/f3045266aa9e3441211ab55f9db70c2b#gistcomment-4225450>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUMLPHK5OVVF3O4OZYDKMKTVTAM73ANCNFSM4IJIG2RA> . You are receiving this because you commented.Message ID: ***@***.***>

I want to edit the default value of the command of powershell from registry, but I am getting "error cannot edit". See attached.

A helpful powershell script (pillaged from superuser) to accomplish the same thing:

'Directory',
'Directory\Background',
'Drive' | ForEach-Object {
  $Path = "Registry::HKEY_CLASSES_ROOT\$_\shell\PowerShellHere";
  New-Item -Path $Path -Name 'command' -Force | Out-Null;
  Set-ItemProperty -Path "$Path\command" -Name '(default)' -Value 'PowerShell -NoExit -NoLogo -Command Set-Location "%V"';
  Set-ItemProperty -Path $Path -Name '(default)' -Value 'PowerShell';
  Set-ItemProperty -Path $Path -Name 'Icon' -Value "${Env:WinDir}\System32\WindowsPowerShell\v1.0\powershell.exe,0";
}

(remember to run as admin)

This is great, but it's opening PowerShell 5 instead of the new PowerShell 7, can anyone guide me on what to change in the reg key so it opens ProgramFiles\PowerShell\7\pwsh.exe instead of System32\WindowsPowerShell\v1.0\powershell.exe? The only path I found in the instructions above is for the icon.

A helpful powershell script (pillaged from superuser) to accomplish the same thing:

'Directory',
'Directory\Background',
'Drive' | ForEach-Object {
  $Path = "Registry::HKEY_CLASSES_ROOT\$_\shell\PowerShellHere";
  New-Item -Path $Path -Name 'command' -Force | Out-Null;
  Set-ItemProperty -Path "$Path\command" -Name '(default)' -Value 'PowerShell -NoExit -NoLogo -Command Set-Location "%V"';
  Set-ItemProperty -Path $Path -Name '(default)' -Value 'PowerShell';
  Set-ItemProperty -Path $Path -Name 'Icon' -Value "${Env:WinDir}\System32\WindowsPowerShell\v1.0\powershell.exe,0";
}

(remember to run as admin)

This is great, but it's opening PowerShell 5 instead of the new PowerShell 7, can anyone guide me on what to change in the reg key so it opens ProgramFiles\PowerShell\7\pwsh.exe instead of System32\WindowsPowerShell\v1.0\powershell.exe? The only path I found in the instructions above is for the icon.

I'm currently building a solution to this very thing. I'll try to remember to share when I'm done. It's crazy how much inaccurate information is out there on this topic lol

Just tested and the following script is working flawlessly for setting up right-click and SHIFT + right-click menus on both directories and attached storage devices for PowerShell 7:

#!/usr/bin/env pwsh
#------------------------------------------------------------------------------
#
# [ regedit-open-ps-here.ps1 ]
#
# Description:
#
#    A PowerShell script that will loop over the following registry entries:
#
#    HKEY_CLASSES_ROOT\Directory\ (right-click menu on directories)
#    HKEY_CLASSES_ROOT\Directory\Background (SHIFT + right-click menu on directories)
#    HKEY_CLASSES_ROOT\Drive (right-click menu on attached storage devices)
#
#    ... and create new items that add an option to "Open PowerShell 7 Here"
#
#    NOTE: This script must be run as "Administrator" (because we're editing
#    the Windows Registry)
#
#    NOTE: This script sets up a right-click menu option for PowerShell 7, not
#    the older built-in version of PowerShell!
#
# Reference:
#
#    # Github Gist by davecan (and related comments)
#    http://bit.ly/3GYmlbO
#
#    # My comment on the above-referenced Github Gist
#    http://bit.ly/3H3zu3n
#
#    # How to Check If a PowerShell Script Is Run As Administrator
#    http://bit.ly/3R8PRAq
#
#------------------------------------------------------------------------------

Write-Host "Checking for elevated permissions..."

if (-NOT ([Security.Principal.WindowsPrincipal] [Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole] "Administrator")) {
	
    Write-Warning "Insufficient permissions to run this script."
	Write-Host "Open the PowerShell console as an administrator and run this script again."
	
    Break

} else {
	Write-Host "Success: Code is running as administrator." -ForegroundColor Green
    Write-Host "Beginning edits to the Windows Registry ..."
    
    'Directory',
    'Directory\Background',
    'Drive' | ForEach-Object {
      $Path = "Registry::HKEY_CLASSES_ROOT\$_\shell\PowerShellMenu";
      New-Item -Path $Path -Name 'command' -Force | Out-Null;
      Set-ItemProperty -Path "$Path\command" -Name '(default)' -Value '"C:\Program Files\PowerShell\7\pwsh.exe" -NoExit -Command Set-Location -LiteralPath "%V"';
      Set-ItemProperty -Path $Path -Name '(default)' -Value 'Open PowerShell 7 Here';
      Set-ItemProperty -Path $Path -Name 'Icon' -Value "C:\Program Files\PowerShell\7\pwsh.exe,0";
    }
    
    Write-Host "Operations complete"
}

@FCalleja - I hope this helps ;-)

A helpful powershell script (pillaged from superuser) to accomplish the same thing:

'Directory',
'Directory\Background',
'Drive' | ForEach-Object {
  $Path = "Registry::HKEY_CLASSES_ROOT\$_\shell\PowerShellHere";
  New-Item -Path $Path -Name 'command' -Force | Out-Null;
  Set-ItemProperty -Path "$Path\command" -Name '(default)' -Value 'PowerShell -NoExit -NoLogo -Command Set-Location "%V"';
  Set-ItemProperty -Path $Path -Name '(default)' -Value 'PowerShell';
  Set-ItemProperty -Path $Path -Name 'Icon' -Value "${Env:WinDir}\System32\WindowsPowerShell\v1.0\powershell.exe,0";
}

(remember to run as admin)

This is great, but it's opening PowerShell 5 instead of the new PowerShell 7, can anyone guide me on what to change in the reg key so it opens ProgramFiles\PowerShell\7\pwsh.exe instead of System32\WindowsPowerShell\v1.0\powershell.exe? The only path I found in the instructions above is for the icon.

Use pwsh instead of ${Env:WinDir}\System32\WindowsPowerShell\v1.0\powershell.exe and Powershell 7 will be launched instead. Works for me

Mine also worked with '%V'.

shift + right-click on folder works

@davecan You saved me man
I did create in the past this key, but it didn't work and I pretty much gave up(thanks microsoft)
but my mistake was that I created this key under /shell/ and not /Background/shell

Thanks man

I followed this.
https://www.youtube.com/watch?v=RzNiD4WQQ1M

solved my issue

I found this page via Google. This is one of the first search results.
So... I wanted to start PS as administrator instead. I tried for an hour and ended up with this:

PowerShell -Command "Start-Process powershell -Verb runAs -ArgumentList '-NoExit', '-Command', 'Set-Location -LiteralPath \"%V\"'"

Here's a registry file for everyone. It adds the context entry everywhere. It adds the icon as well.
(Originally from WinaeroTweaker - but I didn't like that powershell was running "inside" CMD.exe)

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Directory\shell\OpenElevatedPS]
@="Open PowerShell here as administrator"
"Icon"="powershell.exe"
"HasLUAShield"=""

[HKEY_CLASSES_ROOT\Directory\shell\OpenElevatedPS\command]
@="PowerShell -Command \"Start-Process powershell -Verb runAs -ArgumentList '-NoExit', '-Command', 'Set-Location -LiteralPath \\\"%V\\\"'\""

[HKEY_CLASSES_ROOT\Directory\Background\shell\OpenElevatedPS]
@="Open PowerShell here as administrator"
"Icon"="powershell.exe"
"HasLUAShield"=""

[HKEY_CLASSES_ROOT\Directory\Background\shell\OpenElevatedPS\command]
@="PowerShell -Command \"Start-Process powershell -Verb runAs -ArgumentList '-NoExit', '-Command', 'Set-Location -LiteralPath \\\"%V\\\"'\""

[HKEY_CLASSES_ROOT\Drive\shell\OpenElevatedPS]
@="Open PowerShell here as administrator"
"Icon"="powershell.exe"
"HasLUAShield"=""

[HKEY_CLASSES_ROOT\Drive\shell\OpenElevatedPS\command]
@="PowerShell -Command \"Start-Process powershell -Verb runAs -ArgumentList '-NoExit', '-Command', 'Set-Location -LiteralPath \\\"%V\\\"'\""

[HKEY_CLASSES_ROOT\LibraryFolder\background\shell\OpenElevatedPS]
@="Open PowerShell here as administrator"
"Icon"="powershell.exe"
"HasLUAShield"=""

[HKEY_CLASSES_ROOT\LibraryFolder\background\shell\OpenElevatedPS\command]
@="PowerShell -Command \"Start-Process powershell -Verb runAs -ArgumentList '-NoExit', '-Command', 'Set-Location -LiteralPath \\\"%V\\\"'\""

And here is the version using Windows Terminal:

PowerShell -Command "Start-Process -Verb RunAs wt.exe \"powershell.exe -NoExit -Command Set-Location -LiteralPath '%V'\""

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Directory\shell\OpenElevatedPS]
@="Open PowerShell here as administrator"
"Icon"="powershell.exe"
"HasLUAShield"=""

[HKEY_CLASSES_ROOT\Directory\shell\OpenElevatedPS\command]
@="PowerShell -Command \"Start-Process -Verb RunAs wt.exe \\\"powershell.exe -NoExit -Command Set-Location -LiteralPath '%V'\\\"\""

[HKEY_CLASSES_ROOT\Directory\Background\shell\OpenElevatedPS]
@="Open PowerShell here as administrator"
"Icon"="powershell.exe"
"HasLUAShield"=""

[HKEY_CLASSES_ROOT\Directory\Background\shell\OpenElevatedPS\command]
@="PowerShell -Command \"Start-Process -Verb RunAs wt.exe \\\"powershell.exe -NoExit -Command Set-Location -LiteralPath '%V'\\\"\""

[HKEY_CLASSES_ROOT\Drive\shell\OpenElevatedPS]
@="Open PowerShell here as administrator"
"Icon"="powershell.exe"
"HasLUAShield"=""

[HKEY_CLASSES_ROOT\Drive\shell\OpenElevatedPS\command]
@="PowerShell -Command \"Start-Process -Verb RunAs wt.exe \\\"powershell.exe -NoExit -Command Set-Location -LiteralPath '%V'\\\"\""

[HKEY_CLASSES_ROOT\LibraryFolder\background\shell\OpenElevatedPS]
@="Open PowerShell here as administrator"
"Icon"="powershell.exe"
"HasLUAShield"=""

[HKEY_CLASSES_ROOT\LibraryFolder\background\shell\OpenElevatedPS\command]
@="PowerShell -Command \"Start-Process -Verb RunAs wt.exe \\\"powershell.exe -NoExit -Command Set-Location -LiteralPath '%V'\\\"\""

i changed it to "%v" and it does not work.

Don't know what to tell you. Update your software, maybe? Or did you forget the "/", slashs?
I'm using windows 10 pro. Newest everything, afaik. Shouldn't have any effect on this, though.

ok i do have to update then