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
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.