How can I launch powershell.exe with the “default” colours from the PowerShell shortcut?

Question

I\'m attached to the nice blue colour of the PowerShell window when you launch it from one of the pre-installed shortcuts. However, if you manually launch powershell.exe, yo

Answer 1

Based on @rex-hardin excellent answer, I improved the regedit content here to add an icon, and use the PowerShell native arguments to start in the right path.

The context-menu is enabled when right-clicking on a directory background, and when right-clicking directly on a directory icon.

Of course, we also run a console with blue background exactly like the default one.

1. Add ".LNK" extension to %PATHEXT% environment variable

This allows system to execute files with .lnk extension (hidden extension for shortcuts)

2. Copy the default PowerShell shortcut link to system32 as powershell file

This allows the powershell command to launch our shortcut from system32 folder (which is in %PATH%)

Use explorer (copy+rename) or the command-line below:

Copy-Item "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Windows PowerShell\Windows PowerShell.lnk" "C:\Windows\System32\powershell.lnk"

3. Add code below to a powershell_here.reg file and execute it.

powershell_here.reg

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\directory\background\shell\PowerShell]
@="PowerShell Here"
"Icon"="%SystemRoot%\\system32\\WindowsPowerShell\\v1.0\\powershell.exe"

[HKEY_CLASSES_ROOT\directory\background\shell\PowerShell\command]
@="cmd.exe /c start powershell -NoExit -NoProfile -Command Set-Location -LiteralPath '%V'"

[HKEY_CLASSES_ROOT\directory\shell\PowerShell]
@="PowerShell here"
"Icon"="%SystemRoot%\\system32\\WindowsPowerShell\\v1.0\\powershell.exe"

[HKEY_CLASSES_ROOT\directory\shell\PowerShell\command]
@="cmd.exe /c start powershell -NoExit -NoProfile -Command Set-Location -LiteralPath '%L'"

Answer 2

Click the system menu (PowerShell icon in the top-left of the window) and click Defaults. You can change the default colors here and it will be respected by the PowerShell Prompt Here command.

From: https://superuser.com/a/523017/109736

Answer 3

Launch powershell with default blue and white colors in current folder from Explore or Total Commander or Double Commander on Windows 7 Pro 64-bit:

1. Star Menu -> search PowerShell link -> right click on it -> Properties -> Shortcut tab (the one that opens by default) -> modify Start in: -> %CD%

2. Create a batch file named ps.bat somewhere in a folder that is on the system PATH (if you do not have such a folder just make one, let's say C:\run\cli and add it to the PATH system environment variable). This batch file has to contain the following command:

   start "" "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Windows PowerShell\Windows PowerShell.lnk"

That's it. Now just type ps in the Explorer's path bar where the current folder is shown or in the command line box of Total Commander or Double Commander, etc...

On Windows 10, there is no need to modify the PowerShell shortcut from Start Menu and the ps.bat file from above may contain just the following command:

start %SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe

Answer 4

Here's a really easy way:

1. Add .LNK to your PATHEXT variable.

Start -> run "sysdm.cpl" -> advanced -> Environment Variables

Scroll Down through system variables, double click PATHEXT

Add .LNK; as depicted below:

2 Copy the default "Windows Powershell.lnk"

Copy-Item "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Windows PowerShell\Windows PowerShell.lnk" "C:\Windows\System32\powershell.lnk"

3. Typing "powershell" from a run prompt will now bring up the default console color/configuration.

You can further customize the .lnk in C:\Windows\System32 to your liking.

Please note that this will only work because you have added the .lnk to the list of acceptable extensions AND c:\windows\system32 is the first item in the search path (PATH system variable) by default.

This will not customize the console if it is launched via cmd.exe.

4. To make this work from the "Run Powershell Here" context menu, save this as a .reg file and import it:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Directory\shell\PowerShellHere\command]
@="C:\\WINDOWS\\system32\\cmd.exe /c start powershell -NoExit \"cd '%1';(get-host).ui.rawui.windowtitle = 'Oompa Loompa'\""

[HKEY_CLASSES_ROOT\Directory\shell\PowerShellHere\command]
@="C:\\WINDOWS\\system32\\cmd.exe /c start powershell -NoExit \"cd '%1';(get-host).ui.rawui.windowtitle = 'Oompa Loompa'\""

I am using cmd.exe to call "start" which will launch the powershell.lnk and pass the current working directory as an argument. Doesn't seem to work from the address bar yet. I should have gone home 45mins ago, but your problem was fun to solve! :)

Bonus Points: You can thread the commands sent to Powershell. So, if you are looking to modify the Powershell console's title attribute:

\"cd '%1';(get-host).ui.rawui.windowtitle = 'Oompa Loompa'"

Simply add a semicolon between commands.

Happy shelling

Answer 5

Edit your profile script (pointed to by $profile) and set the desired colors yourself:

# set regular console colors
[console]::backgroundcolor = "darkmagenta"
[console]::foregroundcolor = "darkyellow"

# set special colors

$p = $host.privatedata

$p.ErrorForegroundColor    = "Red"
$p.ErrorBackgroundColor    = "Black"
$p.WarningForegroundColor  = "Yellow"
$p.WarningBackgroundColor  = "Black"
$p.DebugForegroundColor    = "Yellow"
$p.DebugBackgroundColor    = "Black"
$p.VerboseForegroundColor  = "Yellow"
$p.VerboseBackgroundColor  = "Black"
$p.ProgressForegroundColor = "Yellow"
$p.ProgressBackgroundColor = "DarkCyan"

# clear screen
clear-host

Answer 6

1. Run regedit command to open registry editor
2. Track down HKEY_CURRENT_USER > CONSOLE and Backup entire folder by exporting just in case
3. Delete the folder

Restart your Powershell, the color scheme must have reset to defaults.

Note: If you have any other settings related to PowerShell (or Command Prompt, Git Bash etc) which you might want to keep, please further explore Console Folder to delete appropriate keys