Skip to content

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

Closed
johlju opened this issue Aug 13, 2017 · 2 comments
Closed

Fix c:\Windows\Sysnative powerShellExePath when using 64-bit VS Code #993

johlju opened this issue Aug 13, 2017 · 2 comments
Labels
Issue-Bug A bug to squash.
Milestone

Comments

@johlju
Copy link

johlju commented Aug 13, 2017

System Details

  • Operating system name and version:
  • VS Code version: 1.15.0 x64
  • PowerShell extension version:
  • Output from $PSVersionTable:
1.15.0 
8b95971d8cccd3afd86b35d4a0e098c189294ff2

[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

Name                           Value
----                           -----
PSVersion                      5.1.16257.1000
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.16257.1000
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Copy / paste the following commands into the PowerShell Integrated Console, and paste the output here:

code -v
$pseditor.EditorServicesVersion
code --list-extensions --show-versions
$PSVersionTable

Issue Description

PowerShell Integration Console fail to start. There is no such folder.

image

Attached Logs

This is the only thing in the log (no need to zip it).

powershell.exe cannot be found or is not accessible at path C:\WINDOWS\Sysnative\WindowsPowerShell\v1.0\powershell.exe
PowerShell could not be started, click 'Show Logs' for more details.
@daviwil
Copy link
Contributor

daviwil commented Aug 14, 2017

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.

@daviwil daviwil changed the title PowerShell Integrated Console trying to start powershell.exe from 'Sysnative' folder Fix powerShellExePath when using 64-bit VS Code Aug 14, 2017
@daviwil daviwil added this to the August 2017 milestone Aug 14, 2017
@johlju
Copy link
Author

johlju commented Aug 15, 2017

I had two settings in the User settings. Removed them both and PowerShell Integration Console starts again.
I didn't even thought of looking there, could you add that to the log output maybe?

    "terminal.integrated.shell.windows": "C:\\WINDOWS\\Sysnative\\WindowsPowerShell\\v1.0\\powershell.exe",
    "powershell.powerShellExePath": "C:\\WINDOWS\\Sysnative\\WindowsPowerShell\\v1.0\\powershell.exe"

@daviwil daviwil modified the milestones: August 2017, 1.4.2 Aug 24, 2017
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 daviwil changed the title Fix powerShellExePath when using 64-bit VS Code Fix c:\Windows\Sysnative powerShellExePath when using 64-bit VS Code Sep 5, 2017
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
@daviwil daviwil closed this as completed in f2aa2a2 Sep 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug A bug to squash.
Projects
None yet
Development

No branches or pull requests

2 participants