WHD 2026.2.1 release notes
Release date: July 30, 2026
Here's what's new in WHD 2026.2.1. You can find the applicable system requirements here.
To view release notes, system requirements, and product guide PDFs for supported versions of WHD, see WHD previous versions. To view release notes for multiple versions
Attention WHD customers
WHD 2026.2.1 completes the migration of Web Help Desk to its completely redesigned modern interface. The classic interface is no longer available.
Important items to be aware of when installing or upgrading to 2026.2.1
-
WHD REST API is not available for WHD 2026.2.1. See Known issues.
-
CentOS 6 and 7 and RHEL 7 are not supported in WHD 2026.2.1. CentOS 9 and 10 and RHEL 9 and 10 are supported for a fresh installation of WHD 2026.2.1. For guidance on migrating your current settings, see Migrate legacy WHD with embedded PostgreSQL from one Linux machine to another.
-
WHD 2026.2.1 supports only macOS 13 and above. WHD instances running on older macOS versions are not supported. See System requirements.
-
If you are using a MySQL database on the backend, you need to download a new MySQL JDBC Driver for MySQL 8.0/8.4/9.x. See Install the MySQL JDBC Driver.
-
Microsoft deprecated the Exchange Web Services (EWS) API previously used by WHD to access and receive email from a Microsoft Exchange or Microsoft 365 mailbox. WHD now uses Microsoft Graph API. See Configure an incoming email account for Microsoft 365.
-
Servlet authentication is no longer available. Before upgrading to WHD 2026.2.1, review your current authentication method under Setup > General > Authentication. If it is set to Servlet authentication, plan your migration to SAML 2.0 or HTTP Header authentication prior to upgrade. Then, verify SSO functionality in the new environment before decommissioning your earlier instance. See Servlet authentication is not supported for more information.
-
To enable FIPS and to provide a CA-signed certificate for WHD 2026.2.1, see the instructions in Enabling FIPS 140-2 compliant cryptography.
-
If you are upgrading from WHD 2026.1, and you previously deployed SSO with CAS 2.0, you must update your IdP configuration; the Service Provider (SP) endpoints have changed. See Deploy SSO with CAS 2.0.
-
HTTPS is enabled by default in WHD 2026.2.1. HTTP access is not supported as a client access path. HTTP listener/redirect behavior (WHD_HTTP_PORT) is limited in this release.
-
Multiple instances of Web Help Desk are not currently supported.
-
Dameware integration is not currently supported.
-
After installation, if you receive a message stating Your connection isn't private, follow the instructions in Convert third-party SSL certificates after upgrading to WHD 2026.2.1.
New features and improvements in WHD
Completely redesigned modern interface
WHD 2026.2.1 features a completely redesigned user interface across 120+ screens, delivering a faster, cleaner, and more intuitive experience for both technicians and administrators. The new design improves navigation, readability, and overall usability while preserving every capability from the classic interface. WHD 2026.2.1 delivers the fully migrated application, including the complete tech interface, all administration and setup screens, and every feature from the classic application.
Interactive tech dashboard
A new customizable dashboard gives technicians an at-a-glance view of their workload:
-
Configurable chart widgets (bar and pie charts) for ticket metrics—by alert level, status, priority, alert condition, and request type
-
Live ticket activity feed showing recent updates across your assignments
-
Drag-and-drop layout with resizable widgets—arrange the dashboard for the way you work
-
Widget drawer for quickly adding or removing widgets
-
Saved search queries as dashboard widgets
Rich text editor with @mention
Techs now have access to a full-featured rich text editor for ticket notes and correspondence:
-
Format text using bold, italics, underline, strikethrough, headings, blockquotes, lists, and tables
-
Upload images, embed media, and attach files
-
Type @ to reference and notify technicians directly within notes
-
Add emojis, insert links, and customize fonts and colors
Multi-tab interface for admins and technicians
WHD 2026.2.1 introduces a multi-tab interface that allows administrators and technicians to open and work with multiple tickets simultaneously within a single browser window. This addresses one of the most requested improvements from the classic interface, where the single-tab constraint made it difficult to cross-reference related tickets or manage complex workflows.
Key capabilities include:
-
Tabbed navigation: Open multiple tickets, screens, or configuration pages as tabs within the same browser window, enabling efficient side-by-side work
-
Persistent sessions: Open tabs are retained across page refreshes, so your working context is never lost
-
Quick ticket referencing: Easily cross-reference and correlate information between related tickets without navigating back and forth
-
Improved multitasking: Handle interrelated issues, incident linking, and escalation workflows more efficiently with concurrent ticket access
Benefits include:
-
Faster ticket resolution times through improved contextual visibility
-
Reduced navigation overhead—no more switching back and forth between screens
-
Smoother handling of complex workflows involving multiple related tickets
SAML and CAS single sign-on
Full single sign-on support is now available in the modern interface:
-
SAML 2.0: Configure your identity provider (such as Okta, Azure AD, or ADFS) for seamless technician and client login. See Deploy SSO with SAML.
-
CAS: Central Authentication Service integration for organizations using CAS infrastructure. See Deploy SSO with CAS 2.0.
-
SSO configuration through the admin UI, including sign-in URL and certificate management.
Improved architecture and security
WHD 2026.2.1 introduces significant improvements to the underlying architecture. The improvements enhance security, performance, and ease of administration.
New reverse proxy for better security and performance
WHD now uses Caddy, a modern, high-performance HTTP server as its front-end entry point. This replaces the bundled Tomcat server used in previous versions and delivers several benefits:
| Benefit | What this means for you |
|---|---|
|
Faster page loads |
Support for HTTP/2 and HTTP/3 means pages and assets load significantly faster on modern browsers. |
|
Stronger default security |
Industry-standard security headers are applied to every response automatically — protecting against clickjacking, MIME sniffing, and other common attacks. |
|
Automatic compression |
All responses are compressed using modern algorithms, reducing bandwidth usage and improving load times. |
|
Built-in health monitoring |
WHD actively monitors the health of its services and responds immediately if a component becomes unavailable. |
|
Simpler SSL setup |
SSL/TLS certificates use standard PEM files instead of Java Keystores. Keytool commands are no longer needed. |
|
Smaller footprint |
The Caddy edge server uses less memory and starts much faster than the previous front-end stack. |
|
Automatic HTTPS redirect |
HTTPS is the supported access path for this release. HTTP listener/redirect behavior (WHD_HTTP_PORT, e.g., 80/8080) is limited due to a known Caddy issue. |
The following certificate options are available:
-
Self-signed certificate: Generated automatically during installation for immediate HTTPS access.
-
Your own certificate: Upload your organization's certificate and private key through the admin user interface.
-
Externally managed certificates: For internet-facing installations, WHD can automatically obtain and renew free certificates from Let's Encrypt. You can follow renewal workflow to refresh cert.pem and key.pem, then restart the WHD HTTP server service.
Security enhancements
WHD 2026.2.1 includes the following security improvements:
-
TLS 1.2 and TLS 1.3 only: Older, less secure protocol versions are no longer supported.
-
Strong cipher suites: Only modern, recommended cipher suites are enabled by default.
-
Security headers on every response: HSTS, content type protection, clickjacking prevention, and referrer control headers are applied automatically.
-
No server identification: Software version information is removed from responses to minimize information disclosure.
-
Internal services are not network-accessible: Only the HTTPS entry point is exposed. All other services are restricted to the local machine.
-
Smart static asset caching: Frequently accessed assets like images and scripts are cached efficiently, reducing server load while ensuring updated content is always delivered.
Service architecture
WHD 2026.2.1 runs as four managed services on your server, all installed and configured automatically. When using the embedded database, an additional PostgreSQL service is included.
| Service | Purpose |
|---|---|
| WHD HTTP server (Caddy) | Handles all incoming web traffic, SSL/TLS encryption, and routes requests to the appropriate service |
| WHD backend | Processes business logic, database operations, and authentication |
| WHD frontend | Renders the web interface and serves it to your browser |
| WHD database | Manages the embedded PostgreSQL database. Present only in embedded database installations. Data is stored under {WHD_HOME}/data/pgsql. |
All four services start automatically when the server boots, and they restart automatically on failure. You can manage them using your operating system's standard service tools (Windows Services, systemctl on Linux, or launchctl on macOS). For embedded database installations, the PostgreSQL service starts before the WHD backend service.
Fixed CVEs
At SolarWinds, we prioritize the swift resolution of CVEs to ensure the security and integrity of our software. In this release, we have successfully addressed the following CVEs.
SolarWinds CVEs
SolarWinds would like to thank our Security Researchers below for reporting on the issue in a responsible manner and working with our security, product, and engineering teams to fix the vulnerability.
This release also includes the fixes from 2026.2, which resolve the following issues:
- SolarWinds Web Help Desk Denial-of-Service Vulnerability
- pgAdmin4 Command Injection Vulnerability
- pgAdmin4 Remote Code Execution (RCE) Vulnerability
- pgAdmin4 LDAP Injection Vulnerability
- pgAdmin4 LDAP Authentication TLS Validation Bypass Vulnerability
See the details in the SolarWinds and third-party CVEs tables for more information.
| CVE-ID | Vulnerability Title | Description | Severity | Credit |
|---|---|---|---|---|
| CVE-2026-28299 | SolarWinds Web Help Desk Denial-of-Service Vulnerability | SolarWinds Web Help Desk is found to be affected by a denial-of-service vulnerability, which when exploited, could cause the Web Help Desk server to crash due to insufficient memory. | 8.2 High | Tenable |
| CVE-2026-28323 | SolarWinds SAML Authentication Bypass Vulnerability | SolarWinds Web Help Desk is found to be affected by a SAML authentication bypass vulnerability. This requires the SAML 2.0 authentication method to be enabled. | 9.8 Critical | Dhabaleshwar Das |
Third-party CVEs
| CVE-ID | Vulnerability title | Description | Severity |
|---|---|---|---|
| CVE-2025-12762 | pgAdmin4 Remote Code Execution (RCE) Vulnerability | pgAdmin versions up to 9.9 are affected by a Remote Code Execution (RCE) vulnerability that occurs when running in server mode and performing restores from PLAIN-format dump files. This issue allows attackers to inject and execute arbitrary commands on the server hosting pgAdmin, posing a critical risk to the integrity and security of the database management system and underlying data. | 9.8 Critical |
| CVE-2025-12763 | pgAdmin4 Command Injection Vulnerability | pgAdmin 4 versions up to 9.9 are affected by a command injection vulnerability on Windows systems. This issue is caused by the use of shell=True during backup and restore operations, enabling attackers to execute arbitrary system commands by providing specially crafted file path input. | 8.8 High |
| CVE-2025-13780 | pgAdmin4 Remote Code Execution (RCE) Vulnerability | pgAdmin versions up to 9.10 are affected by a Remote Code Execution (RCE) vulnerability that occurs when running in server mode and performing restores from PLAIN-format dump files. This issue allows attackers to inject and execute arbitrary commands on the server hosting pgAdmin, posing a critical risk to the integrity and security of the database management system and underlying data. | 8.8 High |
| CVE-2025-9636 | pgAdmin4 Cross-Origin Opener Policy (COOP) Vulnerability | pgAdmin <= 9.7 is affected by a Cross-Origin Opener Policy (COOP) vulnerability. This vulnerability allows an attacker to manipulate the OAuth flow, potentially leading to unauthorised account access, account takeover, data breaches, and privilege escalation. | 7.9 High |
| CVE-2025-12764 | pgAdmin4 LDAP Injection Vulnerability | pgAdmin <= 9.9 is affected by an LDAP injection vulnerability in the LDAP authentication flow that allows an attacker to inject special LDAP characters in the username, causing the DC/LDAP server and the client to process an unusual amount of data DOS. | 7.5 High |
| CVE-2025-12765 | pgAdmin4 LDAP Authentication TLS Validation Bypass Vulnerability | pgAdmin <= 9.9 is affected by a vulnerability in the LDAP authentication mechanism allows bypassing TLS certificate verification. | 7.4 High |
Fixed customer issues
| Case number | Description |
|---|---|
| 02151990 | Tickets created through an Incoming Mail Account are now automatically assigned to the correct technician. |
| 02149151, 02151318 | Users can now log in successfully via Azure SSO after upgrading to WHD 2026.2. |
| 02146929, 02152231, 02152763, 02146421 | Users authenticating via SAML ADFS can now log in successfully without encountering an authentication error. |
| 02153498, 02148014, 02149937, 02147567, 02149834, 02149636, 02155972, 02148479, 02148957, 02149695, 02148342, 02146229, 02147225, 02153542, 02149336, 02148552, 02151318, 02152709, 02146421, 02149038, 02157373, 02155833 | Upgrading from a WHD 2026.1 correctly preserves network settings from 2026.1 instead of resetting to defaults. |
| 02151056, 02153791, 02153797 | Custom labels and multi-language display settings now work correctly. |
| 02147731, 02149017, 02149834, 02149834, 02148503, 02148479, 02155972, 02147577, 02146792, 02153798, 02151608, 02152229, 02149412, 02151318, 02155505, 02146421, 02155833 | The existing trusted HTTPS certificate is preserved instead of being replaced with a self-signed certificate during upgrade or repair. |
| 02147247 | Google SSO now works as expected. |
| 02152795 | Gmail OAuth incoming and outgoing mail accounts now work correctly for ticket creation and updates. |
| 02147817, 02148182, 02153498, 02149983, 02154826 | Client records now appear correctly in the Client List after a successful AD/LDAP connection sync. |
| 02149825, 02153613, 02152066 | When the Request Type is changed at runtime before saving the ticket, technicians are now correctly auto-assigned. |
| 02149788 | Technician notes can now be deleted from a ticket. |
| 02148028, 02151333 | The Client Login option now correctly retains its previously configured value after upgrading. |
| 02146911, 02147817, 02152066, 02149980, 02149863 | Ticket actions submitted via email replies are now correctly recognized and processed by the Incoming Mail Account. |
| 02151096, 02147593, 02146362, 02148381, 02148272, 02149096, 02145930, 02146609, 02148679, 02149495, 02155886, 02149943, 02149943, 02148266, 02147349, 02156836, 02151764, 02149173, 02146725, 02149154, 02159465, 02153064, 02158188, 02149412, 02157373, 02151333, 02159085 | WHD no longer returns an error when logging in immediately after startup. |
| 02148934, 02151572, 02148265, 02148570, 02149378, 02148758, 02153498, 02148539, 02149937, 02148479, 02153613, 02149980, 02149863, 02152066, 02152232, 02153791, 02154049, 02153797, 02149191, 02151990, 02148244 | All ticket statuses are now available in the status dropdown after a ticket has been created. |
| 02116762 | Upgrading from version 12.8.6 to 12.8.8 occurs without errors. |
| 02149136, 02146367, 02156994, 02159695 | Upgrading to WHD 2026.2 occurs without errors. |
Installation instructions
For new installations, you can download the installer from the SolarWinds website or from the Customer Portal. For more information, see the WHD Installation and Upgrade Guide.
For upgrades, if you are upgrading from a version earlier than 2026.1, first upgrade to 2026.1 and verify WHD functionality. Then upgrade to version 2026.2.1.
See Upgrade WHD for supported upgrade paths.
Uninstallation instructions
If you install WHD 2026.2.1 and you would like to revert to a previous version, take the following steps:
-
Uninstall WHD 2026.2.1.
-
Install your previous version.
-
If using FIPS, follow the instructions for enabling FIPS.
Known issues
The WHD REST API is unavailable
The Web Help Desk REST API is not available with version 2026.2.1.
Resolution or workaround: The API will be available in a future version.
Servlet authentication is not supported
Servlet authentication is not supported in WHD 2026.2.1.
Recommended alternative: Customers requiring single sign-on should migrate to SAML 2.0, which provides a standards-based, fully supported SSO experience with identity providers such as AD FS, Okta, Azure AD, and others. For environments using HTTP-based pre-authentication (for example, reverse proxy with Kerberos/NTLM), the HTTP Header authentication method remains available.
| Previous method | Recommended migration path |
|---|---|
| WAFFLE SSO (Negotiate/NTLM) | SAML 2.0 with AD FS, Azure AD, Okta, or another IdP that supports Integrated Windows Authentication (IWA) |
| CAC authentication via WAFFLE | SAML 2.0 with a CAC-aware IdP, or HTTP Header authentication behind a reverse proxy performing certificate-based pre-authentication |
Servlet authentication is no longer available. Before upgrading to WHD 2026.2.1, review your current authentication method under Setup > General > Authentication. If set to Servlet authentication, plan your migration to SAML 2.0 or HTTP Header authentication prior to upgrade. Verify SSO functionality in the new environment before decommissioning your earlier instance.
High availability deployments are not supported
In previous versions, high availability WHD deployments were configured using a multi-instance Tomcat deployment. That option is not available in WHD 2026.2.1.
Resolution or workaround: High availability deployments will be available in a future version.
Embedded database behavior in WHD
Database behavior varies based on whether you upgrade to WHD 2026.2.1 with an embedded database or perform a fresh installation. See the WHD Installation and Upgrade Guide.
End of life
| Version | EoL announcement | EoE effective date | EoL effective date |
|---|---|---|---|
| 12.8.8 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.8.8 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.8.8 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.8.8. |
| 12.8.7 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.8.7 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.8.7 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.8.7. |
| 12.8.6 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.8.6 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.8.6 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.8.6. |
| 12.8.5 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.8.5 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.8.5 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.8.5. |
| 12.8.4 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.8.4 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.8.4 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.8.4. |
| 12.8.3 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.8.3 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.8.3 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.8.3. |
| 12.8.2 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.8.2 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.8.2 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.8.2. |
| 12.8.1 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.8.1 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.8.1 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.8.1. |
| 12.8 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.8 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.8 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.8. |
| 12.7.13 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.7.13 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.7.13 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.7.13. |
| 12.7.12 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.7.12 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.7.12 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.7.12. |
| 12.7.11 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.7.11 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.7.11 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.7.11. |
| 12.7.10 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.7.10 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.7.10 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.7.10. |
| 12.7.9 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.7.9 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.7.9 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.7.9. |
| 12.7.8 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.7.8 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.7.8 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.7.8. |
| 12.7.7 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.7.7 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.7.7 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.7.7. |
| 12.7.6 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.7.6 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.7.6 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.7.6. |
| 12.7.5 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.7.5 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.7.5 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.7.5. |
| 12.7.4 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.7.4 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.7.4 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.7.4. |
| 12.7.3 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.7.3 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.7.3 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.7.3. |
| 12.7.2 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.7.2 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.7.2 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.7.2. |
| 12.7.1 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.7.1 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.7.1 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.7.1. |
| 12.6 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.6 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.6 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.6. |
| 12.5.2 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.5.2 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.5.2 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.5.2. |
| 12.5.1 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.5.1 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.5.1 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.5.1. |
| 12.5 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.5 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.5 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.5. |
| 12.4.2 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.4.2 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.4.2 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.4.2. |
| 12.4 | June 2, 2026: End-of-Life (EoL) announcement – Customers on WHD version 12.4 or earlier should begin transitioning to the latest version of WHD. | July 4, 2026: End-of-Engineering (EoE) – Service releases, bug fixes, workarounds, and service packs for WHD version 12.4 or earlier will no longer actively be supported by SolarWinds. | November 30, 2026: End-of-Life (EoL) – SolarWinds will no longer provide technical support for WHD version 12.4. |
See the End of Life Policy for information about SolarWinds product life cycle phases. To see EoL dates for earlier WHD versions, see WHD release history.
Legal notices
© 2026 SolarWinds Worldwide, LLC. All rights reserved.
This document may not be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the prior written consent of SolarWinds. All right, title, and interest in and to the software, services, and documentation are and shall remain the exclusive property of SolarWinds, its affiliates, and/or its respective licensors.
SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS, OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON THE DOCUMENTATION, INCLUDING WITHOUT LIMITATION NONINFRINGEMENT, ACCURACY, COMPLETENESS, OR USEFULNESS OF ANY INFORMATION CONTAINED HEREIN. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY, EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of SolarWinds Worldwide, LLC or its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be common law marks or are registered or pending registration. All other trademarks mentioned herein are used for identification purposes only and are trademarks of (and may be registered trademarks) of their respective companies.