PowerShell / PowerShell/vscode-powershell

Unregister-EditorCommand doesn't remove command from list

Open
#5,277 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-psEditor Issue-Bug
Dominant language
TypeScript
Stars
1.9k
Forks
547
PR merge metrics
No merged PRs in 30d

Description

Prerequisites
  • I have written a descriptive issue title.
  • I have searched all open and closed issues to ensure it has not already been reported.
  • I have read the troubleshooting guide.
  • I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
  • I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
  • If this is a security issue, I have read the security issue reporting guidance.
Summary

When calling Unregister-EditorCommand or $psEditor.UnregisterCommand(), the command remains in the Additional Commands list, leading to duplicate entries when my profile module is re-loaded. When trying to invoke the command afterwards, an exception is thrown, so the command is being unregistered, but it remains on the list.

PowerShell Version
Name                           Value
----                           -----
PSVersion                      7.5.3
PSEdition                      Core
GitCommitId                    7.5.3
OS                             Microsoft Windows 10.0.22631
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Name             : Visual Studio Code Host
Version          : 2025.3.1
InstanceId       : db3b07b7-3b3b-40bb-8b54-c57ae4548a21
UI               : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture   : en-US
CurrentUICulture : en-US
PrivateData      : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled  : True
IsRunspacePushed : False
Runspace         : System.Management.Automation.Runspaces.LocalRunspace
Visual Studio Code Version
1.104.1
0f0d87fa9e96c856c5212fc86db137ac0d783365
x64
Extension Version
ironmansoftware.powershellprotools@2024.12.0
martinfliegner.dark-powershell-theme@1.0.0
ms-vscode.powershell@2025.3.1
tylerleonhardt.vscode-inline-values-powershell@0.0.7
xkoloblicin.powershell-ise-dark@1.0.1

(note: PowerShell Pro Tools is disabled in my current workspace)
Steps to Reproduce
  1. Register any simple command, like `Register-EditorCommand -Name MyCommand -DisplayName "Test Command" -ScriptBlock {$psEditor.Window.ShowInformationMessage("I came from Register-EditorCommand.")}
  2. View registered commands with Shift+Alt+S or "PowerShell: Show Additional Commands from PowerShell Modules" to ensure the command is registered
  3. Invoke the command to verify it works
  4. Unregister the command with Unregister-EditorCommand -Name MyCommand or $psEditor.UnregisterCommand("MyCommand")
  5. View registered commands again to find if the command remains
Visuals
Duplicate Registered Commands
Logs

For whatever reason, even setting "powershell.developer.editorServicesLogLevel": "Trace" and "powershell.trace.server": "verbose", the PowerShell output log looks about the same as when it's set to "Information", despite the Integrated Terminal showing trace information (e.g. "DEBUG: [Trace] Logging started", etc.). Nothing showed up about registering commands or loading modules.

The only thing I could find after unregistering the command and executing it from the list is from the Extension Host log:

2025-09-18 15:29:28.824 [error] Error: Internal Error - System.Collections.Generic.KeyNotFoundException: Editor command not found: 'ConvertComment3Center'
   at Microsoft.PowerShell.EditorServices.Services.Extension.ExtensionService.InvokeCommandAsync(String commandName, EditorContext editorContext, CancellationToken cancellationToken) in C:\__w\1\s\src\PowerShellEditorServices\Services\Extension\ExtensionService.cs:line 146
   at Microsoft.PowerShell.EditorServices.Services.Extension.InvokeExtensionCommandHandler.Handle(InvokeExtensionCommandParams request, CancellationToken cancellationToken) in C:\__w\1\s\src\PowerShellEditorServices\Services\Extension\Handlers\InvokeExtensionCommandHandler.cs:line 27
   at OmniSharp.Extensions.LanguageServer.Server.Pipelines.SemanticTokensDeltaPipeline`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
   at OmniSharp.Extensions.LanguageServer.Server.Pipelines.ResolveCommandPipeline`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
   at MediatR.Pipeline.RequestPreProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
   at MediatR.Pipeline.RequestPostProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
   at MediatR.Pipeline.RequestExceptionProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
   at MediatR.Pipeline.RequestExceptionProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
   at MediatR.Pipeline.RequestExceptionActionProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
   at MediatR.Pipeline.RequestExceptionActionProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
   at OmniSharp.Extensions.JsonRpc.RequestRouterBase`1.<RouteRequest>g__InnerRoute|7_0(IServiceScopeFactory serviceScopeFactory, Request request, TDescriptor descriptor, Object params, CancellationToken token, ILogger logger)
   at OmniSharp.Extensions.JsonRpc.RequestRouterBase`1.RouteRequest(IRequestDescriptor`1 descriptors, Request request, CancellationToken token)
   at OmniSharp.Extensions.JsonRpc.DefaultRequestInvoker.<>c__DisplayClass10_0.<<RouteRequest>b__5>d.MoveNext()
    at handleResponse (c:\Users\e.dunhjo\.vscode\extensions\ms-vscode.powershell-2025.3.1\dist\extension.js:30293:40)
    at handleMessage (c:\Users\e.dunhjo\.vscode\extensions\ms-vscode.powershell-2025.3.1\dist\extension.js:30103:11)
    at processMessageQueue (c:\Users\e.dunhjo\.vscode\extensions\ms-vscode.powershell-2025.3.1\dist\extension.js:30118:13)
    at Immediate.<anonymous> (c:\Users\e.dunhjo\.vscode\extensions\ms-vscode.powershell-2025.3.1\dist\extension.js:30094:11)
    at processImmediate (node:internal/timers:485:21)
    at process.callbackTrampoline (node:internal/async_hooks:130:17) PowerShell.ShowAdditionalCommands {"value":"ms-vscode.powershell","_lower":"ms-vscode.powershell"}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the register, list, unregister, and list sequence, then trace the command-list handling from the ExtensionService.cs failure at line 146 and InvokeExtensionCommandHandler.cs at line 27. Done means an unregistered command no longer appears in Additional Commands and invoking it produces no stale-entry exception.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell, typescript
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.