PRTG Release Notes:
Preview Channel

The order of elements within this category can be rearranged via drag-and-drop using the arrow icon on the righThe order of elements within this category can be rearranged via drag-and-drop using the arrow icon on the righThe order of elements within this category can be rearranged via drag-and-drop using the arrow icon on the righThe order of elements within this category can be rearranged via drag-and-drop using the arrow icon on the righThe order of elements within this category can be rearranged via drag-and-drop using the arrow icon on the righ

We fixed an issue where opening a direct link to a PRTG object, such as a Map sharing link, triggered an unhandled Single Sign-on error instead of the standard PRTG login screen. This happened when the request URL did not match any of the configured redirect URIs under Single Sign-On in the System Administration settings. PRTG now correctly detects the URL mismatch and no longer forwards you to the SSO provider in this case.

We fixed an issue for Reports where the Object panel under Select Sensors Manually showed raw HTML instead of properly rendered objects. You can now see and click objects again, including their breadcrumb path and icon.

We currently face an issue where the Windows Compatibility Options section is displayed twice. The second, shorter section is an obsolete remnant from a previous implementation and is no longer functional. Any settings configured in this second section will not be applied to any sensors. As a workaround please use the first Windows Compatibility Options section that appears on the page. This is the only section that is active and where your configuration will be correctly applied. We will deliver a fix for this issue with a future PRTG version.

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

• sha256_exe 9B0CB4A66C0C08A73F9E7D775E5A89921F85E77B6DECC4B00F009B557401CCE2
• sha256_zip 64EE104D2C93CEA48FC3CE646072332737D7CB4F72CB04F54AE83326923CDA6F

You can now monitor the complete loading time of web pages, including all resources such as images, scripts, and stylesheets when you try out the experimental HTTP Webpage (BETA) sensor. This sensor is the successor to the existing HTTP Full Web Page sensor. The sensor uses a headless Chrome browser on the probe machine to load the requested URL and alerts you when loading times exceed defined thresholds. This sensor also supports the Smart URL Replacement feature, which adds the device host in the URL field of a HTTP sensor automatically when you enter https:///.

You can try out the experimental SIMATIC S7-1200/1500 CPU Status sensor that monitors the operating state, cycle times, and load of Siemens SIMATIC S7-1200 and S7-1500 PLCs via the S7 Web API (JSON-RPC). This sensor automatically detects firmware capabilities and redundant CPU configurations, cycle time and load channels only appear when the device reports them, so older firmware is supported gracefully. Available channels are Operating Mode, Mode Selector, Cycle Time Events, for example. The channels Operating Mode and Mode Selector, Operating Mode (R2) and Mode Selector (R2) are dynamically created when redundancy is detected.

We now support Negotiate as WMI Authentication Method in the Credentials for Windows Systems as well as WSMan Port and Connection Security in the Windows Compatibility Options for the WMI Service v2 sensor. Please note that this sensor type only supports WSMan protocol for WMI connections with Kerberos and that the option to change the Preferred Data Source in the Windows Compatibility Options is not available for this v2 sensor type.

With this PRTG version we introduce the new Auto-Discovery Task system that lets you manage all your Auto-Discoveries and review their outcomes from one central place in PRTG. You can now create, edit, and delete Auto-Discovery Tasks directly from the overview menu on the left side. Use the new button Create Task to create a task under any probe you have write access to. The button is grayed out if you have no write permissions on any probe. Required fields are validated, and you are redirected to the overview after a successful creation. Existing Legacy Auto-Discovery Tasks will be displayed in the new Auto-Discovery section.

Please note that this feature currently only works if you are logged in as a user with administrative user rights.

We fixed an issue where it was possible to create a group via Add Group button in the action items without entering a value in the mandatory fields. The settings window was closed after you clicked create and an error would occur: The validation of at least one of the new objects failed because of the following: IPv4 Base: Required field, not defined. The object was not created.

We fixed several issues with the approval flow for unapproved probes in the device tree. Previously, the Approve and Deny buttons reappeared after approving or denying a probe instead of disappearing. They now correctly disappear after approval and the sensors and devices of that probe become visible as expected. The buttons now remain visible under an unapproved probe regardless of whether the tree node is expanded or collapsed. The approval or denial notification is also restricted to users with Write permission and pops up immediately upon login if an unapproved probe is present.

• We reordered the tabs across Probes, Groups, Devices, and Sensors sections to follow a logical, usage-based sequence. Tabs are now grouped by relevance, so you can find the most relevant information faster.
• You can now access system information directly from the device detail page in the New UI via the System Information tab. Please note that this tab is not available on mobile view
• You can now view and edit comments directly on Probe objects in the New UI, bringing Probes in line with Devices and Groups. Opening the Comment tab loads the current comment, and saving persists your changes immediately. The Save and Discard buttons are disabled when there are no unsaved changes.
• We fixed an issue where the History tab appeared twice in the submenu on Probe and Group detail pages, once between Logs and Settings, and once again as the last item after Comments. Both entries linked to the same view. The History tab now appears exactly once in its correct position between Logs and Settings on both page types.
• We added a new Messages tab that is now available on the sensor detail page for sensors that collect message data, such as the Syslog Receiver and SNMP Trap Receiver sensor.

The New UI now surfaces Toplists for all sensors that support them. You can view and navigate Toplists directly from the sensor overview and a dedicated Toplists tab. Sensors that support Toplists are, for example, NetFlow v5, sFlow sensor, IPFIX sensor and Packet Sniffer sensor. An Add Toplist button is available on the Toplists detail page to create new Toplists for the sensor.

Read-write and read-only users can now see and navigate all objects they have access to in the New UI device tree. Previously, these users had no access to any objects in the device tree despite having the correct permissions assigned.

• We fixed an issue for the /experimental/probes endpoint where the filter for status=connected did not work and returned a 400 bad request error in the response body. The issue occurred when you executed a GET request on /api/v2/oas/ for the mentioned endpoint.
• We fixed an issue in PRTG API v2 for the endpoint /devices/{id} that returned a partially wrong response for GET requests on devices that did not have inherited access rights.
• We fixed an issue in the /experimental/sensor/{id} endpoint where the channelgroup.primarychannel field used different formats between GET and PATCH operations. Previously, GET responses returned the full channel ID format while PATCH requests required only the short channel index, forcing you to manually extract and transform the value before using it.

We fixed an issue where only the first created sensor name instead of the sensor type was displayed in the Create Template Results pop-up window after template creation. This issue happened, for example, for the SNMP Traffic v2 or Microsoft 365 Service Status Advanced sensor where more than one sensor is created.

We fixed an issue that occurred in the authentication process of the Network Share sensor to the remote server.

We fixed an issue for the Redfish Power Supply sensor that reported an error with the message The requested resource was not found on the remote server after an HPE iLO firmware update to version 1.22.00 in certain cases.

We fixed an issue where using Auto-Discovery with a template to create the SSH Disk Free v2 sensor produced one separate sensor per Linux mount point, each containing all detected mount points as channels. PRTG now correctly creates a single sensor with one channel per mount point.

We fixed an issue where renaming a Multi-Platform Probe in the PRTG UI was reset to the default name after a Core server restart. If you renamed your probes you would unexpectedly see the changes reverted in previous PRTG versions. The name you set in the PRTG UI now always takes precedence, even if the name is later changed in the MPP configuration, the UI name is retained. Please note that this fix also applies to classic probes, which will no longer revert to their connection-time name when renamed during an active connection.

We fixed an issue that occurred when you updated from an older PRTG version, i.e. 26.1.116.1498, to PRTG version 26.1.118.1380 or later where the NATS server certificate could not be imported in certain cases. The update would fail with a NATS setup error in the installer. The issue only occurred if you had PRTG installed with a non-integrated NATS server, that is prior to version 26.1.118.1380 and you updated to a newer version.

You can now use again the option Create Configuration Snapshot under the section Administrative Tools for the PRTG Core Server in PRTG. In previous PRTG versions, the button Go! did not trigger any action to create a configuration snapshot in the Configuration Auto-Backups folder.

You can now use the Show as Gauges view on the Alarms page as expected. Previously, switching to this view resulted in a blank page showing raw JSON data instead of gauge widgets. This affected any sensor that included HTML content in its status message.

We fixed an issue where Chromium-based browsers experienced significant delays or timeouts when loading pages in the Classic PRTG Web UI. The issue was caused by certain Chrome extensions using postMessage to communicate with the application, a confirmed example is the Angular DevTools extension. Firefox was not affected. You can now use Chromium-based browsers with extensions installed without experiencing indefinite loading times.

With this PRTG version we introduce the new IP Reputation Score sensor, which is the successor to the IP on DNS Blacklist sensor. This new sensor lets you check whether the IP address of a device is listed on DNS-based blacklist servers (DNSBL). The sensor supports both IPv4 and IPv6 and is compatible with the Multi-Platform Probe.

With this PRTG version we introduce the new RDP Client-Side Check sensor, which is the successor to the RDP (Remote Desktop) sensor. This sensor monitors the availability and response time of the RDP service on Windows systems. It establishes a TCP connection to the configured port and measures the time until the connection is accepted. It performs no authentication but it verifies the RDP handshake via the initial server packet. Please note that this sensor type does not support TLS connection.

With this PRTG version we introduce the new Traceroute Hop Count v2 sensor that runs also on the Multi-Platform Probe without requiring the .NET framework. This sensor reports the number of hops from the probe to the parent device, displaying the full route in the sensor message so you can immediately see any path changes. If the parent device is unreachable, the sensor goes into a down state with a meaningful error message. The sensor supports IPv4 and IPv6 and is compatible with both Classic Probe and Multi-Platform Probe. Please note that this sensor does not yet support the If Route Changes sensor setting like the already existing Traceroute Hop Count sensor.

You can now monitor the performance of your Microsoft SQL Server instance with the new WMI Microsoft SQL Server sensor. The sensor supports SQL Server versions 2005–2025, including multiple parallel installations. This sensor works on Classic Probe and will also be supported on the upcoming Multi-Platform Probe for Windows. Please note that this sensor type only supports WSMan protocol for WMI connections with Kerberos.

With this PRTG version we introduce the new WMI Volume v2 sensor that monitors free disk space on a single Windows volume, including drives, logical volumes, and mount points. This sensor type is the successor to the WMI Volume and WMI Free Disk Space (Multi Disk) sensor. Please note that this sensor type only supports WSMan protocol for WMI connections with Kerberos.

With this PRTG version we introduce the new VMware Datastore (REST) sensor that monitors the disk usage and availability of VMware datastores via the vSphere REST API. One sensor instance is created per datastore and serves as an alternative to the existing VMware Datastore (SOAP) sensor. The sensor reports free space, available capacity, accessibility status, datastore access mode, VM count, disk count, and VM power states. The sensor enters an error state when the datastore becomes inaccessible, the API is unreachable, or authentication fails.

We hardened PRTG against possible Cross-Site Scripting (XSS) attacks in terms of channel names and lookup values.

With this PRTG version we improve the PRTG Installer process for NatsManager updates. If the PRTG installer detects a new NatsManager version, it now takes a snapshot of the current configuration, saves the old binary, and replaces it with the new one without deleting or reconfiguring the existing setup. This eliminates the previous full uninstall and reinstall of the entire NATS system including the NatsServer.

We now support the Acknowledge Automatically option for all sensors in the Scanning Interval sensor settings. This option supports Show down status on error (default) and Show down (acknowledged) status on error.

With this PRTG version we added HTTP Proxy support for the SSL/TLS Security Check sensor and SSL/TLS Certificate sensor. The sensor will use the HTTP Proxy server settings if you have configured them in the device settings. The SSL/TLS Security Check sensor and SSL/TLS Certificate sensor left their BETA status with the previous Preview version 26.2.121.1545.

Various other minor fixes and improvements, updated user manual.

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

We updated the German and Spanish language files for certain sensor types.

With this PRTG version your existing custom device templates will be migrated for the following sensor types to their successor sensors: SNMP System Uptime (SNMP Uptime v2), SSH Disk Free (SSH Disk Free v2) and SNMP Memory (SNMP Memory v2) sensor. PRTG will store a copy of the original device templates in the folder PRTG Network Monitor/devicetemplates/backup. The migration happens when you update to this PRTG version. For more information about device template migration, please see our Knowledge Base article: https://helpdesk.paessler.com/en/support/solutions/articles/76000085400-what-is-a-sensor-or-device-template-migration-

PRTG will uninstall the PRTG (PostgreSQL) Database and its files and components when you update to this PRTG version and if you have previously installed the PRTG version 26.2.118 that includes the PRTG Database. This update process, which involves removing the PRTG Database, only occurs if you have not activated the PRTG Database. If the PRTG Database is activated and contains data, you will receive a message in the installer explaining the next steps when you update to this version.

The Core & Probes tab in the PRTG System Administration section is now divided into two clearly separated sections, Core Server and Probes, so you can easily distinguish which settings apply to the PRTG core server and which apply to PRTG probes. This change also applies to the PRTG New UI.

With this PRTG version we announce the upcoming deprecation of the HTTP Full Web Page Sensor. You cannot add this sensor anew when you update to upcoming PRTG version 26.x.123, however, existing sensor types continue to run. We recommend that you use the HTTP Webpage Sensor (BETA) instead. You will receive an according PRTG TO DO ticket when you update to this PRTG version.

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

• sha256_exe 55461A83AAEDB89DCDBFCB9F624D881CF6F50BACCCA18CEC5A3F8F5B5CD69C2B
• sha256_zip 2C787B8B05E091DCA3BB7132B4596366080370647F2407D557214C659EBAC010

We fixed an issue for the Syslog Receiver sensor that did not receive and display Syslog messages anymore in the previous PRTG version when you had configured Syslog messages with notification template Send Syslog Message.

We fixed an issue that caused gauge widgets to stop rendering in the sensor overview and on maps in certain cases when the target device for that sensor was not reachable and the sensor was in Down status. The issue happened, for example, for the Ping v2 sensor that measures float values and that could report non-numeric values (NaN or INF) when a monitored target became unreachable.

You can now fully access the Custom HTML map item properties in Map Designer again when you update to this PRTG version. Previously, selecting the Custom HTML option in the Properties panel caused an endless loading state, preventing the HTML fields from appearing.

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

• sha256_exe 2A2C762BDF021EF697A398D831BDED29901EDD7E64AA0E4E73E14D53FD7FD278
• sha256_zip 12C69861563963FE542B3447A03A6F05CF919EDED91259652610A184644DFC98

You can try out the experimental WMI Service v2 sensor that is the successor to the WMI Service sensor. You can select the services during sensor creation. The sensor will report if services are stopped or paused. If you want to use WSMAN for WMI connection, please make sure to enable WSMAN protocol on the target device. Please note that this sensor no longer has the option Start/Restart service in the WMI Service Monitor settings.

The dependency field now displays the root of the dependency chain. Previously, the dependency of an object was only displayed to its immediate dependency.

We reduced the loading time for iframes on the PRTG System Settings page in the New UI.

We have improved the user rights for read only and read/write users regarding the Copy function via context menu of an object.

• We have replaced the following PRTG API v2 endpoints that were already announced as deprecated in the Open API Specification: probes/{id}/overview, groups/{id}/overview, sensors/{id}/overview and channels/{id}/overview. Those endpoints were replaced with probes/{id}, groups/{id}, devices/{id}, sensors/{id} and channels/{id}. Please note that the endpoints marked as deprecated will be removed in the future.

After activating your PRTG license and restarting the Core Service, successful license activations are no longer incorrectly logged as errors in Core.log. Previously, a successful activation triggered a misleading error entry such as Error during activation of license [...]: Activation was successful. This issue occurred only at the DEBUG log level.

• We have improved the PRTG installer that displayed a command window for a short moment when external commands or programs were called, like for the PostgreSQL database.
• We fixed an issue where the links for our terms and conditions and privacy policy redirected to the English web page when running the installer in German.

When using the HTTP v2 sensor with the POST request method, you can now set a custom Content-Type header (e.g. application/json) and the sensor will correctly apply it to outgoing requests. Previously, the sensor ignored the configured value and always sent application/x-www-form-urlencoded instead.

After an unexpected SSH disconnection, the SSH Script v2 sensor now correctly uses the newly established SSH session for all subsequent scans. Previously, after a successful reconnect, the probe fell back to the previous session object, causing repeated authentication failures (e.g., ssh_userauth_publickey: Out of memory) every 60 seconds with no automatic recovery. A possible workaround was to manually pause and resume the sensor.

We fixed an issue where it was possible to click an Add sensor button for the PRTG Core Server device, which resulted in an error with the message: Autonomous objects do not support this operation. The Add sensor button is now hidden for devices that do not support this option. We fixed this issue also in the New UI.

With this PRTG version we introduce the new Proxmox VE Cluster Health sensor that left its BETA status and is now fully supported. This sensor monitors the health status of Proxmox VE clusters. We introduced this sensor type as experimental BETA sensor with PRTG version 26.1.118.1380.

With this PRTG version we introduce the new Proxmox VE Container Status sensor that left its BETA status and is now fully supported. This sensor monitors performance metrics and status of LXC containers on Proxmox VE clusters. We introduced this sensor type as experimental BETA sensor with PRTG version 26.1.116.1498.

With this PRTG version we introduce the new Proxmox VE Node Performance sensor that left its BETA status and is now fully supported. This sensor monitors performance metrics and status of Proxmox VE host nodes. We introduced this sensor type as experimental BETA sensor with PRTG version 26.1.118.1380.

With this PRTG version we introduce the new Proxmox VE Virtual Machine Status sensor that left its BETA status and is now fully supported. This sensor monitors performance metrics and status of QEMU virtual machines on Proxmox VE clusters. We introduced this sensor type as experimental BETA sensor with PRTG version 26.1.116.1498.

With this PRTG version we introduce the new REST JSON Data sensor that left its BETA status and is now fully supported. This sensor accesses a Representational State Transfer (REST) application programming interface (API) endpoint and retrieves JavaScript Object Notation (JSON) encoded data. We introduced this sensor type as experimental BETA sensor with PRTG version 25.3.110.1313.

With this PRTG version we introduce the new SSL/TLS Security Check sensor that left its BETA status and is now fully supported. The SSL/TLS Security Check sensor monitors the security of a connection secured by Secure Sockets Layer (SSL)/Transport Layer Security (TLS). We introduced this sensor type as experimental BETA sensor with PRTG version 26.1.118.1380.

With this PRTG version we introduce the new SSL/TLS Certificate sensor that left its BETA status and is now fully supported. This sensor monitors the certificate of a connection secured by Secure Sockets Layer (SSL)/Transport Layer Security (TLS). We introduced this sensor type as experimental BETA sensor with PRTG version 26.1.116.1498.

With this PRTG version we introduce the new SNMP Custom v2 sensor that left its BETA status and is now fully supported. The SNMP Custom v2 sensor monitors a single parameter that is returned by a specific object identifier (OID) or Abstract Syntax Notation One (ASN.1) Management Information Base (MIB) via the Simple Network Management Protocol (SNMP).

With this PRTG version we introduce the new SNMP Traffic v2 sensor that left its BETA status and is now fully supported. The SNMP Traffic v2 sensor monitors bandwidth and traffic on a device via the Simple Network Management Protocol (SNMP). We introduced this sensor type as experimental BETA sensor with PRTG version 23.3.88.1393.

With this PRTG version we introduce the new SSH Script v2 sensor that left its BETA status and is now fully supported. This sensor connects to a Linux/Unix system via Secure Shell (SSH) and executes a script file that is located on the target system. This sensor type is the successor sensor of the SSH Script sensor. We introduced this sensor type as experimental BETA sensor with PRTG version 25.2.108.1358.

You can now monitor network jitter on any supported probe platform — including Linux and macOS — without requiring the .NET framework, using the new Ping Jitter v2 sensor. It supports IPv4 and IPv6 and provides four monitoring channels: Jitter (ms), Minimum, Average, and Maximum Response Time (ms). You can configure the timeout, ping count, ping delay and time to live. If no ping replies are received, the sensor reports an error message accordingly.

We changed the error message handling for EXE/Script and EXE/Script Advanced sensors. PRTG will no longer print error messages in the sensor message. Please check your sensor logs in case of errors with your custom scripts.

Various other minor fixes and improvements, updated user manual.

We updated the French, Portuguese, Russian, Chinese, Dutch and Japanese language files for certain sensor types.

Your Database Health (Autonomous) sensor will be removed from your PRTG installation when you update to this PRTG version or future versions. The Database Health (Autonomous) sensor was created upon installation of PRTG version 26.1.118.1380 that includes the PRTG Database. With PRTG version 26.2.120.1449, we have already removed the files and components from the PRTG Database which will no longer be installed for new installations.

New PRTG installations now use WSMAN as the default monitoring protocol instead of DCOM. Existing installations continue to use DCOM without any changes, and you can switch to WSMAN at any time using the new global activation toggle in the UI. PRTG will also create a To-Do ticket for existing installations, informing you that WSMAN is now the default for new setups, that Kerberos is available.

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

Due to changes to certain PRTG API v2 endpoints that we are deprecating in this version, the current OPC UA server version 1.3 is not compatible with this Preview xxx. These changes will be included in the new OPC UA server release following the PRTG 122 stable version.

We currently face an issue that occurs when you update from an older PRTG version, i.e. 26.1.116.1498, to PRTG version 26.1.118.1380 or later where the NATS server certificate could not be imported in certain cases. The update would fail with a NATS setup error in the installer. The issue only occurs if you have PRTG installed with a non-integrated NATS server, that is prior to version 26.1.118.1380 and you update to a newer version.

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

Preview 26.2.121.1545

• sha256_exe 4F163E726DF5202571BEEA50C13C8A9C6FB23B12E1460B30E412E3317FDE7EDC
• sha256_zip A16AA8BE15B2088C6946BFB68F2224C9AEB5D6BA5A962A8242573C1302E61DED