1

With PowerShell Core 6.0.0 released I'd like to start using it instead of Windows 10's default PowerShell.

I currently use Cmder for this, which is based upon ConEmu. There are already two PowerShell tasks and I assume that I can update them to point to my local install of PowerShell Core (in C:\Program Files\PowerShell\6.0.0).

I've tried updating the Task parameters for Powershell::Powershell to the following:

/dir "C:\Program Files\PowerShell\6.0.0\" /icon "%CMDER_ROOT%\icons\cmder_blue.ico"

Then I update the commands to this:

"%ProgramFiles%\PowerShell\6.0.0\PowerShell.exe" -ExecutionPolicy Bypass -NoLogo -NoProfile -NoExit -Command "Invoke-Expression '. ''%ConEmuDir%\..\profile.ps1'''" -new_console:d:"%USERPROFILE%" -new_console:d:D:\git

However, it's breaking with the following error:

'c:\program' is not recognized as an internal or external command, operable program or batch file.

How would I setup Cmder/ConEmu to call the PowerShell Core version of PowerShell instead of the default installation?

  • Please don't edit the answer into your question. Super User is a question and answer site and answers should be separate from questions. – DavidPostill Jan 12 '18 at 22:36
2

I currently use Cmder for this, which is based upon ConEmu. There are already two PowerShell tasks and I assume that I can update them to point to my local install of PowerShell Core (in C:\Program Files\PowerShell\6.0.0).

You are using the wrong executable.

The binary name for PowerShell Core has been changed from powershell(.exe) to pwsh(.exe). This change provides a deterministic way for users to run PowerShell Core on machines to support side-by-side Windows PowerShell and PowerShell Core installations. pwsh is also much shorter and easier to type.

What's New in PowerShell Core 6.0

Additionally

You can launch PowerShell via the Start Menu or $env:ProgramFiles\PowerShell\pwsh.exe

Installing PowerShell Core on Windows

  • That's fine. As a regular user on Super User I'll defer to you. I just know that on SO it would be closed for "This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers.", especially since you had noted that via a comment on the question first. – James Skemp Jan 12 '18 at 19:44
5

Use

*pwsh -ExecutionPolicy Bypass -NoLogo -NoProfile -NoExit -Command "Invoke-Expression '. ''%ConEmuDir%\..\profile.ps1'''"

enter image description here

  • Thanks the screen shot helps a ton. – user212241 Jan 17 at 4:38

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.