PowerShell Studio 2019: Released!

We are happy to announce the release of PowerShell Studio 2019! This major release is included as part of the regular update cycle for our subscribers.


PowerShell Studio 2019


New Features

The 2019 release includes new features, some changes, and improvements.


Script Security Center

This release introduces the new Script Security Center tool, which replaces the previous Execution Policy Manager.

Script Security Center


The new Script Security Center tool allows you to change the execution policy for all versions of Windows PowerShell and PowerShell Core. In addition, you can change the trust policy of the Windows Script Host.


Debugging – Watch Panel

We updated the Watch Panel to highlight value changes when stepping in the debugger:



The values highlighted in red indicate a change from the previous state.


Coloring for Parentheses and Curly Braces

You can now change the coloring of parentheses and curly braces in the editor:

Braces and Parenthesis Coloring


To change the coloring, use the Editor Font Color Settings dialog (Options->Editor->Font and Color…):

Edit Font and Color Dialog


Formatting Curly Braces

After auto-inserting curly braces, PowerShell Studio will now move the closing brace to a new line when the user presses Enter:

Auto Insert Braces Before NewlineAuto Insert Braces After Newline


File Template Filtering

You can now filter user templates and preset templates:

File Template Preset - User Filter


User templates are now marked with a User tag and preset templates are marked with a Preset tag:

User and Preset Tags


Database Browser – SQL Server Compact

The Database Browser now supports SQL Server Compact database connections:

SQL Server Compact Support



Updated Tools Tab

We updated the ribbon’s Tools tab to include other SAPIEN tools:

Updated Tools Tab

You now have the option to select tools with elevation.


Search PSGallery for Module

Have you ever opened a script created by someone else to find an unknown cmdlet, and you had no idea what module it belonged to? Now there is an easy solution—when you find an unknown cmdlet you can search the PowerShell Gallery for the module using the editor’s context-menu:

Search PSGallery


The Search PSGallery for Module command will open PowerShell ModuleManager and search the gallery for the cmdlet’s module:

PowerShell ModuleManager Search


PowerShell ModuleManager will then allow you to install the missing module.

Important: This feature requires PowerShell ModuleManager to be installed. You can download a trial version here.


Tip Remember to update the module’s cache in PowerShell Studio after installing a new module:

Refresh Cache



Other Changes

This release also includes the following changes and improvements.


User Application Folder

This release removes the year from the user application data folder so that custom templates will be retained across versions.

C:\Users\Username\AppData\Roaming\SAPIEN\PowerShell Studio


User Cache Folder

We removed the year from the user cache folder, and we use a version number instead. This change minimizes duplicate cache files whenever there is a major release.


Go To Declaration

We updated the Go To Declaration command keyboard shortcut to F12.

Go To Declaration


Performance Improvement

We continue with our commitment to improve performance. This build improves the load speeds of large PowerShell script files and projects.




Please continue providing your feedback. Many of the new features included in the service builds are suggestions from users like you. Submit your suggestions or feature requests on the Wish List and Feature Requests forum or the new Feature Requests page.

You can view the complete service build log here.