After kb4494440 was installed, our PRTG server CPU spiked to 100% and stayed there until we removed the update. Most of the CPU time was from MS SQL sensors (v2) and Powershell scripts running from PRTG sensors. Has anyone else has this issue?
Microsoft security update kb4494440 caused problems for PRTG
Votes:
0
10 Replies
Votes:
0
Hi Peter,
We've indeed seen this with other customers and are currently evaluating the issue. For the time being, please remove the update to restore previous performance. Note that KB4495590 might cause a similar behavior. Since you mentioned a different update, is PRTG Server.exe or PRTG Probe.exe experiencing causing a high load?
PRTGapi |
Feature Requests |
WMI Issues |
SNMP Issues
Kind regards,
Stephan Linke, Tech Support Team
Created on Jun 5, 2019 8:25:29 AM by
Stephan Linke [Paessler Support]
Last change on Jun 5, 2019 8:38:51 AM by
Stephan Linke [Paessler Support]
Votes:
0
Neither PRTG Server.exe or Probe.exe were using high CPU. It was entirely the MS SQL v2 sensors and Powershell scripts, being run from sensors.
Votes:
0
Thanks for the update, that helps narrowing it down. Much appreciated!
PRTGapi |
Feature Requests |
WMI Issues |
SNMP Issues
Kind regards,
Stephan Linke, Tech Support Team
Votes:
0
To clarify, this was happening on one of our Remote Probes. The patch has not (yet) been installed on any other probes, or the core server, to my knowledge.
Votes:
0
Thanks for the update on this one :)
PRTGapi |
Feature Requests |
WMI Issues |
SNMP Issues
Kind regards,
Stephan Linke, Tech Support Team
Votes:
0
Just a quick update that I opened up a developer ticket for this for investigation, in case we can do anything about it that is.
Votes:
0
We just had the same problem with another update - KB4505052 I'm really not sure what's happening here. Do these updates all have some of the same code that's breaking PRTG?
This seems really bizarre.
Votes:
0
Thanks for the update on this one, I'll add it to the list - that makes three updates that don't behave with PRTG. I hope that eases pinpointing the actual issue here. Perhaps we need to build our Sensors against a different .NET version or something like that...
Votes:
0
Thanks for updating on this so frequently, it's much appreciated!
Add comment