PingCastle Pro Upgrade Guide
PingCastle Pro 4.1 requires ASP.NET Core 10.0. Versions up to 3.5 use ASP.NET Core 8.0. Before you upgrade from 3.5 or earlier, install the ASP.NET Core 10.0 Hosting Bundle on the server. See Software requirements.
Before proceeding to the upgrade
Version check
You can check the existing version using the About link at the bottom of each page.

Database backup
Netwrix highly recommends backing up the data before proceeding with an upgrade.
PingCastle Pro stores the data in the database. No data exists outside the database.
Software requirements
Before performing the upgrade, you must meet the software requirements for the new version. The following table lists the requirements for each version.
| Upgrade path | Requirement |
|---|---|
| Any 2.x version | All versions have the same requirements. |
| 2.x to 3.2 | Upgrade ASP.NET from 3.1 to 6.0. |
| 3.2 to 3.5 | Upgrade ASP.NET from 6.0 to 8.0. |
| 3.5 to 4.1 | Upgrade ASP.NET from 8.0 to 10.0. Install the ASP.NET Core 10.0 Hosting Bundle before you replace the files. |
Performing the upgrade
If PingCastle Pro connects to the database with a limited-privilege account (read, modify, and delete only), contact Netwrix Support for the SQL script to apply before you replace the files. PingCastle Pro can't create or alter tables without database-owner permissions. If the database user is the database owner, you don't need the script. PingCastle Pro creates or modifies tables automatically the first time it runs after the upgrade.
To upgrade PingCastle Pro:
-
Download the ZIP file for the new version.
-
On the server where PingCastle Pro is installed, open a command prompt as an administrator and stop IIS:
iisreset /stop -
Extract the ZIP file over the installation directory, overwriting the existing files.
-
Start IIS:
iisreset /start
The MSI installer doesn't support upgrades. Use the ZIP file.
Post-upgrade verification
After the upgrade completes:
- Confirm the application starts successfully.
- Check the About link at the bottom of the page to confirm the version number matches the version you installed.
- Confirm your settings in
appsettings.Production.jsonare unchanged, since the upgrade doesn't remove or reset this file. - Confirm the database is intact. Upgrading, like uninstalling, doesn't remove the database.