Solutions

winmgmt.exe slowly uses more and more virtual memory - hotfix981314 did not help

Modified on 2025-06-10 13:36:12 +0200

Hello folks,

I'm hoping someone can help me solve an issue we are seeing on the server we have running PRTG. We are using a Windows 2008 R2 server, and are seeing an increasing amount of memory usage coming from winmgmt.exe. At the current moment, it is utilizing near 500mb.

I have researched this issue and found two hotfixes (KB981314 and KB977357), however, we have applied both hotfixes and neither have fixed the issue.

Any ideas?

Thank you! -Tom

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Other than those hotfixes and doing some googling, we really cannot say any more than what you have already found. WMI is such a complex beast that you may have to contact Microsoft as I stated in the other KB article. Have you tried to move your monitoring to another server and stopping PRTG to see if that's the cause?

Does the other server then experience the same issue?

Sep, 2014 - Permalink

Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.

winmgmt.exe slowly uses more and more virtual memory - hotfix981314 did not help

Article CommentsAttention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Search

Attention

Related Articles

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.