Windows 10: CDPUserSvc

Hello


I've clean installed my system windows 10 1803, after connecting Windows to my account ”CDPUserSvc“ starts receiving non-stop data from internet.


Does any body have the Same experience?

I've tested on two different Systems with two different Outlook accounts.


Any help will be appreciated

:)

 

CDpusersvc <Failed to Read Description. Error Code: 15100 >

Hola, este link explica para que sirve el servicio:
https://social.technet.microsoft.com/Forums/en-US/c165a54a-4a69-441c-94a7-b5712b54385d/what-is-the-cdpusersvc-for-?forum=win10itprogeneral

Por otra parte, tu problema con el Mouse y lo demás seguro es un problema de hardware.

Saludos.

 

CDpusersvc <Failed to Read Description. Error Code: 15100 >

With a bit of research, it turns out that CDPUserSvc starts "svchost -k UnistackSvcGroup” – the service which automatically updates for the Microsoft App Store. If you have a Group Policy which disables the Microsoft App Store,
then this causes a permissions error which results in the popup error. The updates can be turned off by opening the
Microsoft App Store > Settings > Turn Off Automatic Updates. But ifthe app store cannot be started (due to group Policy), you need to set the following Registry Settings:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CDPUserSvc Start --> DWORD 0x00000004

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CDPUserSvc_2f23ea7 Start --> DWORD 0x00000004

NOTE: The suffix _2f23ea7 will be a random value so you will have to check for it.

You will also need to stop the CDPUserSvc service (via Services.msc). You have to set BOTH registry settings for this to be effective.

 

CDpusersvc <Failed to Read Description. Error Code: 15100 >

I found only one solution; ....................search and destroy!

I've written a script to find the errant service and remove it.

this script runs at start up as a scheduled task because every time I reboot it comes back with a different suffix.

disabling it from the registry does not work because it resets again on startup.

This will have to do until Microsoft decide to fix this example of bad coding.

At least this way my event log does not fill up with failed DCOM registration errors

The server {21F282D1-A881-49E1-9A3A-26E44E39B86C} did not register with DCOM within the required timeout.

there are no adverse effects doing this the service is messed up anyway.

here is the Batch Script

@ECHO OFF

SC QUERY state= all>servicesdump.txt

FINDSTR /L /C:"SERVICE_NAME: CDPUserSvc_" servicesdump.txt >CDPservice.txt

FOR /F "usebackq tokens=2" %%i IN (CDPservice.txt) DO SET CDPUserSvc=%%i

NET Stop "%CDPUserSvc%"

SC Delete "%CDPUserSvc%"

DEL CDPservice.txt

DEL servicesdump.txt