
Description
System Details
System Details Output
### VSCode version: 1.33.1 51b0b28134d51361cf996d2f0a1c698247aeabd8 x64
### VSCode extensions:
eamodio.gitlens@9.6.3
mauve.terraform@1.3.9
ms-azuretools.vscode-azureterraform@0.2.3
ms-vscode.azure-account@0.8.2
ms-vscode.azurecli@0.4.5
ms-vscode.powershell@1.12.1
### PSES version:
### PowerShell version:
Name Value
---- -----
PSVersion 5.1.15063.1689
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.15063.1689
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
Issue Description
The integrated PS editor fails to start. In the Code window, buttom right, is the message:
Starting PowerShell...
If I try and run a script via F5, or Debug > Start Debugging, the error is:
Cannot debug or run a PowerShell script until the PowerShell session has started. Wait for the PowerShell session to finish starting and try again.
The script is Get-Process
which works fine in the PS terminal.
I have waiting 2+ hours, uninstalled Code and deleted %UserProfile%.vscode, reinstalled.
Expected Behaviour
It starts in a timely manner.
Tell me the full path and source of what file it is looking for on D:.
Actual Behaviour
The logs seem to suggest Code is looking for something in D:. My PC does not have a D:, which, I guess, is what is making it throw its toys out the pram:
2019-04-29 14:36:25.534 [ERROR] tid:10 in 'OnListenTaskCompleted' C:\PowerShellEditorServices\src\PowerShellEditorServices.Protocol\MessageProtocol\ProtocolEndpoint.cs: line 391
ProtocolEndpoint message loop terminated due to unhandled exception:
System.AggregateException: One or more errors occurred. ---> System.Management.Automation.DriveNotFoundException: Cannot find drive. A drive with the name 'd' does not exist.
at System.Management.Automation.SessionStateInternal.GetDrive(String name, Boolean automount)
at System.Management.Automation.SessionStateInternal.GetDrive(String name, Boolean automount)
at System.Management.Automation.SessionStateInternal.SetLocation(String path, CmdletProviderContext context)
at Microsoft.PowerShell.EditorServices.PowerShellContext.<SetWorkingDirectory>d__65.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
Code / PS did work on this machine. I do not have a $profile
set on this PC.