Hi everyone
I came across this while looking into what's gobbling up CPU power at startup. This is the output from Event Viewer > Applications and Service Logs\Microsoft\Windows\WMI-Activity\Operational:
Log Name: Microsoft-Windows-WMI-Activity/Operational
Source: Microsoft-Windows-WMI-Activity
Date: 29/12/2021 11:56:42
Event ID: 5858
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: GK-Notebook
Description:
Id = {00000000-0000-0000-0000-000000000000}; ClientMachine = GK-NOTEBOOK; User = NT AUTHORITY\SYSTEM; ClientProcessId = 6404; Component = Unknown; Operation = Start IWbemServices::ExecQuery - root\cimv2 : SELECT Name,ServiceName FROM Win32_NetworkAdapter WHERE InterfaceIndex = 22 AND NetConnectionStatus = 2; 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="2021-12-29T09:56:42.7624896Z" />
<EventRecordID>280083</EventRecordID>
<Correlation />
<Execution ProcessID="2360" ThreadID="14696" />
<Channel>Microsoft-Windows-WMI-Activity/Operational%/Channel>
<Computer>GK-Notebook</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>GK-NOTEBOOK</ClientMachine>
<User>NT AUTHORITY\SYSTEM</User>
<ClientProcessId>6404</ClientProcessId>
<Component>Unknown</Component>
<Operation>Start IWbemServices::ExecQuery - root\cimv2 : SELECT Name,ServiceName FROM Win32_NetworkAdapter WHERE InterfaceIndex = 22 AND NetConnectionStatus = 2%/Operation>
<ResultCode>0x80041032</ResultCode>
<PossibleCause>Unknown</PossibleCause>
</Operation_ClientFailure>
</UserData>
</Event>
Using Task Manager, I found that ProcessID 6404 is "swiservice.exe".
It's not a huge problem, as it seemingly only peaked at about 2% of CPU, but it does happen every 5 minutes while idle, which seems a tad wasteful and inefficient, so if it's an easy fix, I'd like to fix it. I just don't know where to go from here to track it further.
There are also a lot more frequent and repeated 5858 events at startup, but with different clients and operations. I was not fast enough to track those ClientProcessId before they terminated, but I figure the one above might be the best place to start, and see what things look like after it's fixed.
Or is this largely a non-issue and I should just ignore it?
Specs:
Edition Windows 10 Pro
Version 21H2
Installed on 13/09/2020
OS build 19044.1415
Experience Windows Feature Experience Pack 120.2212.3920.0
Processor Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz 2.80 GHz
Installed RAM 16.0 GB
System type 64-bit operating system, x64-based processor