Ed Callahan comments

Results 6 comments of


                                            Ed Callahan

PowerShell 5.1 (x64) fails to start in VS Code 1.101.0 with PSES v3.0+ — no logs, EditorServicesHost.exe not launched

I haven't dug into it as deeply as @mmunchandersen, but I am having the same issue. Powershell extension is just not starting, unable to run powershell 5 scripts. I'm on...

PowerShell 5.1 (x64) fails to start in VS Code 1.101.0 with PSES v3.0+ — no logs, EditorServicesHost.exe not launched

> can you try the version of VS code that was broken, but with shell integration explicitly disabled? I added: `"terminal.integrated.shellIntegration.enabled": false` to my settings.json and restarted vscode, but same...

PowerShell 5.1 (x64) fails to start in VS Code 1.101.0 with PSES v3.0+ — no logs, EditorServicesHost.exe not launched

> Try to comment setting `powershell.powerShellDefaultVersion`. It worked for me on several computers. That is already set in my settings.json `"powershell.powerShellDefaultVersion": "Windows PowerShell (x64)",`

PowerShell 5.1 (x64) fails to start in VS Code 1.101.0 with PSES v3.0+ — no logs, EditorServicesHost.exe not launched

>(https://github.com/EdCallahan) The value of `Windows PowerShell (x64)` does not work (dont know why) and causes the PS extension never start. @scriptingstudio Oh, I see what you meant. I commented that...

PowerShell 5.1 (x64) fails to start in VS Code 1.101.0 with PSES v3.0+ — no logs, EditorServicesHost.exe not launched

> I know that this setting says it "has no effect on Windows" _but_ I can reproduce the hang when it's set to its default (true) and it stops hanging...

Millions of remoteIPMoProxy_* powershell logs under temp

Same here, my disk filled up from use of Write-EventLog. I've found that `Import-Module Microsoft.PowerShell.Management -UseWindowsPowershell` will create a remoteIpMoProxy_MicrosoftPowerShellManagement folder in my temp directory that is never cleaned up....