For Windows Vista and Windows Server 2008 systems the memory quota per host is 512MB. Under properties find the property "MemoryPerHost" or any other ones you need to modify and double click itĬhange the value to 512 MB which is 536870912Ĭlick Save Object in the Object Editor windowĬlose the other windows now and exit WMI TesterĪ quick note here - on Windows XP and Windows Server 2003 systems, the memory quota per host is 128MB. In this windows now double click Object Editor windows will come up now In the Class Info dialog box enter Superclass Name as "_ProviderHostQuotaConfiguration" (without quotes) and press OK.Ī query Result window will come up. Note: you aren’t connecting to CimV2 or any other namespaces. In the namespace text box just enter "root" (without quotes) That having been said, if you are in a situation where there is a need to modify these values, you can do so using the steps below:Ĭlick Connect on the Windows Management Instrumentation Tester In instances such as these, normal leak troubleshooting must be performed to identify the root cause. ! If the WMIPRVSE.EXE process is actually leaking handles or memory, modifying the quota will only delay the issue from occurring, not eliminate it. These quotas are configurable, however –ĭo not modify these quotas for the sake of modifying them However, there are applications like System Center that may require more memory or handles for the process. When the WMI Provider service reaches its quota limit, WMI queries that are being handled by that instance of WMIPRVSE.EXE will most likely fail. The different properties available are:ĭefines the number of threads owned by any one hostĭefines the number of kernel object handles each host may haveĭefines the total number of host processes that can be executing concurrentlyĭefines the amount of private memory that can be held by each hostĭefines the combined amount of private memory (in bytes) that can be held by all hosts This class allows limits to be set on host process usage of system resources. The name of this class is _ProviderHostQuotaConfiguration. Within the WMI System Classes there is a configuration class for host provider processes. Set the Value data field to 1 and click OK. Double-click on the ClearPageFileAtShutdown key on the right. We’ve talked about various memory management issues in previous posts, but the WMI Provider Service has some interesting quotas that administrators should be aware of. Navigate to HKEYLOCALMACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management. We’ve been getting some calls recently about the performance of this service and some failures that customers have been experiencing – in particular “Out of Memory” errors when certain WMI-related tasks are running. Hi folks, Mark Ghazai here once again with a quick tidbit on tweaking the WMI Provider Service (WMIPRVSE.EXE). First published on TECHNET on Sep 16, 2008