WhatsUp Gold 2026.0 Release Notes
- Last Updated: April 2, 2026
- 15 minute read
- WhatsUp Gold
- Version 2026
Release Notes for WhatsUp Gold 2026.0
We're excited to announce the features and enhancements implemented in version 26.0 of WhatsUp Gold. Customers helped choose and validate many of the features that went into this release, and we want to hear from you to continue to improve WhatsUp Gold. Thank you for helping make WhatsUp Gold better!
- v2026.0.0 - APR 02 2026
Introduction
We love your feedback
We love hearing from customers! Please join or start a discussion on the WhatsUp Gold Community, request to join and participate in pre-release activities on the Customer Validation Program (CVP), and vote on and submit your product ideas on our ideation portal.
Additional resources
-
For information on the minimum supported versions, patching/upgrade suggestions, and feature/function obsolescence, see the Product Compatibility Guide.
-
For information on how Technical Support can help you, see the Scope of Support.
-
For information on how product security is managed, see the Security Guidelines.
-
For information on what is needed to operate WhatsUp Gold, see the System Requirements.
What's New
The following features have been implemented or improved in the latest version of WhatsUp Gold:
This version of WhatsUp Gold introduces a new encryption mechanism based on a Master Secret Key. The Master Secret Key is generated during installation or upgrade to this version of WhatsUp Gold. Please note, this key is unique to each WhatsUp Gold server. Additionally, a dedicated application is installed with WhatsUp Gold which allows you to manage your Master Secret Key when moving your WhatsUp Gold instance from one server to another. Important considerations:
- Secure storage. The Master Secret Key must be stored in a safe location separate from the WhatsUp Gold server.
- Server migration. The Master Secret Key is required to successfully migrate the WhatsUp Gold database from one server to another.
- Loss. The Master Secret Key is required for database migration and post-recovery access. Loss of this key may prevent recovery of encrypted data.
This enhancement follows modern security best practices and aligns with evolving expectations in today’s security conscious environment. Implementation of the Master Secret Key ensures stronger protection for sensitive data and helps safeguard your monitoring environment against unauthorized access.
Certificate Discovery and Reporting
WhatsUp Gold can now discover certificates on your network and also introduces the ability to report on that data. First, Discovery scans specified IP addresses and ports to identify SSL/TLS certificates and gather rich certificate metadata, including subject, issuer, serial number, timestamps, effective/expiration dates, and whether a certificate is self-signed. This information is presented using new, dedicated inventory and dashboard reports. Beyond capturing certificate attributes, WhatsUp Gold also identifies every way a certificate can be reached, e.g., IP address, DNS hostname, or multiple URLs on the same port. This ensures full visibility into certificate exposures across your environment.
Scan Device Card
Much like the device information cards accessible through the Discovered Network and My Network views, the Scan Results report allows access to a new device details dialog specific to a selected device's discovery. Click on any line item in the Scan Results report to launch the card displaying these key device details gathered during Discovery.
Rescan/Refresh/Reset Improvements
Enhancements have been made to the device rescan, refresh, and reset device and device group management menu options. These changes were implemented for clarity for the user as well as to better align with what WhatsUp Gold is actually doing when any of these options are selected. Please note, no actual functionality has been modified or removed; these enhancements apply to new and updated term usage and associated descriptions within the user interface and accompanying user documentation. Applicable changes are as follows:
- Basic Rescan replaces the Refresh Device Details option present in previous versions of WhatsUp Gold. Selecting this option performs a standard refresh of the device using current Discovery results. Performing a basic refresh adds new roles and/or subroles if the device matches specified scan criteria and automatically applies monitors and attributes associated with newly-detected roles. However, any existing roles and/or monitors remain unchanged if they no longer match scan criteria.
- Advanced Rescan replaces the Include user-defined roles control present in previous versions of WhatsUp Gold. Selecting this option is similar to performing a basic refresh, but it also updates monitors based on the device's assigned roles and subroles. Performing an advanced refresh can apply monitors and attributes to a device even if it does not match current scan criteria.
Update Inventory Data replaces the Remove Stale Data control present in previous versions of WhatsUp Gold. Selecting this option removes and rescans inventory data for a selected time period and applies the most recent device data available. Updating inventory data can improve role calculation, map information, reporting, and other related areas in WhatsUp Gold.

- Reset/Replace Device is a new dialog which can be used in two specific
scenarios:
Select Replace Device if you intend to replace the selected device with the same or similar device and intend to keep the same IP address. Replacing a device removes and re-evaluates device data such as its display name, SNMP OID, operating system, brand, role, subrole, etc. It can also make changes to role-based attributes, custom IP addresses, inventory data, and MAC address.

Select Reset Device if you intend to completely reset the device in WhatsUp Gold. Resetting a device deletes all monitoring and reporting data and removes and re-evaluates all monitors and attributes.

Hirschmann Device Support
In this release, WhatsUp Gold has introduced support for Hirschmann devices in the form of a new subrole. Discovery will automatically detect and configure Hirschmann devices that have a sysObjectID that starts with: '1.3.6.1.4.1.248'. WhatsUp Gold will automatically configure and apply some active and performance monitors for applicable devices with the new subrole upon discovery.
Updated and Improved
Updated and Improved in v26.0
| Feature Area | Item | Description |
|---|---|---|
| Device Groups | WUG-1447 |
Fixed an issue where deleting a device group assigned as a user’s home group returned a generic failure message instead of indicating that the group was set as a home group. |
| Actions | WUG-1901 | Fixed an issue where SMTP action passwords containing a € character were not saved to the database, causing the password field to be blank when reopening the action. |
| API | WUG-10953 | Fixed an issue where the REST API endpoint /api/v1/devices/{deviceId}/reports/disk-utilization did not return a LastPolled value. |
| Maps | WUG-13358 |
Fixed an issue where custom map images and annotations on Custom Map layouts were not persistent, disappearing after refresh or navigation, or incorrectly pulling images from other maps. |
| API | WUG-14291 | Fixed an issue where the API could not move a dynamic layer 2 device group under a different parent group, even though the request was reported as successful. |
| Device Management Actions | WUG-15117 | Fixed an issue where right-clicking the Unacknowledged dynamic group and choosing “Acknowledge All Devices” did not clear devices in the group. |
| Configuration Management | WUG-16719 | Fixed an issue where telnet-based backup scripts for certain switches failed at login following upgrade. |
| Alert Center | WUG-16822 |
Fixed an issue where creating a new Syslog Alert Center notification provided no validation feedback, leaving users unsure which fields or tabs were required before saving. |
| Credentials | WUG-16918 | Fixed an issue where weak client and server SSH algorithms triggered security scan findings. |
| User Interface | WUG-17161 |
Fixed an issue where adjusting the Device column in the Down Active Monitors was not remembered. |
| User Interface | WUG-17233 | Fixed an issue with Dark Mode where the WhatsUp Database Size widget showed black text on a dark background. |
| Reports | WUG-17640 | Fixed an issue where Device Health scheduled reports in CSV/XML failed to display human-readable device names. |
| Logs | WUG-17674 | Fixed an issue where cleanup of expired DeviceStateChangeLog data failed after upgrade, leading to repeated errors and service instability. |
| User Rights | WUG-17678 | Fixed an issue where an LDAP user with device group access rights enabled and Administrators membership could not add devices to be monitored. |
| Certificates | WUG-17681 |
Fixed an issue where the REST API SSL certificate on port 9644 used by ISS was unnecessarily replaced during upgrade with a newly generated certificate. |
| Discovery | WUG-17684 |
Fixed an issue where devices were incorrectly merging. |
| Configuration Management | WUG-17719 | Fixed an issue where configuration backups were saved to the database but failed to write configuration files to disk. |
| User Interface | WUG-17720 |
Fixed an issue where incorrectly formatted role names would not display properly. |
| Wireless | WUG-17728 |
Fixed an issue where remote login connections using the built‑in client failed with memory size errors, requiring manual client switching. |
| Alert Center | WUG-17731 |
Fixed an issue where Alert Center error logs showed Error= An item with the same key has already been added. |
| Discovery | WUG-18243 |
Fixed an issue where discovery was hanging. |
| User Interface | WUG-18248 | Fixed an issue where default error messages failed to display user-friendly error text. |
| Services | WUG-18263 | Fixed an issue where the networkviewerdataservice crashed. |
| Upgrade | WUG-18304 | Fixed an issue where users could not log in after upgrade. |
| Monitors | WUG-18369 | Fixed an issue where SNMP Table Monitors did not create entries for all interfaces visible in a full SNMP MIB walk. |
| Services | WUG-18428 |
Fixed an issue where NmDataCollector folders under \Ipswitch\WhatsUp\Data were not being cleaned up. |
| Reports | WUG-18453 | Fixed an issue where TxSpeed filters required incorrectly scaled values, preventing accurate filtering in interface utilization reports. |
| Wireless | WUG-18461 | Fixed an issue where Cisco 9200 series switch interfaces displayed incorrect status. |
| Security | WUG-18666 | Fixed an issue where obsolete ASP.NET components and the CiscoCollab data folder remained after install or upgrade, triggering security scan findings. |
| Wireless | WUG-18669 |
Fixed an issue where some Cisco 2811 routers showed incorrect SNMP community strings during discovery. |
| Reporting | WUG-18681 | Fixed an issue where filtering reports by multiple IP groups returned no results, preventing aggregate traffic reporting. |
| Inventory | WUG-18711 |
Fixed an issue where Inventory did not display all IP routes due to Refresh/Rescan profiles not correctly inheriting SkipIpRouteTable settings. |
| Reports | WUG-18730 |
Fixed an issue where Live View reports mapped NTA threshold violations to the wrong device based on IP associating them with devices in different locations. |
| Monitors | WUG-18765 | Fixed an issue where a REST API monitor could authenticate to the root of a Redfish device but failed with 401 errors when accessing deeper sub-resource paths. |
Known Issues
| Feature Area | Item | Description | Workaround | Applicable Release Version(s) | Fixed Release Version |
|---|---|---|---|---|---|
| Reporting | WUG-19216 |
In the Certificates report (and other pages that use the shared device picker), changing the device filter may not update the active selection, causing the report to continue using a previously selected device even after choosing All Devices or a different node. As a result, the report can appear empty or fail to show the expected devices until you explicitly select another node and then reselect the desired scope. |
None | 26.0 | N/A |
| Log Management | WUG-18903 |
Agent client builds using Go versions higher than 1.16.7 may fail to connect to WhatsUp Gold due to an incorrect flag in the agent certificate. |
Existing installations may need to regenerate agent certificates from the Agent General Settings dialog, which will trigger a redeploy of all current agents. |
26.0 | N/A |
| Certificates | WUG-19448 |
Devices discovered and monitored in WhatsUp Gold 25.x do not have their existing certificate data migrated into the new certificate tables after upgrading to 26.0, so certificate information may be visible under Device Properties → Monitors but not in Inventory or Dashboard reports. |
To populate certificate data in these reports, you must re-discover affected devices in 26.0 and then start or update certificate monitoring. |
26.0 | N/A |
Things You Should Know
Please also see the following additional WhatsUp Gold documentation:
System Requirements
Hardware requirement guidelines
Hardware requirements vary depending on the WhatsUp Gold configuration. Increasing the number of devices monitored, number of monitors, types of monitors, polling intervals, or other configuration options can result in additional load on the server and database. Hardware configuration adjustments may be required to optimize performance for your network.
Minimum and recommended server requirements
|
Up to 100 Devices / 500 Metrics* |
Up to 2,500 Devices / 12,500 Metrics* |
Up to 20,000 Devices / 100,000 Metrics* |
||||
| Minimum / Recommended | Minimum / Recommended | Minimum / Recommended | ||||
|
Processor(s) |
Quad-core / Octa-core |
Quad-core / Octa-core |
Quad-core / Octa-core |
|||
|
Processor speed |
2.6 GHz or more |
2.6 GHz or more |
2.6 GHz or more |
|||
|
RAM |
8GB / 12GB |
16GB / 24GB |
WhatsUp Gold Server: 16GB / 24GB Dedicated SQL Server: 32GB / 64GB |
|||
|
Database type |
SQL Server 2022 Express Edition |
Dedicated SQL Server 2017/2019/2022 |
Dedicated SQL Server 2017/2019/2022 |
|||
|
Hard drive |
25 GB or more free space |
OS/Application - 15 GB or more free space in RAID 1 Database files - 4 x 100 GB in RAID 10 |
OS/Application - 15 GB or more free space in RAID 1 Database files - 8 x 250 GB in RAID 10 Log files - 2 x 100 GB in RAID 0 Temp database files - 2 x 250 GB in RAID 0 For more information about moving SQL Server database and log files, see How to migrate the WhatsUp Gold database. |
|||
|
Network interface card |
Minimum 100 Mbps (1 Gbps preferred) |
100 Mbps (1 Gbps preferred) |
1 Gbps |
|||
|
Sound card |
SAPI-capable sound card required for Text-to-Speech actions |
SAPI-capable sound card required for Text-to-Speech actions |
SAPI-capable sound card required for Text-to-Speech actions |
|||
* Each data point stored in the database counts as a metric, and WhatsUp Gold may collect more than one metric per monitor.
Recommendations for accessing WhatsUp Gold
We recommend accessing the WhatsUp Gold server using a browser installed on a remote machine. The following specifications are recommended for optimal performance when accessing the WhatsUp Gold server.
|
100 Devices / 500 Metrics minimum required |
2,500 Devices / 12,500 Metrics minimum required |
20,000 Devices / 100,000 Metrics minimum required |
|
|
RAM |
8 GB |
8 GB |
16 GB |
|
Processor |
Quad-core |
Quad-core |
Quad-core |
|
Video display resolution |
1920x1080 or higher |
1920x1080 or higher |
1920x1080 or higher |
|
Sound card |
SAPI-capable sound card required for Text-to-Speech actions |
SAPI-capable sound card required for Text-to-Speech actions |
SAPI-capable sound card required for Text-to-Speech actions |
Within the product, there is no hard-coded limit to the number of logged-in users. The maximum number of concurrent users will depend on IIS limits and the system’s available resources.
Operating system requirements
WhatsUp Gold supports the following Windows Server platforms:
- Microsoft Windows Server 2025
- Microsoft Windows Server 2022
- Microsoft Windows Server 2019
Please note:
- Installing WhatsUp Gold on a domain controller is not recommended or supported.
- If WhatsUp Gold is hosted in virtual environments, to prevent licensing issues, make sure that you assign a static MAC address to the virtual machine on which WhatsUp Gold is operating. Refer to your virtual machine software help documentation for information about assigning a static MAC address for the virtual machine.
- WhatsUp Gold requires quad-core processors @ 2.6 GHz (min). If you are installing WhatsUp Gold on a virtual machine, make sure that your guest VM has at least four CPU cores allocated to it. Refer to additional Hardware requirements guidelines.
Database requirements
SQL_Latin1_General_CP1_CI_AS.
Latin1_General_CI_AS collation is allowed during upgrades, but is
not recommended as it could cause errors in operation. Additionally, the collation of
each of the aforementioned WhatsUp Gold databases should also be set to
SQL_Latin1_General_CP1_CI_AS.Latin1_General_CI_AS
collation is allowed during upgrades, but is not recommended as it could cause errors in
operation.WhatsUp Gold requires a database to maintain data about monitored devices, store system configurations, and save user specified customizations. The database may be co-located with the WhatsUp Gold installation, or may be hosted on a remote machine. Data services for WhatsUp Gold can be provided by the following database servers. The following database versions are supported:
- Microsoft SQL Server 2017
- Microsoft SQL Server 2019
- Microsoft SQL Server 2022
Web server requirements
The WhatsUp Gold installer automatically installs/enables IIS on platforms where it is supported.
WhatsUp Gold requires the following Web Server Role Services for IIS at a minimum:
- Web Server
- ASP .NET
- Static Content
- HTTP Redirection
- Default Document
Framework requirements
WhatsUp Gold requires the Microsoft .NET Framework and other Microsoft packages for scripting. The following are required software framework and support packages:
- .NET 4.8, included in installation program.
- PowerShell 2.0 (Optionally required for PowerShell scripting. Not included in the WhatsUp Gold installer. Refer to the Microsoft MSDN web site for more information about installing PowerShell).
- Microsoft Windows Scripting Host v5.7 (or later).
- Microsoft SAPI 5.1 (required for Text-to-Speech actions).
Web interface requirements
The following web browsers are currently supported for use with WhatsUp Gold:
- Microsoft Edge
- Google Chrome
- Mozilla FirefoxTip: WhatsUp Gold does not support any version of Internet Explorer in Compatibility or Quirks mode.
Log Management Requirements
The WhatsUp Gold Log Management feature collects log data from monitored devices and stores that data for reporting and analysis in an Elasticsearch database. You must install and configure Elasticsearch to utilize WhatsUp Gold Log Management. Please ensure to use a supported Elasticsearch release, such as major version 8 or major version 7.
The minimum system requirements for the server hosting Elasticsearch instance:
- CPU speed >= 2.6 GHz
- CPU count >= 8 cores
- RAM >= 16 GB
- Disk space >= 200 GB
Poller requirements
Depending on the network environment and product deployment, WhatsUp Gold can poll up to 100,000 metrics with one WhatsUp Gold server and additional pollers. Additional pollers installed on your WhatsUp Gold system transmit active monitor and performance monitor data to the WhatsUp Gold server. Extending polling activity across multiple pollers increases the number of devices for which WhatsUp Gold can poll and collect data to send back to the WhatsUp Gold system. Using additional pollers, WhatsUp Gold can efficiently scale polling operations to a larger number of network devices, ultimately providing the capacity to monitor and manage larger networks. Additional pollers may be installed on any Windows system on the network, other than the WhatsUp Gold server.
Minimum requirements for each additional poller:
| Processor(s) |
Quad-core |
| RAM |
4 GB |
| Hard drive space for application |
2 GB |
| OS requirements |
See Operating system requirements section above |
Installing WhatsUp Gold
To maintain adequate operation and security protection for your WhatsUp Gold deployment, we recommend the following:
- Install WhatsUp Gold and any components in a locked server room or cabinet so that physical access is restricted to trusted administrators.
- Install WhatsUp Gold software components on dedicated servers. Do not use these servers for any other purpose.
This version of WhatsUp Gold supports direct upgrade installations from WhatsUp Gold v22.1.0 and newer. If you are running an earlier version of WhatsUp Gold, you must first upgrade to v22.1.0 before installing the latest version of WhatsUp Gold. Make sure to clear the browser cache so the user interface displays the new web application pages after the upgrade. As always, before performing an upgrade be sure to back up your database. If you are using the SQL Express database included in WhatsUp Gold, this can be done by the installer/updater before proceeding with the upgrade. Refer to the Installing WhatsUp Gold guide for details about installation, upgrade, repair, and uninstall.
Offline Installation and Activation
End of life information
To see the list of currently supported versions of WhatsUp Gold, please refer to the Product Life Cycle page.
Copyright notice
Visit the following page online to see Progress Software Corporation’s current Product Documentation Copyright Notice/Trademark Legend: https://www.progress.com/legal/documentation-copyright.