KB3003 - Resetting PowerShell Pro Tools (VS Code)

KB3003 - Resetting PowerShell Pro Tools (VS Code)

Problem


PowerShell Pro Tools (for VS Code) is not behaving as expected. For example, pressing the 'Show Form Designer' button does not successfully launch PSScriptPad (only the splash screen is shown). 

Solution

This solution assumes that you have VS Code installed with the Microsoft PowerShell extension and a licensed PowerShell Pro Tools extension

Reset the PowerShell Pro Tools app folder per below

1. Exit any instances of VS Code that you might have open

2. Delete the PowerShellProTools folder from your user profile directory.

      Windows Users
      For PowerShell Pro Tools version 2023.09 and above and delete: C:\Users\[username]\.vscode\extensions\ironmansoftware.powershellprotools-202X.XX.0
      For PowerShell Pro Tools version prior to 2023.09, delete the same folder as above but also delete: C:\users\[username]\PowerShellProTools

      Linux/Mac Users
      Delete: /home/username/.vscode/extensions/ironmansoftware.powershellprotools-202X.XX.0/
     
If you have any issues with deleting the folder because the files/directories are locked, try restarting your computer.

3. After step 2 is complete launch VS code and make sure you open a PowerShell .ps1 file

4. You should see in the same status bar that the PowerShell Pro Tools extension is not ready yet


5. After a few seconds, it should turn to green indicating it is ready.



6. You should now be able to proceed with using the features of the extension.


(figure shows the PowerShell Pro Tools toolbar in VS Code)


(figure shows the PowerShell Pro Tools sidebar menu in VS Code)

    • Related Articles

    • KB3010 - PowerShell Pro Tools for VS Code "command not found"

      Scope This article only applies to PowerShell Pro Tools for VS Code on the Windows operating system. If you are using PowerShell Pro Tools for VS Code for Mac or Linux then this article does not apply Problem The PowerShell Pro Tools extension for VS ...

    • KB3002 - PowerShell Pro Tools for VS Code (2002) stopped working

      Scope This is a legacy article which only applies to PowerShell Pro Tools for VS Code version 2022.7.2 and below If your PowerShell Pro Tools for VS Code is at 2022.8.0 or higher then this article does not apply Problem PowerShell Pro Tools extension ...

    • KB3009 - PowerShell Pro Tools for VS Code "failed to connect"

      Scope This article only applies to PowerShell Pro Tools for VS Code on the Windows operating system. If you are using PowerShell Pro Tools for VS Code for Mac or Linux then this article does not apply Problem The PowerShell Pro Tools extension for VS ...

    • KB3007 - Resetting PowerShell Pro Tools (Visual Studio)

      Scope This article applies to Visual Studio 2017, 2019 and 2022 (Community, Professional and Enterprise) with the PowerShell Tools for Visual Studio [2002] extension. Problem The PowerShell Tools for Visual Studio extension will not load or A ...

    • KB3012 - PowerShell Pro Tools feature not working

      Scope This article only applies to features of PowerShell Pro Tools for VS Code. Problem A feature (e.g. Refactoring) doesn't work even though you expect it to. Symptoms No action occurs when invoking one of the PowerShell Pro Tools features from the ...