All kinds of things will go wrong when the WMI repository If you hit whatever conditions that cause WMI to start becoming corrupt, the SCCM client with drastically accelerate the speed of that corruption because it makes heavy use of the wmi repository. We ran into basically the same thing, and the answer is: you better install those wmi hotfixes. So have you quit using sccm for update services completely, or just for EP updates?Īlso, how did you clean up outdated updates, did you delete the software update groups? Our software update deployments are free of any expired or superseded updates. We currently have Endpoint Protection updating directly from Microsoft Windows Update. WBEM is a subcomponent of WMI, which in turn is contained in svchost.exe. Deleting the WBEM repository should be avoided. If the WBEM repository is corrupt, it may take hours for WBEM to calm down.
To stop this, remove all software update deployments especially those for Endpoint Protection the WBEM should calm down in an hour or so. Expired updates make WBEM run wild and unstable.
Mostly, it is caused by expired definition updates for Endpoint Protection.
As it turns out this is caused by expired updates, in software update deployments.