devicecensus.exe

rhansen · 05 Jul 2018

storageman said:

It doesn't fix it, just blocks. I would not worry about this. All three of my W10 systems are getting that error every time I power them up and yes it started after the last CU. Its really sad that MS can't get their act together. I do not ever remember having these kind of issues under W7.

Yeah. I disabled the task. No more devicecensus. They can fix it when they rehire their QA team.

Task folder in taskschd.exe is: Microsoft/Windows/Device Information

If you disable that task, it doesn't run any more.

Bree · 19 Jul 2018

storageman said:

... All three of my W10 systems are getting that error every time I power them up and yes it started after the last CU....

I have three W10 systems too. Two do, but one has never shown this error, all three are on 17134.167.

The two that do are both Pro, one x86 the other x64. The one that doesn't is Home x64.

You can create the crash at will by opening a command prompt and typing devicecensus after which there will be one more crash reported in reliability history. On the Home machine I can run it as many times as I want but it never crashes.

Caledon Ken · 28 Jul 2018

Just chiming in.

I have Pro on desktop and I get the error everyday, started with 1803. Happens once a day, in morning when I awake PC.

Funny thing, my ancient Dell laptop running Pro does not get error.

91fw · 31 Jul 2018

64bit windows10-pro. Updated to 1803 July 25. Every single day reliability shows devicecensus.exe error, faulting their own module WaaSAssesment.dll. I wonder if they plan to hire competent programmers or not.

simrick · 11 Aug 2018

Same problem here since updating to v1803.

91fw · 11 Aug 2018

Disabling devicecensus task worked for me (see post #11). Sure looks like M$ still hasn't fixed it.

Caledon Ken · 15 Aug 2018

Today was the first day since I installed 1803 that devicecensus didn't fail. It is also the first day after patches.

Now that I posted this I know it will fail.

Anyone else see a change, those that still have task active?

rhansen · 15 Aug 2018

Looks like the solution to this problem may be to fire up Disk Cleanup, go to admin mode, and select to clean up Windows Update Files. If anyone is still having the problem.

Caledon Ken · 15 Aug 2018

I tried that a week ago. Ran devicecensus manually and it was successful. Next day it failed.

Hoping update from yesterday is a more permanent fix. Maybe a combo of both.

Bree · 15 Aug 2018

Caledon Ken said:

Today was the first day since I installed 1803 that devicecensus didn't fail. It is also the first day after patches. ....
Anyone else see a change, those that still have task active?

rhansen said:

Looks like the solution to this problem may be to fire up Disk Cleanup, go to admin mode, and select to clean up Windows Update Files...

Caledon Ken said:

I tried that a week ago. Ran devicecensus manually and it was successful. Next day it failed....

After every cumulative update I routinely clean up Windows Update files, it's never had any effect on this problem in the past.

I have made no efforts to disable devicecensus tasks, preferring to leave it 'as-is' and wait to see if MS fix it. Like you Ken, I have seen no errors reported since the update to 17134.228 yesterday.

Bree said:

...You can create the crash at will by opening a command prompt and typing devicecensus after which there will be one more crash reported in reliability history. On the Home machine I can run it as many times as I want but it never crashes.

This no longer creates the crash in Pro - a hopeful sign. We'll know for sure in another day or so....