PowerShell module that enables "Open here" shortcuts functionality for Windows PowerShell, PowerShell Core, Windows Terminal, Bash and CMD.
OpenHere is a PowerShell module for installation of shell shortcuts into the context menu (the right mouse button click or the menu key) for Microsoft Windows.
The shortcuts will open desired shell in the current location, e.g. for Windows PowerShell $PWD will be set to the location from which the shortcut was invoked.
- Shortcut installation/removal for Windows PowerShell, Windows Terminal, CMD
- Open here with non-elevated privileges shortcut.
- Open here with elevated privileges shortcut.
- Default setting for easy-to-use.
- Fully customizable shortcut names.
- Shortcut availability on directory, drive, directory background, user's desktop.
- Rollback of all shell modifications.
- Works offline.
- Well documented
To install the OpenHere module, just type following command into your PowerShell session with elevated privileges.
Install-Module -Name OpenHere
Import-Module -Name OpenHereNow, you can use the module as you wish. For shortcut installation:
Set-OpenHereShortcut -ShortcutType:WindowsPowerShellFor other shortcuts just type:
Set-OpenHereShortcut -ShortcutType:WindowsTerminal
Set-OpenHereShortcut -ShortcutType:CMD
Set-OpenHereShortcut -ShortcutType:PowerShellCoreFor a custom shortcut & command names, fill parameters accordingly:
Set-OpenHereShortcut -ShortcutType:WindowsPowerShell -RootName 'Old PowerShell' -OpenHere 'I''m lazy' -OpenHereAsAdmin 'I''m lazy admin'or the equivalent with the escape backtick:
Set-OpenHereShortcut -ShortcutType:WindowsPowerShell`
-RootName 'Old PowerShell' `
-OpenHere 'I''m lazy' `
-OpenHereAsAdmin 'I''m lazy adminTo remove the shortcut with any settings, just call:
Remove-OpenHereShortcut -ShortcutType:WindowsTerminalFor more details about setting/removing process, type:
Set-OpenHereShortcut -ShortcutType:WindowsTerminal -Verbose
Remove-OpenHereShortcut -ShortcutType:WindowsTerminal -Verboserespectively.
For more examples, type:
Get-Help Set-OpenHereShortcut -ExamplesWindows Terminal doesn't responds to RunAs request from the context menu. This problem is a limitation of the UWP platform. A workaround has been implemented to support Windows Terminal shortcut with elevated privileges. A similar workaround had to be implemented for non-elevated Open here Windows Terminal shortcut to support scenarios when requests are invoked from RMB clicks on a directory or a drive letter.
Yes, see the section Planned features.
By default, OpenHere module uses its own icons in shell context menus. If the -UseExeIcon switch is used when shortcut is created, the default icons are not generated. These default icons are written in %LOCALAPPDATA%\OpenHere\[ShellType]. Every shell has its own Icon.ico file in the corresponding subfolder. You can customize icons by overriding these Icon.ico files.
Yes, just run Set-OpenHereShortcut with a new configuration.
No, the shortcut names supports Unicode and this is only limitation as I'm aware of.
OpenHere module at PowerShell Gallery
Get-Icon
CMD icon
PowerShell icon
PowerShell Core icon
WSLBash icon
PNG to icon online converter
PNG to base64 online converter


