Device Census Stopped Working Problem

I installed the latest cumulative update that was released on Tuesday with patch level 17134.165 but the daily crash has not been fixed together with other Windows 10 April 2018 update problems such as some mkv video files cannot have their thumbnails generated in File Explorer unless a thumbnail generator like Icaros thumbnails is installed. The videos play well but most of their details are not loaded when right clicking the file and navigating to the details tab. Icaros thumbnails also loads the details in the details tab.

I installed the latest cumulative update that was released on Tuesday with patch level 17134.165 but the daily crash has not been fixed together with other Windows 10 April 2018 update problems such as some mkv video files cannot have their thumbnails generated in File Explorer unless a thumbnail generator like Icaros thumbnails is installed. The videos play well but most of their details are not loaded when right clicking the file and navigating to the details tab. Icaros thumbnails also loads the details in the details tab.

This issue just started for me with the last cumulative update july 9 2018.

The pc gets passed the bios post test and loads to the start screen and either a failed 

load of the os with a spinning wheel or blank   screen for x minutes.

Looking at the logs from event viewer;    

Faulting application name: devicecensus.exe, version: 10.0.17673.1005, time stamp: 0x79a09a4b

Faulting module name: WaaSAssessment.dll, version: 10.0.17134.1, time stamp: 0xb7ab6594

Exception code: 0xc0000005

Fault offset: 0x0000000000008ee5

Faulting process id: 0xf44

Faulting application start time: 0x01d41bd59ade763f

Faulting application path: C:\WINDOWS\system32\devicecensus.exe

Faulting module path: C:\Windows\System32\WaaSAssessment.dll

Report Id: 006e40b8-7b2b-403a-b842-a07d3f5ed8b2

and this at the same time;

Log Name:      Microsoft-Windows-Kernel-EventTracing/Admin

Source:        Microsoft-Windows-Kernel-EventTracing

Date:          7/14/2018 6:49:09 PM

Event ID:      2

Task Category: Session

Level:         Error

Keywords:      Session

User:          SYSTEM

Computer:      DESKTOP-SVOCV7A

Description:

Session "ECCB175F-1EB2-43DA-BFB5-A8D58A40A4D7" failed to start with the following error: 0xC0000035

So the user is not logged in but these things are trying to run before login, of course it will fail as they need to start after login.

Another fine mess from the quality team and not listening to insiders.

Going to a local account has fixed this issue on another win10 with the same build 17134.165;

may have to do the same on the other four.

Getting this error on all win10 pc's running 1803, so something 6/28/2018 when it started.

Log Name:      Application

Source:        Application Error

Date:          7/22/2018 5:04:58 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      DESKTOP-C7MSO9M

Description:

Faulting application name: devicecensus.exe, version: 10.0.17673.1005, time stamp: 0x79a09a4b

Faulting module name: WaaSAssessment.dll, version: 10.0.17134.1, time stamp: 0xb7ab6594

Exception code: 0xc0000005

Fault offset: 0x0000000000008ee5

Faulting process id: 0x2e34

Faulting application start time: 0x01d422104b581eb4

Faulting application path: C:\WINDOWS\system32\devicecensus.exe

Faulting module path: C:\Windows\System32\WaaSAssessment.dll

Report Id: 75d6d06e-0774-49ed-8713-dd95fe56a512

Faulting package full name: 

Faulting package-relative application ID: 

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2018-07-22T23:04:58.926384000Z" />

    <EventRecordID>3256</EventRecordID>

    <Channel>Application</Channel>

    <Computer>DESKTOP-C7MSO9M</Computer>

    <Security />

  </System>

  <EventData>

    <Data>devicecensus.exe</Data>

    <Data>10.0.17673.1005</Data>

    <Data>79a09a4b</Data>

    <Data>WaaSAssessment.dll</Data>

    <Data>10.0.17134.1</Data>

    <Data>b7ab6594</Data>

    <Data>c0000005</Data>

    <Data>0000000000008ee5</Data>

    <Data>2e34</Data>

    <Data>01d422104b581eb4</Data>

    <Data>C:\WINDOWS\system32\devicecensus.exe</Data>

    <Data>C:\Windows\System32\WaaSAssessment.dll</Data>

    <Data>75d6d06e-0774-49ed-8713-dd95fe56a512</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

Is this what causing device-census related errors?

No. If it were, every Windows 10 computer in the world would have been affected.

I have decided to reset one of my affected devices and see if it'll fix the problem. So far, I've only seen this problem on machines that have been updated from v1709.