As explained in this previous question, I'm dealing with some serious WMI issues. Now one of the options I'd like to explore is the maximal frequency of WMI queries, if any:

Imagine a WMIPrvSE.exe process goes down, due to a quota overflow, is there a minimum time I need to wait before launching a new WMI request, or is a new WMIPrvSE.exe process started up, in order to handle my new request?

  • Have you already tried adjusting or looking over "Increase WMI Quota properties to maximum values" to see if it helps much? Otherwise have you considered scripting a forceful stop of the winmgmt service when the issue occurs? You might have to script out the stop of dependent processes first and then then stop the winmgmt service all elevated as admin. Just a quick thought for a potential workaround. – Pimp Juice IT Apr 15 at 18:06
  • @PimpJuiceIT: sorry for the late reply, but we can't increase WMI quota anymore: this has already been done in the past and I'm afraid this would just cause the quota overflow to appear less frequently, while we are looking for a way to avoid them completely. – Dominique Apr 16 at 13:51
  • As per the second sentence I posted in the above comment I posted, have you already tested with restarting WMI on the server and seeing if that resets the counter of this issue? What are the WMI queries that are run with this server? Is this a batch file you are calling WMIC commands or an app using WMI causing the problem or what? Just curious what you're trying to accomplish ultimately with the running of those commands, etc. and seeing such logic or understanding at this level perhaps to see if there's potentially another angle to tackle it. Happy to brainstorm further too! – Pimp Juice IT Apr 16 at 18:57

Here are some result of my tests, where I dropped some of the three instances of WmiPrvSE.exe that I could see running under the credentials of SYSTEM, LOCAL SERVICE and NETWORK SERVICE.

Dropping the instances manually one by one in Task Manager, two of them were immediately restarted in a matter of seconds. The LOCAL SERVICE instance was not restarted, and to have it running again took a restart of the system service "Windows Management Instrumentation".

I don't rightly know if the LOCAL SERVICE instance will not be restarted immediately when needed, but if you wish to restart the "Windows Management Instrumentation" service, the only method I found was to run in an elevated Command Prompt (cmd):

powershell -command "Restart-Service Winmgmt -Force"

This command only took a few seconds to complete. All other restart methods using the net and sc commands were not effective on this service.

If restarting the service re-initializes the used quota, you might schedule the above command to run every few hours/days as required.

  • I'm sorry, the customer did not respond yet to this proposal. As you are the only person who has given a real answer and the bounty expires tomorrow, I've decided to grant you the bounty. – Dominique 17 hours ago
  • @Dominique: Thank you. – harrymc 16 hours ago

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.