- English
- Deutsch
- Español
- Français
- Italiano
- Português
With this PRTG version, we introduce the new FTP v2 sensor as the successor to the existing FTP sensor. The sensor monitors file servers via the File Transfer Protocol (FTP) and FTP over SSL (FTPS), measuring the server's response time and returning the server's response message. You configure it via an FTP URL, and can set the FTP port, request timeout, and encryption mode (Implicit, Explicit, or None), so you can verify that an FTP/FTPS service is reachable, responsive, and enforcing transport-level security.
With this PRTG version, we introduce the new VMware Host Performance (REST & VI/JSON) sensor as a successor to the VMware Host Performance (SOAP) sensor. The sensor monitors CPU, memory, disk, and network performance metrics of a VMware host via the vSphere REST and VI/JSON API, enabling you to proactively detect performance degradation on your hosts. Please note that the sensor requires vSphere version 8.0.1.0 or above.
You can now monitor the disk usage of a logical disk or mount point on a Windows system using the new WMI Logical Disk I/O v2 sensor, the successor to the WMI Logical Disk I/O sensor. The sensor reads performance counters for a logical partition (identified by its drive letter, such as C) and returns read/write throughput, I/O operations, queue lengths, timing, and free space so that you can detect disk I/O bottlenecks and capacity issues before they affect application performance. This sensor works on PRTG Classic Probe and will be supported on the upcoming Multi-Platform Probe for Windows.
You can now monitor the input/output parameters of a physical hard disk on a Windows system using the new WMI Physical Disk I/O v2 sensor, the successor to the Windows Physical Disk I/O sensor. The sensor provides read/write throughput, I/O operations, queue lengths, and timing percentages to help detect disk I/O bottlenecks that can affect application performance and stability. This sensor works on PRTG Classic Probe and will be supported on the upcoming Multi-Platform Probe for Windows.
With this PRTG version, we introduce a new Default UI setting under System Settings > System Administration > User Interface, so you can make the New UI the default target for system-generated links such as email notifications and reports. Select New UI in the Default UI option to switch these links over; the classic UI remains the fallback until you do.
Beta sensors are now always visible in the Add Sensor dialog. If experimental features are turned off, these sensors appear greyed out together with a hint that you need to enable experimental features under Setup > Monitoring to use them, so you can discover what is available without having to enable the flag first.
We added the regions Europe (Spain) and Europe (Zurich) to the Region selection of the Cloud HTTP v2 and Cloud Ping v2 sensors.
We enabled SSL certificate verification for AWS sensors when they connect through a proxy. In addition, unreachable regions no longer time out the meta-scan or cause it to fail.
We removed the fixed 60-second minimum interval from a large number of sensor types, including many SNMP sensors such as SNMP Memory v2, so you can scan more frequently where your setup allows it. We also adjusted the recommended interval on several other sensors, in most cases to a longer interval, to better match typical usage and reduce unnecessary load. The scanning interval of your existing sensors is not changed; these adjustments only apply to new sensors or when you manually change an interval yourself.
We performed sanitization on EXE/Script sensor parameters to prevent information disclosure.
We improved the automatic update so that a failed update no longer runs in a loop. If the installed version does not match the version the auto-update was targeting, PRTG creates a To Do ticket to let you know that the update failed, as before, and now also removes the leftover installer file at core service start so the failed installer is not picked up again on the next run.
Various other minor fixes and improvements, updated user manual.
With this PRTG version, we automatically enable the Appserver on update so that the Open New UI button and the REST API v2 are directly available without needing to activate the Appserver manually first. Before activating, PRTG checks whether enough memory is free and skips automatic activation if not, so it does not enable the Appserver on installations already running close to their resource limit. You can still activate it manually later from System Administration.
In preparation for changing the Probe-to-core communication from NATS to QUIC, PRTG will create a TO DO ticket that informs you about the change in case you have an integrated or remote NATS Server active. QUIC is a UDP based, reliable and modern transport protocol that enables you to onboard (remote) probes easier with a more secure connection. A direct TCP Connection remains available as fallback, in case your network does not allow QUIC communication. We therefore also simplified onboarding a Multi-Platform Probe (MPP) with QUIC/TCP by showing the public server certificate directly in the PRTG Web UI. A new read-only text box displays the base64 PEM-encoded CA certificate loaded by the probe-adapter for the QUIC/TCP listeners, including the root CA if one is present, so you can easily copy it over to your MPP instead of having to locate and export it manually. The Multi-Platform Probe will support QUIC with upcoming releases. For more information, please see this knowledge base article: How can I transfer my multi-platform probes from NATS to QUIC?.
We fixed the Hardware Fault Count primary channel of the SIMATIC S7-1200/1500 Hardware Status sensor so that a parent module no longer double-counts a child's fault. A faulty module contributes 1 to the count only when none of its charted descendants is already counted, ensuring each faulty piece of hardware is counted exactly once.
We fixed an issue where MQTT sensors (such as MQTT Statistics and MQTT Subscribe Custom) could, in rare cases, stop responding and never deliver results. The issue was caused by a deadlock during sensor creation and is now resolved.
We fixed an issue where the configuration details for Single Sign-on were not transmitted via support bundle when you selected the Contact Support option.
We fixed an issue for PRTG access via link, for example in notifications, where you had to log in again even with an open and active PRTG session.
We fixed an issue where PRTG ignored values above 30 days configured for PRTG Web Server Log Records under Historic Data Purging. Older web server log files are now retained for the full number of days you set, instead of always being deleted after 30 days.
We fixed an issue where logging in to PRTG via Single Sign-on resulted in a 404 error when you used a non-default (custom) HTTPS port for the Web UI. The issue started to occur with version 26.3.122.1665 and affected setups where the PRTG web interface used a non-standard port.
We fixed an issue on the Multi-Platform Probe where buffered monitoring data was not sent to the PRTG core server after a longer outage of the connection. Graphs and data tables showed a gap for the outage period even though the probe had buffered data locally. Buffered data is now delivered after the connection is restored.
We fixed an issue on PRTG Hosted Monitor (PPHM) where the notification sent when a user is deleted used the deleted user's own email address instead of the email of the administrator who performed the deletion.
We fixed an issue that occurred when you updated to PRTG version 26.2.120.1477 in certain cases where you would receive Internal Server Error messages right after logging in to your instance.
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:
We fixed an issue where it was not possible to edit the License Key or License Name on the /settings/status/license/activation page in the New UI. The License Key or License Name was not changed previously when you clicked on Update License. Additionally, we fixed an issue for the Activation Type that did not display the settings when you selected Manual (offline activation).
You can now access the historic sensor data directly in the New UI through the new Historic Data tab on a sensor, so you can run ad-hoc reports over a selected time frame and export monitoring data for analysis in external tools without switching to the classic web interface.
We fixed an issue where it was not possible to create and start a Report with the default Start and End date settings. Previously, the Run Report button would not trigger any action in the Run Now tab in those cases and the report would only start when you selected one of the Quick Range buttons.
We now redirect correctly from the classic PRTG web interface https://yourserver/home to the homepage of the New UI https://yourserver/.
We renamed the tab Insights to Top 10 so that the name better matches the content displayed on the tab.
We fixed an issue where sensor graphs did not clearly show gaps in data collection: the graph ended at the timestamp of the last received data instead of extending to the current time, which could make outdated data look recent. The right edge of the graph now always represents the current time, so gaps in data collection are visible at a glance.
We fixed an issue where a sensor could show fewer channels than expected in the New UI, with its primary channel missing, if the primary channel had been set (for example via the API) to a channel that did not exist yet because the sensor had not completed its first scan. Affected sensors also got stuck with Last Scan showing N/A, and Scan Now did not trigger a new scan.
We fixed an issue in the New UI where copying and pasting a device or sensor into a user's own personal group failed with a permission error, even though the user has write access to that group. This happened when the user's access to a parent group elsewhere in the tree was set to read-only.
With this PRTG version, we introduce the new FTP Server File Count v2 sensor, a successor to the existing FTP Server File Count sensor, ensuring you can continue monitoring file counts on your FTP server. The sensor connects via an FTP URL, rather than separate host/port settings, and lets you configure recursive subfolder scanning, Passive or Active FTP mode, request timeout, and connection security (Explicit, Implicit, or None). This sensor type supports IPv4 and IPv6.
With this PRTG version, we introduce the new Redfish Fan Status sensor, giving you a single, consolidated view of fan health and speeds for a server via Redfish. This sensor creates the channels Overall Status, (Fan Name) Status and (Fan Name) Speed. You can now replace the SNMP HPE ProLiant System Health sensor with the Redfish sensors (Redfish System Health, Redfish Temperature, and Redfish Fan Status), fully migrating from SNMP to Redfish for HPE ProLiant servers.
With this PRTG version, we introduce the new WMI Network Card v2 sensor, a successor to the classic Windows Network Card sensor for monitoring bandwidth usage and traffic statistics of Windows network interfaces. The sensor uses WMI to track in/out traffic, packet rates, and error/discard counters, helping you detect overloaded links, faulty interfaces, or unusual traffic patterns. The sensor runs on PRTG classic Probe and will be supported on the upcoming Multi-Platform Probe for Windows.
With this PRTG version, we introduce the new WMI Print Queue v2 sensor, a modern successor to the existing Windows Print Queue sensor, letting you monitor print queues on your Windows print server. The sensor discovers print queues and reports the number of jobs in the queue, optionally filtered by a minimum print job age so only jobs older than a defined threshold are counted. You can optionally define custom sensor states (Warning or Down) for specific printer return messages, such as Paper Jammed, Toner Out, or Offline, instead of using the default behavior of ignoring these messages. This sensor works on PRTG Classic Probe and will be supported on the upcoming Multi-Platform Probe for Windows.
With this PRTG version, we introduce the new WMI Windows Security sensor as a successor to the WMI Security Center sensor, which monitors the security status of Windows client systems via WMI by reporting on security products registered with the Windows Security Center, such as antivirus, antispyware, or firewall products. Each sensor reports Product Status as the primary channel, along with Signature Status. This sensor does not run on Windows Server systems, since the Windows Security Center is only available on client Windows versions. This sensor works on PRTG Classic Probe and will be supported on the upcoming Multi-Platform Probe for Windows.
We hardened PRTG against possible cross-site scripting (XSS) attacks related to output on error pages.
We performed sanitization on notification message parameters to prevent information disclosure.
The Script v2 sensor now supports PowerShell 7 (PowerShell Core) with this PRTG version, letting you run modern scripts that rely on PS 7 features or modules. The sensor now detects and runs PowerShell scripts using a secure script-wrapper environment that disables verbose event logging. Please note that the already existing EXE/Script sensors continue to support PowerShell 5.1, since compatibility with PowerShell 7 and the old sensors is not given.
We improved how the Traceroute Hop Count v2 sensor handles route changes. Previously, a route change only triggered a single warning or down status that cleared as soon as the route stabilized, which could hide persistently unstable routes. Now, you can enable the new Notify on Route Change setting to have PRTG create a notification whenever the route changes, giving you a more reliable way to track route instability over time. If enabled, you can also activate Ignore ICMP Timeouts to exclude timeouts from the route comparison.
Various other minor fixes and improvements, updated user manual.
We updated the German, Dutch and Spanish language files.
You will see an additional information on the PRTG Setup page for System Status: UVExplorer. This entry is intended to prepare for future releases and currently shows the statuses disabled, unknown, and n/a.
We fixed an issue where sensors that were set to Down (Acknowledged) Indefinitely lost their acknowledged status after a cache recalculation. The issue happened when you triggered a Cache recalculation manually and the acknowledged sensors reverted to Down Status after the Service Restart.
We fixed an issue that occurred in previous Preview version 26.3.123.1654, where the PRTG Core service ran into a read lock in certain cases when you set up a new Multi-Platform Probe using this PRTG Preview version. After adding the NATS Server Access Identifier in the NATS Connection Settings and restarting the Core service, you could observe the following error in the Core.log: The current Thread ran into a timeout after entering a writelock, waiting for readers to leave.
We fixed an issue where PRTG Desktop failed to load a device's child sensors when a Ping v2 sensor on that device was in timeout state and returned an INF value for lastvalue_raw. Previously, the API response's non-standard INF JSON value caused an invalid JSON error in PRTG Desktop, leaving the device entry stuck in loading indefinitely, even though the same device and sensor loaded correctly in the PRTG web interface.
We fixed an issue for the HTTP v2 sensor that reported an error with the message The sensor could not get a response from the server. 302 (Found) in certain cases. The issue occurred in cases where connections closed by some embedded HTTP servers without sending a proper close_notify were incorrectly reported as an error, even though the response data had already been fully received.
We fixed an issue where the NetApp LUN v2 sensor treated the comment field as mandatory, causing sensor creation to fail for NetApp ASA r2 systems, where this field is not present in the LUN REST API response at all.
We fixed an issue where the field for Login Header Name was visible when you used None (default) for the Authentication Method in the Credentials for REST API settings. The Login Header Name field is now only visible when you select the option Session-based authentication with Header (default).
We fixed an issue for sensors that use a strict certificate validation so that system, group policy or enterprise certificates are now properly imported using the Certificate Validation settings. This fix applies for Cisco Meraki, Microsoft 365, Microsoft Azure, Cloud and Zoom sensor types.
With this PRTG version, we deprecate the SSH Disk Free sensor. You can no longer create this sensor type when you update to this PRTG version, however, existing sensor instances continue to run. You will also receive an according TO DO ticket in PRTG. We recommend that you use the successor sensor SSH Disk Free v2 instead. For more information about sensor deprecation and discontinuation, please see our Knowledge Base article: What do deprecation and discontinuation in the context of a sensor mean?
With this PRTG version, we deprecate the HTTP Full Web Page sensor that we already announced with PRTG Stable version 26.3.122.1665. You cannot add this sensor anew when you update to this PRTG version, however, existing sensor types continue to run. We recommend that you use the HTTP Webpage Sensor (BETA) instead.
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:
You can try out the experimental SIMATIC S7-1200/1500 Alarm Status sensor (BETA) with this PRTG version, which uses the S7 Web API's Alarms.Browse function to monitor active and unacknowledged alarms on your Siemens S7-1200/1500 PLC, including the critical case where the PLC stays in RUN while a process alarm remains active and unaddressed. The sensor reports the number of unacknowledged active alarms in Unacknowledged Active Alarms as primary channel, alongside total active alarms broken down into program, system, and other alarm categories, and shows the text of the most critical active alarm as the sensor message. This sensor requires Credentials for S7 Web API in the device settings.
We introduce a new feature Alarm Insights in the New UI. It is available on the left side menu bar. The feature helps you analyze alarms, acknowledge them directly, and get suggestions on how to resolve them. Alarm Insights is currently available as an early access preview. You can sign up to participate via a link that takes you to the registration page.
You are now able to simulate an error status via context menu Simulate error status for sensors. Once a sensor is in simulated error state, resuming it clears the simulated error.
We fixed an issue where in certain cases submitting forms that use iFrames in the New UI briefly displayed the classic PRTG interface in the background.
We fixed an issue in the Map Designer where clicking on objects in a Data Table did not navigate correctly within the New UI. Previously, clicking a sensor's graph opened the sensor overview in the classic UI instead of the sensor's Graphs page in the New UI, and clicking on other objects resulted in a Something went wrong while loading the content error.
With this PRTG version, you can now use the Search option in the New UI, letting you search all your objects from anywhere in the interface and jump straight to a device, sensor, report, or ticket by name instead of navigating the object tree. A search input is now available in the header on every page; submitting a search takes you to a dedicated results page. The page also shows a loading state while searching, a hint when no term is entered, and an empty state with a quick way to clear your search and filters when nothing matches.
The primary channel of a sensor is now correctly displayed in the New UI when you changed it before in the Sensor Display settings in the PRTG classic interface.
You can now use the Recommended sensors feature in the New UI that is displayed on the sensor Overview page and which is available also via context menu. You can trigger the action by clicking on Recommend now. You can trigger a scan at any time to refresh recommendations, with a spinner shown while the scan is in progress, and an empty list if no recommendations are available. A success or error toast confirms the outcome after installing sensors.
We fixed an issue in the popup window for editing Schedules where saving with an empty Schedule Name field correctly blocked the save and showed the This field is required. validation error, but incorrectly also displayed the Settings have been saved. success toast at the same time. Now, only the validation error is shown when a required field is missing, and no success toast appears.
With this PRTG version, we introduce the new Redfish Temperature sensor, which lets you monitor individual temperature readings from any Redfish-compliant server. The sensor creates one instance per physical temperature probe, giving you granular thermal visibility and per-sensor alerting instead of a single rollup value. This sensor supports IPv4 and IPv6.
With this PRTG version, we introduce the new SNTP v2 sensor, which monitors a Simple Network Time Protocol (SNTP/NTP) server. The sensor checks the time difference between the target NTP server and the probe's local system time, the server's response time, and its stratum level. Unlike the already existing SNTP sensor, this sensor reports the time offset at millisecond resolution instead of in whole-second steps, making small clock drifts visible so you can set alerts on them. This sensor comes with the channels Response Time, Offset, and Stratum. The sensor supports both IPv4 and IPv6 and is compatible with the Classic probe, the Multi-Platform Probe, and PRTG Hosted Monitor.
You can now monitor available (free) system memory on Windows using the new WMI Memory v2 sensor. The sensor connects via WMI and provides free memory in bytes and as a percentage, helping you detect low-memory situations before they impact application performance or stability. This sensor will also be supported on the upcoming Multi-Platform Probe for Windows.
You can now monitor the CPU load of Windows systems using the new WMI CPU Load v2 sensor. The sensor gives you full visibility into CPU utilization, both as an overall total and broken down per logical processor core, helping you quickly spot overloaded systems and identify uneven load distribution across cores. This sensor will also be supported on the upcoming Multi-Platform Probe for Windows.
You can now monitor how long a Windows system has been running since its last reboot with the new WMI System Uptime v2 sensor. Use it to detect unexpected reboots early and verify the stability and availability of your systems over time. This sensor will also be supported on the upcoming Multi-Platform Probe for Windows.
With this PRTG version, we introduce the new WMI Pagefile v2 sensor, which monitors the overall usage of the Windows paging file on a device. The sensor shows total pagefile usage in percent, helping you detect memory pressure situations and prevent performance degradation due to excessive paging. The sensor is compatible with the Classic Probe and will be supported on the Multi-Platform Probe for Windows.
We enforced input sanitization on sensor channel names to defend against possible Cross-Site Scripting (XSS).
We improved and sanitized the displayed data in Bad Request error dialogues that occur during data validation when you entered disallowed characters or invalid data.
We improved the log message that is logged in the Log tab when you pause an object indefinitely. Previously, the log message only displayed the status pausing. The log message now also displays paused when the process is finished.
We added an explicit Certificate Validation option to HTTPS-based sensors, giving you control over how strictly certificates are checked. The following sensor groups use strict validation that is now enabled by default: Cisco Meraki, Microsoft 365, Microsoft Azure, Cloud, and Zoom. These sensors will fail if they encounter an untrusted or manipulated certificate. The other sensor groups, as follows, keep the default accept any certificate so existing behavior is unchanged: DellEMC, Fortigate, HPE 3PAR, HTTP v2, NetApp, Orchestra, PRTG Data Hub, Proxmox, REST v2, Redfish, VMware, and Veeam. Please note that on Windows, the Cloud and Zoom sensors (now using strict validation) may fail if the intermediate CA certificate is not directly installed in the certificate store. This is a known limitation and might happen especially if you are using a deep inspection firewall manipulating the SSL certificates.
We updated the device template Printer (Generic) for printer sensors that is used during the Run Auto-Discovery with Template process to use the new SNMP Printer v2 sensor. Previously, the template only discovered and added the former SNMP Printer sensor after you ran an auto-discovery with the mentioned device template.
We improved the performance of the Traceroute Hop Count v2 sensor on Windows by switching from sequential pings to event-based response handling.
Various other minor fixes and improvements, updated user manual.
We fixed an issue for the Microsoft Azure SQL Database sensor where switching an Azure SQL Database to the Hyperscale service tier caused the sensor to fail with a BAD_REQUEST error. The sensor now works correctly on Hyperscale instances. Since Hyperscale does not report storage utilization the same way, the Data Space Used % channel is not shown for Hyperscale instances, while all other channels continue to work as before. Please note that switching an existing instance's service tier is not supported retroactively. If you change a database's tier, you will need to recreate the sensor.
We fixed an issue for the SNMP Library sensor where it was possible to select the entry Select a file in the Please select a library file pop-up window during sensor creation. Creating this sensor would fail with the error message Nothing was selected, no sensors could be created when you had selected this option.
We fixed an issue where the Processes table on the System Information tab remained empty when no SNMP credentials were configured, even though WMI was unavailable and SNMP was able to retrieve values. This issue occurred when you had configured the WSMan protocol for WMI connections before.
We fixed an issue for Device Settings where the Windows Compatibility Options section was displayed twice. The second, shorter section was an obsolete remnant from a previous implementation and was no longer functional. You will now only see one available Windows Compatibility Options section in the Device Settings again.
With this PRTG version, we deprecate the Enterprise Virtual Array sensor. You cannot create this sensor again if you update to PRTG 26.x.123; however, existing sensor instances continue to run. You will also receive an according To-Do ticket in PRTG.
With this PRTG version we discontinue the Common SaaS sensor. We announced the deprecation of the Common SaaS sensor with PRTG version 25.3.110. Please note that existing Common SaaS sensors will stop working when you update to this PRTG version. It is not possible to create a Common SaaS sensor anymore. For more information about sensor deprecation and discontinuation, please see our Knowledge Base article: What do deprecation and discontinuation in the context of a sensor mean?
You can verify the authenticity of the PRTG installer with the Secure Hash Algorithms for the following versions and release channels:
You can now monitor the health of hardware modules and PROFINET IO devices connected to your Siemens S7-1200/1500 PLC when you try out the experimental SIMATIC S7-1200/1500 Hardware Status (BETA) sensor. This sensor discovers the connected hardware tree via the S7 Web API and reports the status of each device and module—such as ET200SP stations, drive controllers, remote IO stations, and individual I/O modules—directly in PRTG. It complements the existing PLC CPU Status sensor by monitoring the external hardware attached to the CPU, so you can detect issues like remote IO power loss, module removal, or PROFINET communication problems even while the CPU itself keeps running. It requires PLC firmware V4.1 or higher and credentials for the S7 Web API.
You can now access Libraries directly from the main navigation menu in the New UI. The new Libraries entry is placed between Monitoring and Maps and loads the Libraries page in the main content area. The Management tab is visible to read/write users only. The History tab requires admin rights. The right-click context menu is available on Library and Library Node objects in the Overview tab only.
With this PRTG version, we introduce the new Dependencies view in the New UI, so you can review your objects' dependency tree without switching to the classic interface. A new Dependencies entry in the main navigation takes you to an overview page with three tabs — Overview, Selected Dependencies, and Master Dependencies — and you can click any object in the graph or tables to jump directly into its dependency view.
We fixed an issue where the mobile navigation header (hamburger menu) disappeared entirely when navigating into the Auto-Discovery Tasks module on a mobile device. The navigation header is now visible on all Auto-Discovery Tasks routes, so you can always open the main menu and navigate elsewhere, even though this module still shows a Not available on mobile message in the content area.
With this PRTG version, we introduce Insights, bringing the Top 10 Lists feature into the New UI. Insights appears as a new tab in the right-split layout monitoring view for Groups and Probes. From this view, every table link takes you to the Root Group's right-split layout monitoring view showing the correct sensor table, so you can move seamlessly from an overview straight into the relevant sensors.
We fixed an issue for Auto-update where in certain cases the step for uninstalling the PostgreSQL Database was not finished successfully. You could observe that update process was still running but did not finish, waiting for a message confirmation on preserving historic data in the UninstallPostgreSQL process. This issue could occur if you had a PRTG installation with the PostgreSQL database disabled and attempted to update to version 26.x.122 via auto-update.
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.1663
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 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 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