chris13

In my humble opinion this need s to be sorted out between Microsoft and Eset. Disabling wmi scan is not an option as it leaves you vulnerable. As far as i remember the famous stuxnet took advantage of wmi technologies. One more thing: After computer scan not only does wmi host provider crash but there is also a handle leak taking place.

This is not a microsoft issue. It is ESET that needs to solve the problem. The same error appears after a computer scan not only wmi.

Hello, I would just like to emphasize a new issue that i just discovered. After each computer scan but especially when i start a custom wmi database scan the WMI PROVIDER HOSTS crashes. This is what i found in the event log. And the same entry is created after each scan. Can somebody assist? Faulting Application Path: C:\Windows\System32\wbem\WmiPrvSE.exe Problem signature Problem Event Name: CLR20r3 Problem Signature 01: wmiprvse.exe Problem Signature 02: 10.0.19041.546 Problem Signature 03: 5da7ab91 Problem Signature 04: System.Management.Instrumentation Problem Signature 05: 4.8.4084.0 Problem Signature 06: 5dda3e38 Problem Signature 07: 40 Problem Signature 08: 132 Problem Signature 09: FatalError OS Version: 10.0.19042.2.0.0.256.48 Locale ID: 1033 Additional Information 1: ba66 Additional Information 2: ba665be9707b05c3401a25e345fcc5c9 Additional Information 3: e321 Additional Information 4: e321cd104b60201d6468d53bd9769b58 Extra information about the problem Bucket ID: 45782a9a1a61f26c27dfe8789c869ae9 (1720349187398605545) Regards Chris