We've just released PRTG version 25.4.114 to the stable release channel.
This version brings you important fixes for the Windows Updates Status (PowerShell) sensor and the VMware Datastore (SOAP) sensor, as well as an extended grace period for license renewals and new capabilities in the PRTG API v2.
Here's what's new and improved in this release:
Sensor fixes and improvements
🧩 Windows Updates Status (PowerShell) sensor fix
If you've been running into issues with the Windows Updates Status (PowerShell) sensor recently, we've got you covered. Some of you reported an error after the latest Windows update from October 14th, 2025. The sensor displayed the message "Update history does not contain any entries. Please enable the sensor debug options and contact support for further help" on Windows Server 2025 or Windows 11 target systems.
This issue is now resolved, and the sensor will work reliably again.
🧩 VMware Datastore (SOAP) sensor fix
We fixed an issue for the VMware Datastore (SOAP) sensor that affected users who had set their PRTG interface to a different language than English - for example, German or Spanish. In these cases, the sensor created an extra non-functioning channel that didn't deliver any values and therefore generated an error status, while the actual Free Space channel continued to function.
With this update, only the correct channels will be created, regardless of your language settings.
PRTG API v2 enhancements
API users, we've got something for you too! You can now create an EXE/Script sensor via POST request on the /experimental/devices/{id}/sensor endpoint. This gives you more flexibility when automating your monitoring setup.
Additionally, the Web.log will now create log entries for requests with invalid API keys that were executed on API v2. This makes it easier for you to troubleshoot authentication issues and keep track of API usage.
Check our PRTG release notes
In summary, PRTG 25.4.114 includes 53 resolved issues, including 2 implemented features and stories, 10 bug fixes, 18 completed tasks & to-dos, and 21 finished documentation tickets. For all the details, take a look at our release notes page.
We also offer a public roadmap of PRTG on our website, which we update regularly. There you can read which features we are currently working on and what kind of things we want to implement in PRTG in the future.
Published by