Paessler has released PRTG Network Monitor version 25.4.114 to the Stable Release Channel, reinforcing its focus on reliability, operational continuity, and enterprise-grade monitoring stability. Rather than introducing disruptive new features, this release prioritizes critical fixes and API enhancements that directly impact production environments.

For organizations running PRTG in live infrastructures—especially large-scale, regulated, or automation-driven setups—this update delivers tangible operational value.

Key Improvements in PRTG 25.4.114

1. Sensor Stability and Accuracy Enhancements

Windows Updates Status (PowerShell) Sensor

Following recent Microsoft updates (October 2025), some environments—particularly Windows Server 2025 and Windows 11—experienced sensor errors indicating missing update history.

What changed:
This issue has been fully resolved. The sensor now reliably retrieves update data again, preventing false alarms and unnecessary operational noise.

Why it matters:
Patch monitoring is a foundational requirement in enterprise and public-sector environments. This fix restores trust in update visibility and compliance monitoring.

VMware Datastore (SOAP) Sensor

In systems where the PRTG web interface was set to a non-English language, an additional invalid channel was created, showing no data and causing sensor errors.

What changed:
The sensor now behaves consistently across all UI languages, creating only valid and functional channels.

Why it matters:
Multinational and localized deployments benefit from predictable sensor behavior regardless of language settings, reducing troubleshooting overhead.

API v2 Enhancements: Enabling Smarter Automation

PRTG 25.4.114 introduces meaningful improvements to API v2, supporting advanced automation and integration use cases.

Programmatic Sensor Creation

EXE/Script sensors can now be created via a POST request using the experimental endpoint:

/experimental/devices/{id}/sensor

Impact:
This enables fully automated sensor lifecycle management, supporting Infrastructure as Code (IaC) approaches, CI/CD pipelines, and large-scale onboarding scenarios.

Improved API Security Visibility

Invalid API key requests are now logged in Web.log.

Impact:
Security teams and administrators gain improved auditability and faster troubleshooting for API-related access issues, aligning with enterprise security best practices.

Release Scope and Quality Focus

This stable release includes 53 resolved items, covering:

Bug fixes

Operational and maintenance tasks

Documentation improvements

Select feature enhancements

The emphasis is clear: production stability over experimental functionality.

Why This Release Matters for Enterprise PRTG Users

PRTG 25.4.114 is particularly relevant for organizations that:

Operate large or distributed PRTG environments

Depend on Windows patch monitoring for compliance

Use VMware extensively across localized deployments

Build automation and integrations using PRTG API v2

This update improves monitoring continuity, reduces false positives, and strengthens automation capabilities without introducing upgrade risk.

Final Thoughts

PRTG 25.4.114 is a pragmatic and mature release that aligns with real-world operational needs. For teams running PRTG in production—or planning deeper automation around API v2—upgrading to this stable version is strongly recommended.

If you would like guidance on:

Upgrade planning and validation

API v2–based automation design

Enterprise-scale PRTG architecture

feel free to reach out to our technical team.