Dec 02 2021 03:47 AM
Hello, since upgrading to Windows 10 Pro 20H2 from 1903. The following start up after 5 minutes. These are...
Win32_TpmProvider provider started with result code 0x0. HostProcess = wmiprvse.exe; ProcessID = 3188; ProviderPath = C:\Windows\System32\wbem\Win32_TPM.dll
And Win32_DeviceGuard provider started with result code 0x0. HostProcess = wmiprvse.exe; ProcessID = 3188; ProviderPath = %SystemRoot%\System32\Win32_DeviceGuard.dll
Unfortunately they are triggering massive network activity even if it is for a few seconds..
This is triggering this error Id 5858 = {00000000-0000-0000-0000-000000000000}; ClientMachine = DESKTOP-XXXXX; User = NT AUTHORITY\SYSTEM; ClientProcessId = 4912; Component = Unknown; Operation = Start IWbemServices::ExecQuery - ROOT\CIMV2 : SELECT ID FROM Win32_ServerFeature; ResultCode = 0x80041010; PossibleCause = Unknown
After restarting computer, no more errors and this doesn't occur again until the next day, back to square one again.
But this is just like UPFC.exe. I think this is some sort of telemetry that Microsoft implemented every day to happen once at least.
Dec 02 2021 10:47 AM
Dec 05 2021 07:43 PM
Dec 07 2021 08:42 AM
Dec 12 2021 12:11 PM
@Arexodius@adam deltinger
I have finally solved this mysterious error!!!!
Turns out this has absolutely nothing to do with the actual Device Guard Virtualisation as some advised me. This stupid error is triggered due to Device Information Task Schedule that is exclusive to Windows 10 only! You will not find this task schedule in Windows 7 or 8.1.
What is devicecensus.exe on Windows 10 and why does it need Internet connectivity? - gHacks Tech New...
This is basically another telemetry data collection that Microsoft uses to collect information about your system. This is why you get network spikes when this schedule runs.
The way I found out is that when the error occurred, it corresponded to the exact timing of the task schedule. I have observed this in my last error history that it matches the last task schedule run time. As soon as I disabled this task schedule, the error stopped occurring and you'll no longer get Win32_DeviceGuard and Win32_TpmProvider logged.
I have to say I am really disappointed that, no one was able to tell me that this was the issue triggering the error! Even Microsoft Support failed to give me the right answer. They were giving me the Device Guard advice. I know that had nothing to do with it.
Somehow when I upgraded initially from 1903 to 20H2 the task schedule was reset back to default. But I had no idea that Device Information task schedule was responsible for triggering this error! Now I know and hopefully this should be helpful to others as well!
Dec 13 2021 03:28 AM