You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am sure this issue is with PowerShell Editor Services itself and does not reproduce in a standalone PowerShell instance, and is not an issue with my editor.
I have verified that I am using the latest version of PowerShell Editor Services.
I ran into this issue when my VSCode debugger broke after an VSCode update. After some troubleshooting I discovered that the issue originates from PowerShellEditorServices. When starting Editor services, the console hangs on a never ending blinking cursor.
PowerShell Version
Name Value---- -----PSVersion 7.4.7PSEdition CoreGitCommitId 7.4.7OS Microsoft Windows 10.0.26100Platform Win32NTPSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}PSRemotingProtocolVersion 2.3SerializationVersion 1.1.0.1WSManStackVersion 3.0
Editor Version
VSCode 1.96.0, but also a "normal" terminal
PowerShell Editor Services Version
Unknown, cannot fetch information from $pseditor.ModuleType Version PreRelease Name ExportedCommands---------- ------- ---------- ---- ----------------Manifest 7.0.0.0 Microsoft.PowerShell.Management {Add-Content, Clear-Content, Clear-Item, Clear-ItemProp…Binary 4.2.0 PowerShellEditorServices Start-EditorServicesScript 2.3.6 PSReadLine {Get-PSReadLineKeyHandler, Get-PSReadLineOption, Remove…
Prerequisites
Summary
I ran into this issue when my VSCode debugger broke after an VSCode update. After some troubleshooting I discovered that the issue originates from PowerShellEditorServices. When starting Editor services, the console hangs on a never ending blinking cursor.
PowerShell Version
Editor Version
VSCode 1.96.0, but also a "normal" terminal
PowerShell Editor Services Version
Steps to Reproduce
Import-Module "C:\Users{username}.vscode\ms-vscode.powershell-2025.0.0\modules\PowerShellEditorServices\PowerShellEditorServices.psd1"
start-EditorServices
Visuals
No response
Logs
No response
The text was updated successfully, but these errors were encountered: