PRTG Release Notes:
Stable Channel

A new version of the multi-platform probe is now available! With this release the multi-platform probe has undergone a major re-architecture to deliver you a better overall user experience. Key improvements of the new multi-platform probe architecture are enhanced performance and reliability, allowing you to deploy more sensors per probe while reducing memory consumption and overall resource usage. For example, previously, you were required to have 2 CPU cores to support 200 sensors. With the new architecture, the multi-platform probe can support up to 400 sensors with the same setup. Please see the manual, Multi-Platform Probe for PRTG , for the updated system requirements.

In addition to these user-facing enhancements, we made the probe easier to maintain and improve, enabling us to streamline the development of new features, maintenance, and bug fixes.

For detailed release notes about this release, see our Knowledge Base article: What are the release notes for the Multi-Platform Probe?.

We introduce the new NATS Server Overview sensor with this PRTG release that monitors a NATS Server by connecting as a NATS Client in order to retrieve monitoring data. In case of Jetstream enabled NATS servers, the NATS Overview sensor will display the additional channels Jetstream Memory Used (%), Jetstream Storage Used (%), Jetstream Memory Reserved (%) and Jetstream Storage Reserved (%).

We introduce the new SNMP CPU Usage sensor with this PRTG version that is the successor sensor for the SNMP CPU Load sensor. This sensor type monitors the system load via the Simple Network Management Protocol (SNMP). This sensor type was rewritten to be compatible with the Multi-Platform Probe.

With this PRTG version, the SNMP UPS Status sensor left its BETA status and is now fully supported. This sensor type monitors the status of an uninterruptible power supply (UPS) via Simple Network Management Protocol (SNMP). We introduced this sensor type as experimental sensor with PRTG version 24.4.102.1351.

With this PRTG version, the SSH Load Average v2 sensor left its BETA status and is now fully supported. This sensor monitors the load average of a Linux/Unix system using Secure Shell (SSH). We introduced this sensor type as experimental sensor with PRTG version 24.4.102.1351.

With this PRTG version, the SSH Meminfo v2 sensor left its BETA status and is now fully supported. This sensor monitors the memory usage of a Linux/Unix system using Secure Shell (SSH). We introduced this sensor type as experimental sensor with PRTG version 24.4.102.1351.

With this PRTG version, the SSH Remote Ping v2 sensor left its BETA status and is now fully supported. This sensor remotely monitors the connectivity between a system running Linux/macOS and another device using Internet Control Message Protocol (ICMP) echo requests ("ping") and Secure Shell (SSH). We introduced this sensor type as experimental sensor with PRTG version 24.4.102.1351.

With this PRTG version we introduce the new SNMP Linux Load Average v2 sensor that is the successor sensor for SNMP Linux Load Average. This sensor type was rewritten to be compatible with the Multi-Platform Probe. The SNMP Linux Load Average sensor monitors the system load average of a Linux/Unix system via the Simple Network Management Protocol (SNMP).

With this PRTG version we introduce the new SNMP Linux Meminfo v2 sensor that is the successor sensor for SNMP Linux Meminfo sensor. This sensor type was rewritten to be compatible with the Multi-Platform Probe.

Please note that the channel Available Memory (%) has been renamed to Free Phyiscal (%) and vice versa to better match its purpose, for example, Available Memory (%) should be the memory that is available for applications if the operating system was also reclaiming buffers/cache space, whereas Free Phyical (%) is the value which is not in use currently.

We introduce the new SNMP Memory v2 sensor with this PRTG version that is the successor sensor of the SNMP Memory sensor. This sensor type monitors the memory usage of a system via the Simple Network Management Protocol (SNMP). This sensor type was rewritten to be compatible with the Multi-Platform Probe.

We hardened PRTG in relation to CVE-2024-12833 by applying further sanitization to names objects.

We hardened PRTG against a possible XSS (Cross-Site Scripting) vulnerability. We considered this vulnerability as medium with a CVSS score of 6.5 and the vectors as follows: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N.

We improved our handling for licenses to accept more formats when you have to use the Activation Data file in order to activate PRTG on an offline system. This file will be sent as .dat or .txt file and it is needed during the manual activation process.

We improved the behavior of PRTG when you have activated a PRTG Subscription or Paessler PRTG Enterprise Monitor license that has expired or is going to expire. You will now receive a growl message that displays when your PRTG Subscription license has expired or will expire. In case of license expiration, the License Status will show the activation data is no longer valid. Additionally, PRTG requests the value from validuntil in the activation data as well when you activated it with a Paessler PRTG Enterprise Monitor license first on an online system and later switch to an offline environment.

We added support for flash memory classification in the SNMP Disk Free v2 sensor. Previously, disks reported as flash memory in the SNMP Disk Free v2 sensor were not listed during sensor creation.

We replaced our old PRTG gauge logo with a new one that was updated in colour and style throughout PRTG. The logo has also changed in the new UI in various locations, for example, in the tab as the favicon display or as the Monitoring icon.

Various other minor fixes and improvements, updated user manual.

We updated the German, Spanish, French, Russian, Chinese, Portuguese and Dutch language files.

Microsoft announced that Exchange Online will permanently remove support for Basic authentication with Client Submission (SMTP AUTH) in September 2025. To further maintain support for SMTP settings and email delivery in PRTG, please see the following Knowledge Base article: How can I use SMTP with the deprecated Microsoft Exchange authorization?

We fixed an issue that occurred when your active directory server was not accessible and you wanted to add a user group to your PRTG. You would receive a Bad Request pop-up instead of a proper error message. PRTG will now display Active Directory Domain not found under Active Directory Group in the User Group Settings in these cases.

We fixed an issue for the endpoint getdesktoptoken.htm, that returned the message unauthorized when you had Single Sign-on configured and created an API key for PRTG Multiboard. The issue occurred when you were logged in with the relevant Single Sign-on user to whom the API key was assigned. PRTG will now return the according API token and only display the error message when the user has no assigned token.

We fixed an issue for returned errors on certain not accessible pages in PRTG that previously reported a not found error. PRTG will now return a HTTP 403 forbidden path error in those cases.

We fixed an issue where log messages with the text Wrong period in cache where wrongly logged as exceptions when you changed a graph period under Graph Settings in the User Interface setup.

We fixed an issue for notification templates where settings for Microsoft Teams and Slack notifications were cleared in certain cases. The issue occurred when you selected notification templates via multi-edit menu to add tags. After you have added tags for your notification templates and saved the changes, the set checkboxes under Custom Content in the Microsoft Teams and Slack notification templates were cleared.

PRTG will now list the actual System ID in the Core.log and in the PRTG Administration Tool to help solve license activation issues in case of incorrect returned System IDs. When you wanted to perform an offline activation of PRTG with a Paessler PRTG Enterprise license, for example, and the System ID was incorrect, you would get the error message The local system ID does not match the system ID returned by the activation service. This information is not available on PRTG remote probe systems.

We fixed an issue for the HPE 3PAR Drive Enclosure sensor that reported the error message N/A could not be converted to integer in certain cases. The issue occurred when the drive controller reported an invalid temperature or no temperature at all.

The HPE ProLiant Memory Controller sensor now supports additional lookups for systems using Adaptive Double Device Data Correction (ADDDC). Previously, the sensor reported an error undefined lookup value (16) in such cases.

We fixed an issue for the SNMP Disk Free v2 sensor that displayed the settings Type and Size for the monitored disks in the sensor Settings. Those columns should only be available during sensor creation. The SNMP Disk Free v2 sensor will now only display the columns Type and Size during sensor creation in the result columns.

We fixed an issue for SNMP v3 error messages that did not reflect that the error was due to a timeout. In case of an SNMP timeout, the error message will now display Timeout Error: The sensor failed to communicate with the target system.

We fixed an issue in the sFlow sensor to support 32bit numbers in the SourceID field. In previous PRTG versions, this packet format was not accepted by PRTG. This change allows you to monitor now specific devices, for example Neptune (NPT) routers.

We currently face an issue with SMTP notification delivery when you have set your Notification Delivery settings to Use direct delivery with the built-in email server (default). This issue occurrs with updating to PRTG version 25.2.106.1114 where email notifications are sent several times instead of only once. Additionally, you will notice an error growl message: Your PRTG core server is currently unable to send email notifications. Check your configuration..

With updating to PRTG version 25.2.106.1114, SNMP sensors monitoring devices via SNMP v3 may report a timeout error (SNMP error -2003) in certain rare cases. A probe restart only helps temporarily. In case you received a preliminary fix for this issue, we recommend that you update your PRTG only when we deliver a fixed library in the upcoming versions.

There currently is an issue that occurrs in certain rare cases after sensor migration of SSH sensors. The SSH Inodes Free v2 sensor, for example, ran into a timeout under certain circumstances when you updated to PRTG version 25.2.106.1114 in which we introduced the migration process for this sensor type. In the Result of Sensor log, that is created when you enable Store Result for this sensor, you could also observe a connection failure and timeout error. We are investigating the problem with the highest priority.

You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:

Stable 25.2.108.1358

• sha256_exe 5DD6D0FEC1071FC5F90CF05E81965BB01CC47726CF63FCA37421DE60E927405C
 
• sha256_zip 144D4E61D3E095550C22542919F0C5859CFDF27683351F03FA1429C53ABC1AD5

With this PRTG version we deprecate the SFTP Secure File Transfer Protocol sensor. Existing sensors will continue to run but you will not be able to add this sensor anew when you update to this PRTG version. Currently there is no successor sensor planned for this sensor type. You will receive an according To Do ticket in PRTG about this sensor deprecation.

With this PRTG version we discontinue the SSH INodes Free sensor. We already announced the deprecation of this sensor type with PRTG version 25.2.106.1114. Running SSH INodes Free sensors on your PRTG installation will stop working when you update to this PRTG version. Migrated sensor types from SSH INodes Free to the successor v2 sensor version are not affected. You cannot add the SSH INodes Free sensor anymore when you update to this PRTG version. Please use the successor sensor SSH INodes Free v2 in this case which left its BETA status with PRTG version 25.1.104.1946.

With this PRTG version we announce the deprecation of the following sensor types: SSH Meminfo, SSH Load Average and SSH Remote Ping sensor. Existing sensor types will continue to run when you update to this PRTG version, however, you cannot add those sensors anymore as new. PRTG will also create an according To Do ticket. For more information on sensor deprecation, please see our Knowledge Base articles: What sensors are deprecated and what are their successors or alternatives? and What do deprecation and discontinuation in the context of sensors mean?

With this PRTG version we announce the sensor migration that will happen with PRTG 25.x.110 for the following sensor types: SSH Meminfo, SSH Load Average and SSH Remote Ping sensor. PRTG will sent an according TO DO ticket with all relevant information. The sensors will be migrated to their successor types SSH Meminfo v2, SSH Load Average v2 and SSH Remote Ping v2 sensor. Those successor sensors left their BETA status with this PRTG release.

• We added the option to use session-based authentication with the REST Custom v2 (BETA) sensor in order to monitor devices that cannot be integrated into PRTG yet. You will find additional settings Session Based Authentication in the device settings under Credentials for REST API where you can define an Authentication Method.
  
  Important:: Please note that existing REST Custom v2 sensors will go into down or warning state with the error message Creation of rest_custom_v2_sensor failed: The setting "authentication_section.authentication_group.login_path" was not available when you update to this PRTG version. To solve this issue, please pause and resume the affected sensors to make them work again. We will provide a fix for this issue with the upcoming PRTG versions.
• We improved the logging for the REST Custom v2 sensor concerning passwords, placeholders and API keys that you can configure under Credentials for REST API in the device settings. For example, if you run an auto-discovery with device template for this sensor type, no sensitive data will be logged in the CoreAutoDiscovery logfile or the data is masked and therefore unreadable.

You can try out the experimental SNMP CPU Usage sensor (BETA) which is the successor of the SNMP CPU Load sensor. This sensor type monitors the system load via the Simple Network Management Protocol (SNMP). Please note that you need to enable the PRTG BETA feature under Experimental Features in the PRTG Setupfirst in order to use this sensor.

• We implemented a new endpoint /experimental/devices/{id}/move in our PRTG APIv2 that allows you to relocate objects within the monitoring structure via POST request. In this new endpoint, you can enter the ID of the device that you want to move in an additional field. In the request body, you need to add the parent and the position where the device should be placed.
• We implemented a new GET endpoint under api/v2/experimental/license in the Systems section of Swagger UI. This endpoint is only accessible if you are logged in as a PRTG administrator. You can receive information about the current PRTG license with the fields start_date, end_date, maintenance_end_date via GET request.
• We fixed an issue for GET endpoints in PRTG API v2 that returned a 200 OK response with a default set of fields when you, for example, had a typing error in the inheritance parameter. The API will now return a 400 Bad Request in this case with the message the request could not be processed.
• We added a new filter operator Ancestor ID for experimental list endpoints in PRTG API v2. The filter returns all objects that have the specified ID as an ancestor in their object hierarchy. Affected experimental endpoints are, for example, /experimental/channels and /experimental/sensors.
• We fixed an issue where the pagination headers for all experimental endpoints related to the wrong endpoint. In most of the cases, the headers pointed to endpoints that were not set as experimental. For example, /api/v2/experimental/devices related to /api/v2/devices instead. The pagination headers will now point to the same endpoint as the requested URL.
• We implemented a new GET endpoint /experimental/objects that allows you to receive probes, groups, devices, sensors and channels from a single endpoint.

We improved the performance of the PRTG application server used on larger installations and reduced memory consumption on all installations.

We added an extra card that displays the current version of PRTG that you have installed. The card shows the title Your version of PRTG. You can also see previous and additional versions with the link View version history / release notes of previous versions.

To make the Notification Triggers more visible, we moved the Notification Triggers section from access via button to an extra tab. You will also have the possibility to access the Notification Triggers via context menu.

We fixed an issue that occurred when you clicked the split view buttons on the Monitoring page from left to right or vice versa and when the developer tools were opened in the browser at the same time. You would receive an unknown error growl message in these cases and when you used Chrome as browser for PRTG.

We fixed an issue where the link back from the new UI to classic web interface resulted in an error page when you navigated to the History or Logs tab of the local probe. PRTG would return an error page There was a problem... when you clicked on Open Classic UI in the relevant tabs.

This version comes with a new setting that allows administrators to customize the time interval at which ITOps Board sends notifications.

Additionally, the following issues were fixed in this release of ITOps Board:

• Dialog boxes that allow users to edit table columns do not work well with screen readers. These tables have been updated for improved accessibility.
• When you attempt to open the Alerts tab on a board, the tab does not load.
• When the alert count for a board changes, the interface does not automatically refresh and show an updated alert count.

We hardened PRTG against open redirect vulnerabilities where URL forwarding to external sites was possible.

We adapted our device templates so that they also contain the new v2 sensor types. Former deprecated sensors that have an according v2 sensor type as successor were removed from the device templates. For example, when you execute an auto-discovery with device template for Server DNS, the DNS v2 sensor will be added afterwards.

The VMware Datastore (SOAP) sensor now includes limits for the channel Free Space by default. The Lower Warning Limit (%) is set to 10 and Lower Error Limit (%) is set to 5. These thresholds are set by default when you create this sensor type new or when you did not have set custom limits before in a previous PRTG version for this sensor. When you have set custom limits before, those settings will be kept when you update to this PRTG version.

The Script v2 sensor now supports native executables. This means that the sensor can now run arbitrary executable files (Linux) or *.exe (Windows). The native executable file should be stored on the probe system. On Linux systems, executables require execute permissions to run. To run Python scripts, this sensor requires that Python 3 is within PATH.

We improved the error message text in the sensor status so you will receive a proper error message instead of a generic one when certain exceptions occur.

We improved our license handling and error messages on the License Information page in PRTG. For example, when you want to change your license and the key is not valid or wrong, you will receive an according error message Activation successful - using previous license key. PRTG will then use the previous key as stated in the message instead.

We improved the wording for sensors that is displayed in the sensor overview popup when you hover over a sensor in the device tree.

Various other minor fixes and improvements, updated user manual.

We updated the German and Spanish language files.

We fixed an issue for geo location information that was displayed in native language for the according country, region or city. The issue occurred because our location service provider updated their API which had impact on the location language. The locations in the Geo Map will be displayed in English again when you update to this PRTG version.

We fixed an issue that occurred with PRTG version 25.1.104.1946 where the application server service stopped running or did not run at all in rare cases, depending on the number of sensors and system resources, for example. As a result, you could not use the new PRTG user interface. You could also observe that the application server was consuming much more memory in these cases.

We fixed an issue that occurred when you have set your SMTP server settings to Continue delivery if session is disconnected by client in order to receive email notifications in certain cases. PRTG would cut the connection to the SMTP server before getting any confirmation in those cases. PRTG will now send a QUIT verb to the SMTP server before cutting the connection.

• We fixed an issue for the HTTP Transaction sensor that occurred in previous PRTG versions where the sensors went into Down state after updating to PRTG 22.2.77.2204 in certain cases. A possible workaround was to set the Monitoring Engine to use the Compatibility engine mode in order to monitor the URL what helped in certain cases. The issue happened because the HTTP request cookie was not transferred for all following requests in a non compatibility mode. In some cases the HTTP Advanced sensor was also affected by reporting that the connection was refused and it would work again with the Compatibility engine mode.
• We fixed an issue for the HTTP Transaction sensor that occurred when you chose the option Compatibility engine under the option Monitoring Engine section and you set a text value for example ccc in the option Response must not include field in the sensor settings. The sensor then would have displayed a down status with the message URL #1 Warning: RegEx does not match [ccc].

We fixed an issue for LDAP sensors that could not be created via device template in certain cases. The issue occurred when you created a device template for an LDAPS server with accordingly configured sensors before, that is LDAP Specific has to be set to Use LDAP over SSL in the Connection Security. The sensors would be created afterwards but the settings were configured wrongly to use LDAP (Port 389) for unsecure connections.

We fixed an issue for the NetApp SnapMirror v2 sensor that reported the error message The queried field "resnyc_failed_count" is empty in certain cases. The issue occurred, when you monitored a NetApp SnapMirror system that never had a failed resync or update.

We fixed an issue for OPC UA sensors that went into error state in certain cases when you have set the Security Mode in the Credentials for OPC UA of your device settings to None. The issue occurred, because the sensors still used a previously set client certificate although you disabled the Security Mode in the device settings.

We fixed an issue for SNMP sensors that reported the error message SNMP error -2011 and Could not create SNMP session (-1)-2011 in certain cases when you updated to the latest PRTG version 25.1.104.1961. The issue occurred for sensors using SNMP v3 for monitoring as set version.

We prevented a possible access violation that could happen in rare cases when a probe created too many sensors at once. The fix applies for classic remote probes as well as the Multi-Platform Probe. On Windows systems, the error could be displayed as Invalid access to memory location with error code 998.

The WMI Vital System Data v2 Sensor now offers the counter Memory:Cache Bytes when you add a new sensor under the section Vital System Data Readings Accessible Using WMI.

We fixed an issue that occurred when you had Single Sign-on configured in your PRTG and changed the license key to a Paessler PRTG Enterprise Subscription license type. In those cases, the Single Sign-on login would not work anymore and the Single Sign-On Settings under System Administration would be missing additionally after changing the license type.

The configuration file of this version is not downwards compatible with previous PRTG versions.

With this version we announce the deprecation of the SSH INodes Free sensor, that will be migrated to a successor SSH INodes Free v2 sensor when you update to this PRTG version. SSH INodes Free v1 sensors cannot be added anew when you have updated to this PRTG version. For more information about sensor deprecation and discontinuation, please see our Knowledge Base article: What do deprecation and discontinuation in the context of sensors mean?

With this version we deprecate the Python Script Advanced sensor that we already announced with PRTG version 25.1.104.1946. The Python Script Advanced cannot be added anew when you update to this PRTG version, however, existing sensor types continue to run. Please use the successor sensor Script v2 instead. For more information please see our Knowledge Base article: What do deprecation and discontinuation in the context of sensors mean?

Read here for differences and more information about the two sensors: Why should I use the Script v2 sensor?

We also provide information on how to migrate your scripts with this Knowledge Base article: How can I make my Python scripts work with the Script v2 sensor?

You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:

Stable 25.2.106.1114

• sha256_exe CBEB1C5ECD86060B2866E1E6C56844FDA63CECB3EB29A7551DA94DB7066F95A0
 
• sha256_zip ED2E78563E54F187F3E6078DE85D0671B246E393AB154A4B0EBEA59A15659C38

• You can now receive and edit location information with the include parameter set to locationgroup via GET and PATCH request on the devices and group endpoints. To see the location of an object, use the /{id} or list endpoint for a certain object type and make sure to include locationgroup via the include parameter.
• We added the sections /experimental/users/{id} and /experimental/users for GET requests in the api/v2/oas.
• You are now able to create a group via PRTG API v2 and an according POST request on the endpoint /api/v2/experimental/groups/{id}/group and /api/v2/experimental/probes/{id}/group .
• You are now able to edit group settings via PRTG API v2 and an according PATCH request on the endpoint /api/v2/experimental/groups/{id}.
• You can now delete a group or a sensor with a DELETE request in the experimental section /experimental/groups/{id} or /experimental/sensors/{id}. If the request is successful, you will receive a 204 response code.
• We updated the /devices/{id} and /groups/{id} to receive and display information about the status of auto-discoveries. When you execute a GET request on the mentioned endpoints, you will see the additional section about auto-discovery with the fields active, progress and last_autodiscovery, which display whether an auto-discovery is currently running, the progress and when the last auto-discovery ran respectively. Please make sure to set the include parameter first for the section autodiscovery.
• We fixed an issue that occurred when you sent a PATCH request to the /devices/{id} endpoint for the settings group discoverytypegroup and the devicetemplate value was not set. The returned error response code was 400 with the message BAD REQUEST in those cases.
• We fixed an issue for the dbport field in the dbcredentials used for Credentials for Database Management Systems in the device settings. When the default value of that according field was set to 1, for example, the request would fail in the PRTG API v2.

You will now see an indicator bar in your device tree view indicating there is an auto-discovery session running in the device tree. If you have more than one sessions running the indicator bar will display the total number.

We updated the page PRTG Manual: Update from Previous Versions in our user manual.

We fixed an issue for SNMP sensors that ran into error state in certain cases when you used the SNMP v3 setting for SNMP Version and when you updated to PRTG version 25.1.104.1946. The issue occurred when your devices had the same SNMP engine ID, which could happen after cloning virtual machines with preconfigured SNMP settings for SNMP v3. A possible workaround was to use different user names per switch.

Please note that this issue persists in the intermediate PRTG version 25.1.104.1906 that is needed for further PRTG updates. We recommend that you update to this version 25.1.104.1961 soon.

You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:

Stable 25.1.104.1961

• sha256_exe 480637BD026D608FF987BAF3273921C7995934653913EBF42DDD0DA939EFE47A
 
• sha256_zip 6B2ED30C8AF36F2355674BE8A1F2724CBEBD969ACC4937EA353A12F01E3E0D20

Please note that the intermediate version of PRTG that is needed for further software updates contains an issue for SSH sensors and SNMP v3 settings that could occur in certain cases. We recommend that you update to the latest released PRTG version 25.1.104.1961 that fixes the mentioned issues.

We implemented the Audit Log feature with this PRTG version that is enabled when you have an according PRTG subscription license. You will see available settings under Core & Probes - Audit Log settings . Additionally, we updated the Send Syslog Message template in the Notification Templates. In order to meet the requirements for the transparency of security-related data in SIEM systems, this feature enables you to write audit logs to disk. You will find an according Audit Logs folder under C:\ProgramData\Paessler\PRTG Network Monitor\Logs\audit. Depending on your subscription, you might also have the possibility to export audit logs to a third-party system. Please note that this feature is only available if you run PRTG with a subscription license.

The Cisco WLC Access Point Overview sensor left its BETA status and is now fully supported. We introduced this sensor type as experimental sensor with PRTG version 24.3.98.1210. This sensor monitors your access points that are connected to your Cisco Wireless LAN Controller (WLC). In course of this, we also fixed an issue for the Cisco WLC Access Point Overview sensor that reported the error message The returned result from OID...is the wrong type ('Error'). The expected type is 'Integer (32bit)' in certain cases what resulted in access points not being able to be monitored. The issue occurred in cases when the Number of Slots during sensor creation reported more slots then were actually successful for an access point. For example, the SNMP response during sensor scan reported 2 slots, slot 0 did work whereas slot 1 failed. The sensor will now no longer report an error in these cases but show the data of the successful slots instead. Additionally, you can change the number of slots in the Cisco WLC Access Point Overview Specific settings upon request with the lock button.

The PRTG Data Hub sensors, that is PRTG Data Hub Process sensor, PRTG Data Hub Traffic sensor and PRTG Data Hub Rule sensor, left their BETA status and are now fully supported with this PRTG version. We introduced those sensor types as experimental sensors with PRTG version 24.3.100.1361 in order to monitor a PRTG Data Hub instance.

The Port v2 sensor left its BETA status and is now fully supported. We introduced this sensor type as experimental sensor with PRTG version 22.4.80.1553. This sensor combines the features of the Port sensor and Port Range sensor and monitors a network service by connecting to one or more of its TCP/IP ports.

The SSH INodes Free v2 sensor left its BETA status and is now fully supported. We introduced this sensor type as experimental sensor with PRTG version 24.3.100.1361.  This sensor monitors the free index nodes on disks of Linux/Unix and macOS systems via Secure Shell (SSH). 

We improved the usage of lookups created by PRTG that now implement the necessary syntax to reference the schema. This shows you information about the formatting when you work with lookup files in an editor program. For example, when you check the created lookup in the \PRTG Network Monitor\lookups\custom folder with an editor program after you have added an SNMP Library sensor before, you will now see additional information about the XML schema. This change applies only for newly created lookup files. 

You can now define a scale factor as integer or floating-point number for the MQTT Subscribe Custom sensor in the sensor settings during sensor creation. The setting is available in the MQTT Specific settings and can be defined in the Scale Factor setting of a channel when the Channel Unit is set to custom. The default scale value is set to 1 and can be changed depending on whether you want to scale up or down. You can change this setting later after sensor creation in the Edit Channel settings under Scaling Multiplication.

We improved the section in the device Settings for credentials so they are masked for read-only users what was not the case for certain sensor types in previous PRTG versions. When you are logged in with a read-only user, you will now see that, for example, the Credentials for Windows Systems are masked forUser Name and Domain or Computer Name. This change applies for all credentials under Settings. 

We improved the process for adding a sensor on the Multi-Platform Probe that in certain cases will display a progress bar for the sensor scan during sensor creation. For example, if you add the AWS RDS v2 sensor it could happen, that it takes a while until the scan is completed and you will see a progress bar in the pop-up window under the message Working... 

Various other minor fixes and improvements, updated user manual.

We updated the German and Spanish language files.

The PRTG application server will now be installed by default when you install PRTG for the first time with a valid license key. This change applies only for new installations that do not have a trial key license, existing PRTG version updates are not affected. After you have set up a fresh installation of PRTG, you will see the Open new UI button on the login page. Additionally, the PRTG application server service is available and running on your system.

For more information, please see our Knowledge Base article: I want to use the new UI and API v2. What do I need to know?

We fixed an issue that could cause internal nodes to be deleted via API call. Internal nodes required for your PRTG installation can no longer be deleted now via API call. 

You can now delete an object only when you have the according access rights to that object, regardless if you have write or full access to the parent node. Previously, there was a check for the access rights only on the parent node. If you do not have write access to all the objects that you want to delete, you will receive an access denied error for this operation.

We improved the behavior of PRTG auto-update concerning available PRTG versions. 

We fixed an issue where in certain cases an enabled Geo Map could lead to ajax timeout errors or slow performance in the PRTG web interface. You could observe this issue when your PRTG core server was blocked in your firewall for outgoing connections and PRTG would try to reach the geolocation service continuously. In the Core.log you could also read an error log entry GetGeoLocation: failed to read geolocation.

We fixed an issue that occurred in the CoreActivation logfile when you used a trial license key for a PRTG offline activation. The activation was successful, however, the CoreActivation log would show an error unknown license selector passed. The issue was due to our internal license processing and did not have any functional impact.

We fixed an issue for email Notifications that occurred in certain cases in the previous PRTG version where email notifications were not received although they reported the status Status sending Email: OK in the PRTG system information. 

We improved the stability of PRTG local and remote probes that ran into a higher memory consumption in certain cases in the previous PRTG versions. You could observe access violations or exceptions in some cases in the Probe log and that the probe service stopped working due to the high memory consumption. Restarting the probe service only helped temporarily in such cases. 

We fixed an issue for remote probes where in certain cases the content in the Log tab was not rendered and therefore the Log tab was displayed as empty. 

We fixed an issue for reports where the first line of a report saved in .csv file format displayed the first line in unresolved characters and was not readable. The issue occurred when you have set your PRTG language to Russian, Japanese or Chinese and ran a report including data tables to be saved as .csv file. 

You will now be able to log in with your Single-Sign on user account again after you have changed your license key or after server migration. In previous PRTG versions, the user account for a Single-Sign on user was paused after you have transferred to a new license and login was not possible. 

We fixed an issue for the HPE3 PAR Drive Enclosure sensor where the drive controller reported an invalid temperature or no temperature at all in certain cases. The sensor will now ignore drives with missing or invalid temperatures instead of going into an error state.

We fixed an issue for the MQTT Round Trip sensor that was not added to a device when you used this sensor in a device template and the Port configured was not default 1883. For example, when you changed the default Port of a device in the Credentials for MQTT to secure connection Port 8883 and ran Run Auto-Discovery with Template with MQTT Round Trip selected, no sensors would be created afterwards.

We fixed an issue where in some cases changing settings of certain custom sensor types resulted in a PE270 error with the message An error occurred. To resolve this issue, try to pause and resume the sensor or check your settings. In cases where pause and resume did not help, a PRTG core server restart would make those sensors run again. Sensor types affected were, for example, Modbus TCP Custom sensor and MQTT Subscribe Custom sensor.

The option Filter by Message in the WMI Event Log sensor settings under Filter Event Log Entries is now working again as expected. When you disabled the Filter by Message option and saved the settings, the log entries would still only be returned for this filter option

You can now generate a Historic Data report when you click on the arrow button behind the Start button that is displayed in the Historic Data tab for Historic Data Report Settings. In previous PRTG versions, the report could not be created and instead an error message was displayed: PRTG Network Monitor has encountered a problem. Your last request could not be processed properly.

We fixed an issue for the Multi-Platform Probe Connection Settings in the PRTG Setup menu that you could not save anymore in certain cases. For example, when you changed the connection settings from Allow multi-platform probe connections to Do not allow multi-platform probe connections (default), the changes would not be applied after a Core restart. You could also observe an error message in the Multi-Platform Probe Connection Health (Autonomous) sensor that displayed Error caused by lookup value 'Disconnected' in channel 'NATS Connection State' although the NATS server was installed and running. 

With this PRTG version we announce the deprecation of the Python Script Advanced sensor as of PRTG version 25.x.106. You will receive a corresponding PRTG to do ticket when you update to this PRTG version and when you have added the Python Script Advanced sensor to your PRTG installation. The Python Script Advanced sensor will be deprecated and cannot be added anew as of PRTG 25.x.106. Please use the successor sensor Script v2 instead. For more information please see our Knowledge Base article: What do deprecation and discontinuation in the context of sensors mean?

Read here for differences and more information about the two sensors: Why should I use the Script v2 sensor?

We also provide information on how to migrate your scripts with this Knowledge Base article: How can I make my Python scripts work with the Script v2 sensor?

With this PRTG version we inform you about the upcoming sensor migration of the SSH INodes Free sensor to its successor SSH INodes Free v2 sensor in PRTG 25.x.106. You will receive an according To Do ticket in PRTG with this PRTG version when you run SSH INodes Free v1 sensors. This tickets informs you also about upcoming custom device template migration from the existing sensors to the new sensors.

For more information about sensor migration, see the following Knowledge Base article: https://kb.paessler.com/en/topic/91901.

This release contains a new code signing certificate and a corresponding intermediate version which will cause the auto-update process to run two times, please be informed that this could lead to longer update times and multiple reboots.

Important: If you update your PRTG manually, please note that you need to update to the intermediate version 25.1.104.1906 first before you are able to update to the released PRTG version 25.1.104.1946.

In certain cases, the PRTG core server does not start anymore after updating to PRTG 25.1.104 and the log file core.log contains the message:
 

• Signature of \Program Files(x86)\PRTG Network Monitor\32 bit\PRTG Server.exe is not valid or
• Signature of \Program Files (x86)\PRTG Network Monitor\64 bit\PRTG Server.exe is not valid

The issue mainly affects PRTG installations that are offline or have limited access to the internet and happens if the code signing signature fails due to a missing trust chain in the trusted root certificates of the Windows certificate store.

You can resolve the issue by adding the trusted root certificate for timestamp signature. For more information, see the Knowledge Base article https://kb.paessler.com/en/topic/91907.

If you are running on preview or canary channel, the auto-update process may run into problems. You need to either switch to the stable channel for one full update cycle or install the newest update by hand since there is no intermediate version for this version channel available, we are sorry for the inconvenience.

You will notice that PRTG logs several entries for exceptions in the Core.log in certain cases when you change the graph period in the Graph Settings under User Interface in the System Setup. The issue occurred in the previous PRTG version 24.4.102.1351. The log entries with the message Exception: Wrong period in cache appear after the automatic core server restart when you have changed and saved graph settings before. We will deliver a fix for this issue with the upcoming PRTG versions. 

When you run PRTG as a cluster setup and when you update to this PRTG version then the failover node will not be updated automatically. This issue occurs when you use an intermediate PRTG version before in order to update to the latest released PRTG version 25.1.104.1946. As a workaround, please update your failover node manually.

In certain cases, you may run into an issue when you use SNMP v3 as SNMP Version for monitoring tasks in your PRTG. Your SNMP sensors can run into an error state with the message no response. The issue occurs when you update to this PRTG version 25.1.104.1946 and could happen as well on the intermediate version 25.1.104.1906 needed for further updates. We are currently investigating this issue with high priority.

You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:

Stable 25.1.104.1946

• sha256_exe 012721D374016A2B472171EE5B1B6657C05744E8A6AA2A05479D5CB004A26D93
 
• sha256_zip 2AC635C1B702628CE7613D3E1236A4CF5063A56466D3AFFA2135E6389F188D6D

• We fixed an issue for the section scheduledependency where maintstart and maintend for Schedules, Dependencies, and Maintenance Window setting where not displayed in UTC (Universal Time). When you executed a GET request on the endpoint api/v2/devices/id you could notice that the maintstart and maintend was displayed in the given timezone of the user set in the PRTG web interface instead of the UTC timestamps used by PRTG core and appserver.
• We fixed an issue for the endpoint devices/id that happened in rare cases when you executed a GET request with the include parameter. The values for id, name and href under _inheritanceSource were empty in these cases. For the value kind type you would receive an error message: unknown_referenced_object_type_for_itemEnumerated.
• We fixed an issue for GET request API call on [Probe/Group/Device] endpoint with the include parameter set where certain settings were missing in the returned response. The issue occurred only when you had a fresh new PRTG installation and with the object IDs [1/50/40] that are automatically created upon installation.
• You can now receive the settings Credentials for PRTG Data Hub when you execute a GET request on the endpoints schemas/kind and devices/id in the PRTG APIv2.
• We improved the handling for receiving and editing access rights via PRTG API v2. When you execute a GET request on an object endpoint, for example /devices/{id} with id=40 (local Probe) and include= accessgroup, inheritance as parameter, you will get the corresponding access rights groups. Previously, if you wanted to change access rights via PATCH request, you would have to use the same number of arguments that were returned with your GET request before. It is now possible to change access rights settings for only a certain number of groups via PATCH request. Executing a PATCH request for access rights will lead to a 403 access denied error in the API when you are logged in with a read-only user.

We improved the performance of the PRTG application server that caused a higher memory usage especially for larger PRTG installations in the previous PRTG versions. 

We fixed an issue for creating objects when the parent (e.g. device, group) was deleted in the meantime. In previous PRTG versions, you would receive an unspecific error message in this case. The error message now displays that the object could not be created: The parent object does not exist. It might have been deleted.

You will now see the message in your acknowledged sensors about who acknowledged it with an according time stamp as well as the error message itself. This information was missing in the previous PRTG versions when you did not enter a text for an acknowledge message. 

We fixed an issue for the error page with the message The selected object cannot be used here or it does not exist that is displayed when you, for example, want to clone or delete a not existing report. In this case the mentioned error page is displayed, however, the redirect would link you to the PRTG welcome page. You will now be redirected back to the page you came from, in this case the Reports tab.

We fixed an issue that occurred when you have set your Home Page URL to an object in PRTG where you did not have the corresponding access rights or the object was deleted in the meantime. An error page would appear in those cases, however, there was no option to return to PRTG. We now added an additional button to the error page Go to welcome page that will direct you to welcome.htm.

We improved the drop down menu for the tab Logs in the PRTG New UI. In previous PRTG versions, you had to scroll down in the menu when you clicked on Choose Filter in order to see the option Status Message Related. The drop down menu has now an extended view to display all options without scrolling.

We improved the objects Detail page when you navigate to the Monitoring overview. Instead of just the content list, you can now scroll through the whole page. The Actions button will stay in place when you scroll through the page. 

You can now set a different Refresh Interval (Sec.) for a page refresh in PRTG in your Account Settings for PRTG Web Interface. In previous PRTG versions, you were able to save your settings, however, the refresh timer in the page footer was not updated. 

We fixed an issue where not all channels of sensors that belong to the probe device of a remote probe were displayed in the new UI. This issue occurred in previous PRTG versions after you have approved a new incoming remote probe.  

• Your selected sensors will now be displayed fully in the Report settings under Select Sensors Manually when you have added them to your report via drag and drop. In the previous PRTG versions, those selected sensors were cut off in the Objects area under Select Sensors Manually.
• We fixed an issue for the reports URL when you open the settings Select Sensors Manually. The URL would wrongly display /report//channels in this case. We changed it now to /report//select-sensors-manually.

We improved the message toast that is displayed when you save settings on pages throughout PRTG in the new UI. The message that is displayed after you have saved your settings successfully will now show Settings have been saved. For Map comments and Report comment setting changes, the message displayed will be Comments have been saved.

• We fixed an issue that occurred, when you clicked on a sensor in the navigation tree under Monitoring. The sensor overview page would open on the right side. When you closed the split view for the sensor overview page and clicked on the same sensor in the tree again, the overview page would not open.
• We improved the message for new added sensors to a device when there is no data available yet. Previously, when you navigated to the sensor overview page of a new created sensor when no data was available yet, you would see the message No matches could be found. The message now displayed in such cases is No data yet.

The new UI and APIv2 now support the login via Single Sign-on with this PRTG release. When you want to use the PRTG application server, you do not need to specify any new callback URLs on your PRTG instance under Available Callback URLs in the Single Sign-on Settings. However, you need to configure the callback URL within the single sign-on provider for any domain that the appserver is reachable under (Okta or Entra ID). For more information on how to set up SSO, please see our Knowledge Base article: How to integrate Microsoft Entra ID into PRTG? and How to integrate Okta SSO into PRTG?

You are now able to see and access the tabs Log and History in the new UI provided that you have the according user rights for the relevant object. Please note that there is no contex menu available for object links, for example in the Log tab when you right click on a sensor or device.

You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:

Stable 25.1.102.1373

• sha256_exe 45BE984AEBCECFD670BDCD3B7228A4190E7656CAEC4BE29A2E43E5BE3EF24E81
• sha256_zip 5659680469A7ECC56FD49D6D6EE0DFE84CCA09819820765911DE2AD4A1319378