-
Notifications
You must be signed in to change notification settings - Fork 510
Fix c:\Windows\Sysnative powerShellExePath when using 64-bit VS Code #993
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hey Johan, what's the value of "powershell.powerShellExePath" in your user settings? Try clearing it out if it's set to the c:\WINDOWS\Sysnative path. |
I had two settings in the User settings. Removed them both and PowerShell Integration Console starts again.
|
daviwil
added a commit
to daviwil/vscode-powershell
that referenced
this issue
Sep 5, 2017
This change introduces a new module that contains all the logic for determining the current OS platform, process architecture and OS architecture for use in determining available Windows PowerShell EXE paths. This module helps resolve problems that were introduced by the new 64-bit distribution of Visual Studio Code. Fixes PowerShell#1008 Fixes PowerShell#1007 Fixes PowerShell#1006 Fixes PowerShell#993
daviwil
added a commit
that referenced
this issue
Sep 5, 2017
This change introduces a new module that contains all the logic for determining the current OS platform, process architecture and OS architecture for use in determining available Windows PowerShell EXE paths. This module helps resolve problems that were introduced by the new 64-bit distribution of Visual Studio Code. Fixes #1008 Fixes #1007 Fixes #1006 Fixes #993
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System Details
$PSVersionTable
:Issue Description
PowerShell Integration Console fail to start. There is no such folder.
Attached Logs
This is the only thing in the log (no need to zip it).
The text was updated successfully, but these errors were encountered: