[Fix] Cdpusersvc Failed to Read Description (Error Code 15100)
Command Used:
(Invoke-WebRequest -uri "[ Ссылка ]").Content
Some Windows users have discovered a service called CDpusersvc whose description contains an error code (Failed to Read Description – Error Code 15100). Since this service is most commonly discovered in Task Manager, naturally some users tried to disable it conventionally (from the Services screen), but found that they couldn’t – The parameter is the incorrect error appears.
The CDPUserSvc service is a sub-component of the Connected Device Platform service and will only be used in scenarios where the user connects a Bluetooth device, a printer, a scanner, or other types of external devices. So if you are not using any devices in these categories, you can disable this service with no repercussions.
As it turns out, there are several different scenarios that might end up facilitating the apparition of the Failed to Read Description – Error Code 15100. Here’s a shortlist with every potential culprit:
Outdated OS – As it turns out, Microsoft is already aware of this issue and has already released a hotfix treating this problem on Windows 7, Windows 8.1, and Windows 10. To take advantage of it, simply install every pending Windows update.
CDpusersvc service is not isolated – Even though the vast majority of native Windows services are isolated, this process isn’t. In case this problem occurs due to the fact that the CDpusersvc process does NOT function as a standalone service, you can fix the issue by running a simple command in an elevated CMD prompt.
Corrupted CDpusersvc service – System file corruption can also be responsible for the apparition of this error code. If this scenario is applicable, you should run DISM and SFC scans to see if your operating system is capable of fixing the issue applicable. Else, consider disabling the service via Registry Editor (if you don’t have any connected devices that make use of it).
Permission issue with Microsoft Store – If you previously disabled it via a Group Policy (or some other way), it’s very likely that this produces a conflict that will ultimately result in the Failed to Read Description pop-up error. In this case, you will need to enable the auto-update function manually in order to stop new errors from appearing.
Conflicting errant service – Another possible culprit is errant service tied to CDpusersvc containing a suffix that puts it above being touched by the changes you enforce on the Registry. In this case, you will need to create a manual script and use Task Scheduler to configure it to run at every system startup in order to clean every new instance.
This tutorial will apply for computers, laptops, desktops,and tablets running the Windows 10, Windows 8/8.1, Windows 7 operating systems.Works for all major computer manufactures (Dell, HP, Acer, Asus, Toshiba, Lenovo, Samsung).
