Device Census Stopped Working Problem

"...no additional Reliability History entry appears..."

This means the problem is fixed, even if it means it is fixed temporarily. I myself run "DeviceCensus.exe", used Task Manager to ensure DeviceCensus.exe had ended, and waited 10 second before opening Reliability Monitor (or refreshing it with F5) to check for a crash. I did this whole test five times in a row! The five times repetition had no reason; I just couldn't believe my eyes. 😜

"Remove-Item : A positional parameter cannot be found that accepts argument '/s'."

The 'rd "C:\Windows\SoftwareDistribution" /s' command is for Command Prompt only. The equivalent in PowerShell is 'Remove-Item "C:\Windows\SoftwareDistribution" -Recurse -Force', even though rd "C:\Windows\SoftwareDistribution" -r -f also works. In addition, "net stop wuauserv" and "net start wuauserv" are also for Command Prompt, even though they work perfectly well in PowerShell. Their native equivalents are " Stop-Service wuauserv" and "Start-Service wuauserv".

I should have mentioned all this earlier. Sorry.

1. I received/applied KB4343909 on 08/14/2018. This took my system from 17134.191 to 17134.228.
2. Looking at the directory entry for devicecensus, it doesn't appear to have a recent date, reflecting the 17134.228 update.
3. I launched RUN devicecensus.exe. The execution raised a powershell-like panel, except the panel was completely blank. In ~10 seconds, the panel collapsed and disappeared. I did this launch directly from the RUN box, and via Cortana's RUN box access.
4. But, based on the assumed devicecensus failure, no additional Reliability History entry appears, subsequent to the entry generated from the earlier morning's initial activation. IOW. This is why I suggested having to wait until the next day to see the event entry. In this system, there will only be 1 devicecensus "Stopped Working" per day.

Stopped Update Service via net stop wuauserv command. Successfully processed.

Below, is the response received from the rd "C:\Windows\SoftwareDistribution" /s command.

PS C:\WINDOWS\system32> rd "C:\Windows\SoftwareDistribution" /s

Remove-Item : A positional parameter cannot be found that accepts argument '/s'.

At line:1 char:1

• rd "C:\Windows\SoftwareDistribution" /s

    + CategoryInfo          : InvalidArgument: (:) [Remove-Item], ParameterBindingException

    + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.RemoveItemCommand

PS C:\WINDOWS\system32>

Rather than wasting time on the rmdir syntax, I just proceeded to C:\Windows\SoftwareDistribution and deleted the folder and contents.

Started Update Service via net start wuauserv command. Successfully processed. Then I checked that the SoftwareDistribution folder had been rebuilt. Successfully processed.

Restarted system, and looked for signs of additional devicecensus failure. No new devicecensus event found. As explained in #04.

I'll check the 08/15 system initialization to see the devicecensus failure status.

Thanks.

Since my devicecensus failure only occurs once daily, I'll have to defer 'til tomorrow to report my result.

But, I'll report that result here then.

You don't have to wait.

DeviceCensus.exe is scheduled to run daily, but you can manually run it any time you want. To do so

1. Press Win+R combination on your keyboard to open Run dialog box (Or open it from the start menu. Or open Cortana instead of Run. Whichever is good for you.)
2. Type "DeviceCensus.exe" (if you are using Cortana instead of Run, wait for it to be found.)
3. Press Enter

Yes, I should have realized that CMDline option.

I must be brief, I have a morning appointment....

I completed the net stop, rmdir, net start sequence yesterday.

Activated the system this morning, but the devicecensus 08/14 failure remains. After allowing 5-10 minutes for failure to occur.

I will say that I received failure response from rmdir. I think it related to the "/s" append. And, also it seemed to squawk about access credentials. Although I ran as admin.

I simply moved to File Explorer, and rid the system of C:\Windows\SoftwareDistribution, manually.

I diligently verified the folder removal.

Issued the net start. Processed successfully.

Restarted.... Successful.

Performed another of the endless KB2267602 pending updates. Successful.

I'll Identify my rmdir anomaly, and take another stab at the process, after I return.

Thanks.

P.S. I may have mentioned my weekend admin duties. These steps include, among many housekeeping

items, "checkhealth", "scanhealth" , and "restorehealth" calls for system integrity. I would have thought

that one of these invocations would have flagged/corrected what you were doing with the distribution

rebuild.

"

Since my devicecensus failure only occurs once daily, I'll have to defer 'til tomorrow to report my result.

But, I'll report that result here then.

You don't have to wait.

DeviceCensus.exe is scheduled to run daily, but you can manually run it any time you want. To do so

1. Press Win+R combination on your keyboard to open Run dialog box (Or open it from the start menu. Or open Cortana instead of Run. Whichever is good for you.)
2. Type "DeviceCensus.exe" (if you are using Cortana instead of Run, wait for it to be found.)
3. Press Enter

Sure. Go ahead and ask anything you wish.

If you want to know how I deleted the "C:\Windows\SoftwareDistribution" folder, it is as easy as issuing the following commands:

net stop wuauserv

rd "C:\Windows\SoftwareDistribution" /s

net start wuauserv

This is the confirmed solution for me.

The Disk Cleanup solution has never received a direct confirmation. I ask people to carry it out and they stop pestering me altogether instead of giving me a clear confirmation. They say no news is good news.

Thank you, very much for that information. That's what I needed. Others, elsewhere had simply removed

devicecensus, but I was denied that access, and somewhat concerned with that anyway.

Since my devicecensus failure only occurs once daily, I'll have to defer 'til tomorrow to report my result.

But, I'll report that result here then.

Thanks again.