PA Storage Monitor Release Candidate

This page is where you can find our very latest release. Versions that make it to this page are considered solid and candidates for production release, but we're still adding features and/or the build hasn't received enough feedback yet. If we implement a feature or fix for you, we will typically send you to this page to try it out. We fully support these builds as though they were production releases. Many of our largest customers stay on the Preview build so they get features and fixes sooner.

Click here if you are looking for the current Production Release.

Download the Release Candidate

Current Release

Version 9.7.0.96 [9 December 2025] is currently in testing.

[.23] * Increasing Strict-Transport-Security maximum age to 1 year
[.23] * Stricter failed login lockout counts
[.29] * Fixed Powershell v2 Execute Scripts that stopped working
[.51] * Faster Inventory Database responses, which helps speed up server status reports
[.51] * MIB files are parsed on the Central Server, and synced in parsed form to Satellites and Fail Over
[.51] * Fixed copying custom properties to computers to not return an error when there wasn't one
[.51] * Improved server selector in a few places
[.51] * Stable inventory props that are stable don't have to be fresh (no stale check)
[.51] * Added help buttons to all monitors and actions
[.51] * Fix to handle path matching with wild cards on very long strings
[.76] * Fixed an extremely rare crash involving scanning long paths
[.76] * A better experience testing database connection strings
[.76] * Fixed issue of Console not getting monitor status updates if the Central Server restarts while the Console is running
[.88] * Improved the server type probe which affects Automatic Configuration
[.96] * Fix for File & Directory Change monitor when working with IPv6 addresses

Updates / Upgrades

PA Storage Monitor can be upgraded by simply installing the latest version on top of your existing installation. Your settings and databases will be upgraded as needed.

You might need to reset the PA Storage Monitor service's Run As account (from Settings or the Windows Services applet), but other than that no further configuration changes will be needed.