WMI Provider Host excessive CPU

%3CLINGO-SUB%20id%3D%22lingo-sub-1103779%22%20slang%3D%22en-US%22%3EWMI%20Provider%20Host%20excessive%20CPU%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1103779%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20apologies%20if%20this%20is%20the%20wrong%20place%20for%20this%20question%20but%20I've%20scoured%20the%20web%20and%20although%20I%20have%20found%20many%20people%20asking%20the%20same%20or%20very%20similar%20questions%20I%20have%20failed%20to%20find%20any%20answers%20that%20resolve%20the%20problem.%3C%2FP%3E%3CP%3EI'm%20running%20Windows%2010%20Pro%20at%20the%201909%20level%20on%20an%20i5%20processor%20with%2016%20GB%20of%20memory%20and%20an%20SSD.%20I%20have%20a%20major%20problem%20with%20WMIPrvSE.exe%20continuously%20burning%2020%25%2B%20of%20the%20processor%20(for%20days%20on%20end)%20-%20it%20is%20not%20using%20a%20great%20deal%20of%20memory%20(250MB%20or%20so)%20and%20it%20does%20no%20physical%20I%2FOs%20according%20to%20task%20manager%20but%20it%20does%20do%20a%20significant%20number%20of%20%22other%22%20I%2FOs.%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20problem%20is%20there%20does%20not%20seem%20to%20be%20any%20way%20that%20I%20can%20find%20of%20tracking%20down%20why%20this%20is%20happening.%20If%20I%20look%20in%20the%20WMI-Activity%2FOperational%20log%20in%20Event%20Manager%20I%20see%20a%20lot%20of%20messges%20reporting%20error%20code%200x80041032%20which%20seems%20to%20be%20associated%20with%20requests%20being%20issued%20for%20some%20data%20but%20then%20a%20timeout%20occurring%20before%20the%20data%20is%20recieved.%20This%20is%20the%20text%20of%20one%20such%20Event%20Log%20entry%3A-%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CEM%3ELog%20Name%3A%20Microsoft-Windows-WMI-Activity%2FOperational%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3ESource%3A%20Microsoft-Windows-WMI-Activity%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3EDate%3A%2012%2F01%2F2020%2021%3A36%3A10%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3EEvent%20ID%3A%205858%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3ETask%20Category%3A%20None%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3ELevel%3A%20Error%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3EKeywords%3A%20%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3EUser%3A%20SYSTEM%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3EComputer%3A%20Tower3620%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3EDescription%3A%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3EId%20%3D%20%7B00000000-0000-0000-0000-000000000000%7D%3B%20ClientMachine%20%3D%20TOWER3620%3B%20User%20%3D%20TOWER3620%5CBernard%3B%20ClientProcessId%20%3D%2028064%3B%20Component%20%3D%20Unknown%3B%20Operation%20%3D%20Start%20IWbemServices%3A%3AExecQuery%20-%20ROOT%5CCIMV2%20%3A%20SELECT%20*%20FROM%20Win32_PhysicalMemory%20WHERE%20Tag%3D'Physical%20Memory%200'%3B%20ResultCode%20%3D%200x80041032%3B%20PossibleCause%20%3D%20Unknown%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3EEvent%20Xml%3A%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CEVENT%20xmlns%3D%22%26quot%3B%26lt%3BA%22%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fwin%2F2004%2F08%2Fevents%2Fevent%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fwin%2F2004%2F08%2Fevents%2Fevent%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fwin%2F2004%2F08%2Fevents%2Fevent%3C%2FA%3E%22%26gt%3B%3C%2FEVENT%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CSYSTEM%3E%3C%2FSYSTEM%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CPROVIDER%20name%3D%22%26quot%3BMicrosoft-Windows-WMI-Activity%26quot%3B%22%20guid%3D%22%26quot%3B%7B1418ef04-b0b4-4623-bf7e-d74ab47bbdaa%7D%26quot%3B%22%3E%3C%2FPROVIDER%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CEVENTID%3E5858%3C%2FEVENTID%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CVERSION%3E0%3C%2FVERSION%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CLEVEL%3E2%3C%2FLEVEL%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CTASK%3E0%3C%2FTASK%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3COPCODE%3E0%3C%2FOPCODE%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CKEYWORDS%3E0x4000000000000000%3C%2FKEYWORDS%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CTIMECREATED%20systemtime%3D%22%26quot%3B2020-01-12T21%3A36%3A10.852378600Z%26quot%3B%22%3E%3C%2FTIMECREATED%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CEVENTRECORDID%3E265967%3C%2FEVENTRECORDID%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CCORRELATION%3E%3C%2FCORRELATION%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CEXECUTION%20processid%3D%22%26quot%3B2680%26quot%3B%22%20threadid%3D%22%26quot%3B2320%26quot%3B%22%3E%3C%2FEXECUTION%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CCHANNEL%3EMicrosoft-Windows-WMI-Activity%2FOperational%3C%2FCHANNEL%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CCOMPUTER%3ETower3620%3C%2FCOMPUTER%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CSECURITY%20userid%3D%22%26quot%3BS-1-5-18%26quot%3B%22%3E%3C%2FSECURITY%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CUSERDATA%3E%3C%2FUSERDATA%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3COPERATION_CLIENTFAILURE%20xmlns%3D%22%26quot%3B%26lt%3BA%22%20href%3D%22http%3A%2F%2Fmanifests.microsoft.com%2Fwin%2F2006%2Fwindows%2FWMI%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fmanifests.microsoft.com%2Fwin%2F2006%2Fwindows%2FWMI%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fmanifests.microsoft.com%2Fwin%2F2006%2Fwindows%2FWMI%3C%2FA%3E%22%26gt%3B%3C%2FOPERATION_CLIENTFAILURE%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CID%3E%7B00000000-0000-0000-0000-000000000000%7D%3C%2FID%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CCLIENTMACHINE%3ETOWER3620%3C%2FCLIENTMACHINE%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CUSER%3ETOWER3620%5CBernard%3C%2FUSER%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CCLIENTPROCESSID%3E28064%3C%2FCLIENTPROCESSID%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CCOMPONENT%3EUnknown%3C%2FCOMPONENT%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3COPERATION%3EStart%20IWbemServices%3A%3AExecQuery%20-%20ROOT%5CCIMV2%20%3A%20SELECT%20*%20FROM%20Win32_PhysicalMemory%20WHERE%20Tag%3D'Physical%20Memory%200'%3C%2FOPERATION%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CRESULTCODE%3E0x80041032%3C%2FRESULTCODE%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3CPOSSIBLECAUSE%3EUnknown%3C%2FPOSSIBLECAUSE%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3E%3CEM%3E%3C%2FEM%3E%3C%2FSTRONG%3E%3CP%3E%3C%2FP%3E%3CP%3EWhen%20I%20look%20for%20ClientProcessID%2028064%20in%20Task%20Manager%20it%20is%20nowhere%20to%20be%20found%20-%20its%20terminated.%3C%2FP%3E%3CP%3EProcessID%202680%20is%20WIndows%20Management%20Instrumentation%2C%20but%20its%20CPU%20utilisation%20is%20alwys%20effectively%20zero.%3C%2FP%3E%3CP%3EBelow%20is%20another%20example%20of%20a%20log%20entry%20-%20same%20error%20code%20but%20very%20different%20message%2C%20ProcessID%205372%20no%20longer%20exists%3A-%3C%2FP%3E%3CP%3E%3CEM%3E%3CSTRONG%3ELog%20Name%3A%20Microsoft-Windows-WMI-Activity%2FOperational%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3ESource%3A%20Microsoft-Windows-WMI-Activity%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3EDate%3A%2012%2F01%2F2020%2021%3A28%3A33%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3EEvent%20ID%3A%205858%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3ETask%20Category%3A%20None%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3ELevel%3A%20Error%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3EKeywords%3A%20%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3EUser%3A%20SYSTEM%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3EComputer%3A%20Tower3620%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3EDescription%3A%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3EId%20%3D%20%7B00000000-0000-0000-0000-000000000000%7D%3B%20ClientMachine%20%3D%20TOWER3620%3B%20User%20%3D%20TOWER3620%5CBernard%3B%20ClientProcessId%20%3D%205372%3B%20Component%20%3D%20Unknown%3B%20Operation%20%3D%20Start%20IWbemServices%3A%3AExecQuery%20-%20ROOT%5CCIMV2%20%3A%20SELECT%20SerialNumber%20FROM%20Win32_Bios%3B%20ResultCode%20%3D%200x80041032%3B%20PossibleCause%20%3D%20Unknown%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3EEvent%20Xml%3A%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CEVENT%20xmlns%3D%22%26quot%3B%26lt%3BA%22%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fwin%2F2004%2F08%2Fevents%2Fevent%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fwin%2F2004%2F08%2Fevents%2Fevent%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fwin%2F2004%2F08%2Fevents%2Fevent%3C%2FA%3E%22%26gt%3B%3C%2FEVENT%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CSYSTEM%3E%3C%2FSYSTEM%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CPROVIDER%20name%3D%22%26quot%3BMicrosoft-Windows-WMI-Activity%26quot%3B%22%20guid%3D%22%26quot%3B%7B1418ef04-b0b4-4623-bf7e-d74ab47bbdaa%7D%26quot%3B%22%3E%3C%2FPROVIDER%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CEVENTID%3E5858%3C%2FEVENTID%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CVERSION%3E0%3C%2FVERSION%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CLEVEL%3E2%3C%2FLEVEL%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CTASK%3E0%3C%2FTASK%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3COPCODE%3E0%3C%2FOPCODE%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CKEYWORDS%3E0x4000000000000000%3C%2FKEYWORDS%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CTIMECREATED%20systemtime%3D%22%26quot%3B2020-01-12T21%3A28%3A33.751355300Z%26quot%3B%22%3E%3C%2FTIMECREATED%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CEVENTRECORDID%3E265964%3C%2FEVENTRECORDID%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CCORRELATION%3E%3C%2FCORRELATION%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CEXECUTION%20processid%3D%22%26quot%3B2680%26quot%3B%22%20threadid%3D%22%26quot%3B29552%26quot%3B%22%3E%3C%2FEXECUTION%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CCHANNEL%3EMicrosoft-Windows-WMI-Activity%2FOperational%3C%2FCHANNEL%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CCOMPUTER%3ETower3620%3C%2FCOMPUTER%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CSECURITY%20userid%3D%22%26quot%3BS-1-5-18%26quot%3B%22%3E%3C%2FSECURITY%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CUSERDATA%3E%3C%2FUSERDATA%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3COPERATION_CLIENTFAILURE%20xmlns%3D%22%26quot%3B%26lt%3BA%22%20href%3D%22http%3A%2F%2Fmanifests.microsoft.com%2Fwin%2F2006%2Fwindows%2FWMI%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fmanifests.microsoft.com%2Fwin%2F2006%2Fwindows%2FWMI%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fmanifests.microsoft.com%2Fwin%2F2006%2Fwindows%2FWMI%3C%2FA%3E%22%26gt%3B%3C%2FOPERATION_CLIENTFAILURE%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CID%3E%7B00000000-0000-0000-0000-000000000000%7D%3C%2FID%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CCLIENTMACHINE%3ETOWER3620%3C%2FCLIENTMACHINE%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CUSER%3ETOWER3620%5CBernard%3C%2FUSER%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CCLIENTPROCESSID%3E5372%3C%2FCLIENTPROCESSID%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CCOMPONENT%3EUnknown%3C%2FCOMPONENT%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3COPERATION%3EStart%20IWbemServices%3A%3AExecQuery%20-%20ROOT%5CCIMV2%20%3A%20SELECT%20SerialNumber%20FROM%20Win32_Bios%3C%2FOPERATION%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CRESULTCODE%3E0x80041032%3C%2FRESULTCODE%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3CPOSSIBLECAUSE%3EUnknown%3C%2FPOSSIBLECAUSE%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3E%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20completely%20stumped%20on%20how%20to%20resolve%20this%20issue%20-%20can%20anyone%20help%20please%3F%3C%2FP%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1364358%22%20slang%3D%22en-US%22%3ERe%3A%20WMI%20Provider%20Host%20excessive%20CPU%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1364358%22%20slang%3D%22en-US%22%3EI've%20got%20a%20similar%20issue%2C%20any%20success%20in%20trying%20to%20resolve%20this%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1365469%22%20slang%3D%22en-US%22%3ERe%3A%20WMI%20Provider%20Host%20excessive%20CPU%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1365469%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F658143%22%20target%3D%22_blank%22%3E%40ktoerne%3C%2FA%3E%26nbsp%3B-%20yes%20I%20did%20manage%20to%20resolve%20it%20but%20more%20by%20luck%20than%20anything.%20I%20tried%20some%20other%20forums%20but%20no%20one%20seemed%20to%20come%20up%20with%20an%20answer%20as%20to%20how%20you%20could%20track%20the%20cause%20of%20the%20problem%20down.%20I%20really%20not%20sure%20it%20is%20possible.%20However%20I%20discovered%20purely%20by%20accident%20that%20it%20was%20Garmin%20Connect%20that%20was%20causing%20the%20problem%20on%20my%20machine.%20I%20believe%20the%20issue%20is%20basically%20caused%20by%20an%20application%20asking%20for%20some%20windows%20instrumentation%20data.%20I%20was%20running%20Garmin%20Connect%20to%20upload%20data%20from%20my%20Garmin%20Edge%2025%20cycling%20computer%20to%20Garmin's%20web%20site%20and%20when%20the%20process%20was%20finished%20(only%20takes%20about%2030%20seconds%20each%20time)%20I%20would%20click%20close%20on%20the%20Connect%20application%20and%20it%20would%20go%20away%20but%20continue%20running%20with%20an%20icon%20in%20the%20little%20box%20that%20you%20get%20when%20you%20click%20on%20the%20upwards%20pointing%20arrow%20on%20the%20right%20of%20the%20task%20bar.%20I%20right%20clicked%20this%20and%20it%20gave%20me%20the%20option%20to%20%22Exit%22%20Garmin%20Connect%20and%20instantly%20the%20problem%20went%20away%20as%20the%20app%20closed%20down%20completely.%20I%20have%20reported%20the%20problem%20to%20Garmin%20but%20they%20haven't%20done%20anything%20about%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20all%20I%20can%20suggest%20is%20that%20you%20bring%20up%20task%20manager%20and%20then%20selectively%20try%20completely%20closing%20any%20non%20Windows%20system%20app%20you%20find%20in%20that%20list%20on%20the%20bottom%20right%20of%20the%20screen%20and%20see%20which%20one%20is%20causing%20your%20problem%20-%20assuming%20you're%20not%20running%20Garmin%20Connect%20of%20course%20-%20if%20you%20are%20then%20you%20probably%20have%20an%20easy%20answer.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGood%20luck.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1380631%22%20slang%3D%22en-US%22%3ERe%3A%20WMI%20Provider%20Host%20excessive%20CPU%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1380631%22%20slang%3D%22en-US%22%3E%2B1%20this.%3CBR%20%2F%3EIn%20my%20case%2C%20it%20was%20Garmin%20Express%20which%20caused%20excessive%20CPU%20Usage%20through%20WMI%20Provider%20Host.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20for%20the%20information%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F118466%22%20target%3D%22_blank%22%3E%40bernard%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1380669%22%20slang%3D%22en-US%22%3ERe%3A%20WMI%20Provider%20Host%20excessive%20CPU%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1380669%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F663753%22%20target%3D%22_blank%22%3E%40Adrianonfire%3C%2FA%3E%26nbsp%3BYou're%20right%20-%20my%20apologies%2C%20I%20meant%20to%20say%20Garmin%20Express.%20Glad%20I%20was%20able%20to%20point%20you%20in%20the%20right%20direction%20and%20sorry%20I%20mistyped%20the%20name.%3C%2FP%3E%3CP%3EBernard%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1387598%22%20slang%3D%22en-US%22%3ERe%3A%20WMI%20Provider%20Host%20excessive%20CPU%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1387598%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F56662%22%20target%3D%22_blank%22%3E%40Bernard%20Cadogan%3C%2FA%3E-%20wow%20thanks%2C%20this%20also%20worked%20for%20me%20(exiting%20Garmin%20Express)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1387722%22%20slang%3D%22en-US%22%3ERe%3A%20WMI%20Provider%20Host%20excessive%20CPU%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1387722%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F666906%22%20target%3D%22_blank%22%3E%40markdotai%3C%2FA%3E%26nbsp%3BMy%20pleasure%20Mark%2C%20its%20feedback%20like%20this%20that%20makes%20me%20think%20it%20was%20worth%20while%20posting%20what%20worked%20for%20me%20even%20if%20I%20cant%20explain%20why.%20Thank%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1401439%22%20slang%3D%22en-US%22%3ERe%3A%20WMI%20Provider%20Host%20excessive%20CPU%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1401439%22%20slang%3D%22en-US%22%3E%3CP%3EMany%20thanks%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F56662%22%20target%3D%22_blank%22%3E%40Bernard%20Cadogan%3C%2FA%3E!%20After%20hours%20of%20struggling%20with%20this%20you%20pointed%20me%20into%20the%20right%20direction!%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Fhtml%2Fimages%2Femoticons%2Fsmile_40x40.gif%22%20alt%3D%22%3Asmile%3A%22%20title%3D%22%3Asmile%3A%22%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1416498%22%20slang%3D%22en-US%22%3ERe%3A%20WMI%20Provider%20Host%20excessive%20CPU%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1416498%22%20slang%3D%22en-US%22%3E%3CP%3EWMI%20Provider%20Host%20shouldn't%20normally%20use%20much%20CPU%2C%20as%20it%20shouldn't%20normally%20be%20doing%20anything.%20...%20Locate%20the%20%E2%80%9CWindows%20Management%20Instrumentation%20service%E2%80%9D%20in%20the%20list%2C%20right-click%20it%2C%20and%20select%20%E2%80%9CRestart%E2%80%9D.%20If%20you%20see%20consistently%20high%20CPU%20usage%2C%20it's%20likely%20that%20another%20process%20on%20your%20system%20is%20behaving%20badly.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1416619%22%20slang%3D%22en-US%22%3ERe%3A%20WMI%20Provider%20Host%20excessive%20CPU%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1416619%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F378366%22%20target%3D%22_blank%22%3E%40Smith_J%3C%2FA%3E%26nbsp%3BYes%2C%20another%20process%20is%20causing%20the%20problem%2C%20although%20it%20is%20WMI%20Provider%20that%20is%20using%20the%20excess%20CPU.%20The%20other%20process%20is%20Garmin%20Express%20and%20how%20to%20deal%20with%20it%20has%20been%20explained%20in%20the%20previous%20posts.%20The%20problem%20has%20been%20reported%20to%20Garmin%20but%20so%20far%20they%20have%20not%20released%20any%20fix%20for%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1456027%22%20slang%3D%22en-US%22%3ERe%3A%20WMI%20Provider%20Host%20excessive%20CPU%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1456027%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F56662%22%20target%3D%22_blank%22%3E%40Bernard%20Cadogan%3C%2FA%3E%26nbsp%3B%2B1%20for%20finding%20this%20-%20worked%20for%20me%20too.%20I%20had%20hit%20a%20dead%20end%20because%20all%20the%20PIDs%20that%20had%20caused%20the%20WMI%20errors%20were%20no%20longer%20in%20the%20process%20table%20-%20and%20even%20turning%20on%20Process%20success%20auditing%20in%20the%20Security%20Log%20hadn't%20enabled%20me%20to%20track%20anything%20down.%20Good%20old%20Garmin%20%3A-(.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1480543%22%20slang%3D%22en-US%22%3ERe%3A%20WMI%20Provider%20Host%20excessive%20CPU%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1480543%22%20slang%3D%22en-US%22%3EGreat%20-%20solved%20my%20issue%20instantly.%20Garmin%20express%20it%20is.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1481639%22%20slang%3D%22en-US%22%3ERe%3A%20WMI%20Provider%20Host%20excessive%20CPU%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1481639%22%20slang%3D%22en-US%22%3EJust%20chiming%20in%3A%20it%20was%20also%20Garmin%20Express%20for%20our%202010%20Dell%20desktop%20computer.%20Many%20thanks!%20The%20computer%20was%20barely%20functioning%20but%20the%20impact%20of%20shutting%20down%20Garmin%20Express%20was%20immediate%20and%20dramatic!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1481670%22%20slang%3D%22en-US%22%3ERe%3A%20WMI%20Provider%20Host%20excessive%20CPU%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1481670%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F707018%22%20target%3D%22_blank%22%3E%40codetojoy%3C%2FA%3E%26nbsp%3BDelighted%20to%20be%20of%20help%20-%20the%20really%20frustrating%20thing%20is%20Garmin%20seems%20to%20have%20ignored%20my%20report%20of%20the%20problem%20-%20I%E2%80%99ll%20have%20to%20have%20another%20go%20at%20them.%20I%20suspect%20many%20more%20people%20are%20seeing%20this%20problem%20and%20not%20just%20those%20of%20you%20who%20have%20responded%20on%20this%20thread.%20I%20appreciate%20your%20feedback%20and%20thank%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1831386%22%20slang%3D%22en-US%22%3ERe%3A%20WMI%20Provider%20Host%20excessive%20CPU%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1831386%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20are%20a%20genius!%20It%20works%20for%20me%20too.%26nbsp%3B%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Fhtml%2Fimages%2Femoticons%2Fsmile_40x40.gif%22%20alt%3D%22%3Asmile%3A%22%20title%3D%22%3Asmile%3A%22%20%2F%3E%20Thanks!%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F56662%22%20target%3D%22_blank%22%3E%40Bernard%20Cadogan%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1831595%22%20slang%3D%22en-US%22%3ERe%3A%20WMI%20Provider%20Host%20excessive%20CPU%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1831595%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F850014%22%20target%3D%22_blank%22%3E%40BeaLozer%3C%2FA%3E%26nbsp%3BThanks%2C%20I%20updated%20my%20Garmin%20Express%20to%207.1.4.0%20a%20couple%20of%20weeks%20ago%20and%20it%20seems%20Garmin%20have%20fixed%20the%20problem%20in%20that%20release%20-%20I%E2%80%99m%20also%20running%20WIN%2010%20Pro%20at%20the%202004%20level%2C%20just%20in%20case%20that%20is%20relevant.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1831699%22%20slang%3D%22en-US%22%3ERe%3A%20WMI%20Provider%20Host%20excessive%20CPU%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1831699%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F56662%22%20target%3D%22_blank%22%3E%40Bernard%20Cadogan%3C%2FA%3E%26nbsp%3B%3CSPAN%3EThank%20you%20very%20much!%20Now%20I%20also%20installed%26nbsp%3Bthe%20new%20version%26nbsp%3Band%20seems%20that%20the%20bug%20is%20fixed.%20I%20am%20not%20an%20IT%20person%2C%20therefore%20your%20easy%20solution%20helps%20me%20a%20lot.%20Thanks!%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

My apologies if this is the wrong place for this question but I've scoured the web and although I have found many people asking the same or very similar questions I have failed to find any answers that resolve the problem.

I'm running Windows 10 Pro at the 1909 level on an i5 processor with 16 GB of memory and an SSD. I have a major problem with WMIPrvSE.exe continuously burning 20%+ of the processor (for days on end) - it is not using a great deal of memory (250MB or so) and it does no physical I/Os according to task manager but it does do a significant number of "other" I/Os. 

The problem is there does not seem to be any way that I can find of tracking down why this is happening. If I look in the WMI-Activity/Operational log in Event Manager I see a lot of messges reporting error code 0x80041032 which seems to be associated with requests being issued for some data but then a timeout occurring before the data is recieved. This is the text of one such Event Log entry:-

Log Name: Microsoft-Windows-WMI-Activity/Operational
Source: Microsoft-Windows-WMI-Activity
Date: 12/01/2020 21:36:10
Event ID: 5858
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: Tower3620
Description:
Id = {00000000-0000-0000-0000-000000000000}; ClientMachine = TOWER3620; User = TOWER3620\Bernard; ClientProcessId = 28064; Component = Unknown; Operation = Start IWbemServices::ExecQuery - ROOT\CIMV2 : SELECT * FROM Win32_PhysicalMemory WHERE Tag='Physical Memory 0'; ResultCode = 0x80041032; PossibleCause = Unknown
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WMI-Activity" Guid="{1418ef04-b0b4-4623-bf7e-d74ab47bbdaa}" />
<EventID>5858</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2020-01-12T21:36:10.852378600Z" />
<EventRecordID>265967</EventRecordID>
<Correlation />
<Execution ProcessID="2680" ThreadID="2320" />
<Channel>Microsoft-Windows-WMI-Activity/Operational</Channel>
<Computer>Tower3620</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<Operation_ClientFailure xmlns="http://manifests.microsoft.com/win/2006/windows/WMI">
<Id>{00000000-0000-0000-0000-000000000000}</Id>
<ClientMachine>TOWER3620</ClientMachine>
<User>TOWER3620\Bernard</User>
<ClientProcessId>28064</ClientProcessId>
<Component>Unknown</Component>
<Operation>Start IWbemServices::ExecQuery - ROOT\CIMV2 : SELECT * FROM Win32_PhysicalMemory WHERE Tag='Physical Memory 0'</Operation>
<ResultCode>0x80041032</ResultCode>
<PossibleCause>Unknown</PossibleCause>
</Operation_ClientFailure>
</UserData>
</Event>

When I look for ClientProcessID 28064 in Task Manager it is nowhere to be found - its terminated.

ProcessID 2680 is WIndows Management Instrumentation, but its CPU utilisation is alwys effectively zero.

Below is another example of a log entry - same error code but very different message, ProcessID 5372 no longer exists:-

Log Name: Microsoft-Windows-WMI-Activity/Operational
Source: Microsoft-Windows-WMI-Activity
Date: 12/01/2020 21:28:33
Event ID: 5858
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: Tower3620
Description:
Id = {00000000-0000-0000-0000-000000000000}; ClientMachine = TOWER3620; User = TOWER3620\Bernard; ClientProcessId = 5372; Component = Unknown; Operation = Start IWbemServices::ExecQuery - ROOT\CIMV2 : SELECT SerialNumber FROM Win32_Bios; ResultCode = 0x80041032; PossibleCause = Unknown
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WMI-Activity" Guid="{1418ef04-b0b4-4623-bf7e-d74ab47bbdaa}" />
<EventID>5858</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2020-01-12T21:28:33.751355300Z" />
<EventRecordID>265964</EventRecordID>
<Correlation />
<Execution ProcessID="2680" ThreadID="29552" />
<Channel>Microsoft-Windows-WMI-Activity/Operational</Channel>
<Computer>Tower3620</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<Operation_ClientFailure xmlns="http://manifests.microsoft.com/win/2006/windows/WMI">
<Id>{00000000-0000-0000-0000-000000000000}</Id>
<ClientMachine>TOWER3620</ClientMachine>
<User>TOWER3620\Bernard</User>
<ClientProcessId>5372</ClientProcessId>
<Component>Unknown</Component>
<Operation>Start IWbemServices::ExecQuery - ROOT\CIMV2 : SELECT SerialNumber FROM Win32_Bios</Operation>
<ResultCode>0x80041032</ResultCode>
<PossibleCause>Unknown</PossibleCause>
</Operation_ClientFailure>
</UserData>
</Event>

 

I'm completely stumped on how to resolve this issue - can anyone help please?

16 Replies
Highlighted
I've got a similar issue, any success in trying to resolve this?
Highlighted

@ktoerne - yes I did manage to resolve it but more by luck than anything. I tried some other forums but no one seemed to come up with an answer as to how you could track the cause of the problem down. I really not sure it is possible. However I discovered purely by accident that it was Garmin Connect that was causing the problem on my machine. I believe the issue is basically caused by an application asking for some windows instrumentation data. I was running Garmin Connect to upload data from my Garmin Edge 25 cycling computer to Garmin's web site and when the process was finished (only takes about 30 seconds each time) I would click close on the Connect application and it would go away but continue running with an icon in the little box that you get when you click on the upwards pointing arrow on the right of the task bar. I right clicked this and it gave me the option to "Exit" Garmin Connect and instantly the problem went away as the app closed down completely. I have reported the problem to Garmin but they haven't done anything about it.

 

So all I can suggest is that you bring up task manager and then selectively try completely closing any non Windows system app you find in that list on the bottom right of the screen and see which one is causing your problem - assuming you're not running Garmin Connect of course - if you are then you probably have an easy answer. 

 

Good luck. 

Highlighted
+1 this.
In my case, it was Garmin Express which caused excessive CPU Usage through WMI Provider Host.

Thanks for the information @bernard
Highlighted

@Adrianonfire You're right - my apologies, I meant to say Garmin Express. Glad I was able to point you in the right direction and sorry I mistyped the name.

Bernard

Highlighted

@Bernard Cadogan- wow thanks, this also worked for me (exiting Garmin Express)

 

Highlighted

@markdotai My pleasure Mark, its feedback like this that makes me think it was worth while posting what worked for me even if I cant explain why. Thank you.

Highlighted

Many thanks @Bernard Cadogan! After hours of struggling with this you pointed me into the right direction!:smile:

Highlighted

WMI Provider Host shouldn't normally use much CPU, as it shouldn't normally be doing anything. ... Locate the “Windows Management Instrumentation service” in the list, right-click it, and select “Restart”. If you see consistently high CPU usage, it's likely that another process on your system is behaving badly.

Highlighted

@Smith_J Yes, another process is causing the problem, although it is WMI Provider that is using the excess CPU. The other process is Garmin Express and how to deal with it has been explained in the previous posts. The problem has been reported to Garmin but so far they have not released any fix for it.

Highlighted

@Bernard Cadogan +1 for finding this - worked for me too. I had hit a dead end because all the PIDs that had caused the WMI errors were no longer in the process table - and even turning on Process success auditing in the Security Log hadn't enabled me to track anything down. Good old Garmin :-(.

Highlighted
Great - solved my issue instantly. Garmin express it is.
Highlighted
Just chiming in: it was also Garmin Express for our 2010 Dell desktop computer. Many thanks! The computer was barely functioning but the impact of shutting down Garmin Express was immediate and dramatic!
Highlighted

@codetojoy Delighted to be of help - the really frustrating thing is Garmin seems to have ignored my report of the problem - I’ll have to have another go at them. I suspect many more people are seeing this problem and not just those of you who have responded on this thread. I appreciate your feedback and thank you.

Highlighted

You are a genius! It works for me too. :smile: Thanks! @Bernard Cadogan 

Highlighted

@BeaLozer Thanks, I updated my Garmin Express to 7.1.4.0 a couple of weeks ago and it seems Garmin have fixed the problem in that release - I’m also running WIN 10 Pro at the 2004 level, just in case that is relevant.

Highlighted

@Bernard Cadogan Thank you very much! Now I also installed the new version and seems that the bug is fixed. I am not an IT person, therefore your easy solution helps me a lot. Thanks!