Some Windows users have experienced this unusual error following the release of the security updates on Windows 10. However, this problem is not specific to Windows 10, appearing also on Windows Server 2016.
The root cause of the problem is hard to pinpoint. Microsoft has released very little official information about it, so users have had to resort to makeshift solutions until Microsoft releases more info. This article will describe two common fixes for Windows 10.
What Is Happening?
As stated above, there isn’t too much official information about what’s causing this problem, but it helps to know a little bit about the relevant process. CDPUserSvc is a process associated with OneDrive and Windows live sync. CDPU stands for Connected Devices Platform User Service and the service creates a secure protocol for devices to shuttle data back and forth.
This is important to know because you may not need anything that this service is governing. As of now, solutions to this problem involve shutting down the process. If you’re not using any of the associated services, you should have no problems with that.
Disabling the Service
The good news is that this service isn’t critical to the proper functioning of Windows. The error produces an error code and prompts which can pretty safely be ignored. Generally the prompt will say something along the lines of “A problem caused the program to stop working correctly.” You will be offered several options, one of which is “Close the program.” If you opt for it, you can get back to work without much fuss.
If the error is persistent or causes issues with your software, you will be forced to take action, and an easy way to do this is to disable the service. Disabling is done through the Registry Editor. Don’t be intimidated by the big words, this is a simple and safe process. Follow the steps outlined below.
- Press the Windows key and the R key together to open the Run command. You can also do this via the Win + X menu or typing “run” into the Windows search bar.
- Type “regedit” into the Run command and press Enter.
- You will see a prompt asking you if you want to allow the Registry Editor to make changes to your device; click Yes.
- Once you’ve launched the editor, navigate to this path:
You can do this by hand, in the left pane of the editor, or you can copy and paste the path into the editor’s path box.
- In the right pane, double-click on the “Start” DWORD. That’s the item labeled Start in the CDPUserSvc directory.
- In the editor, change the “Value Data” field to 4. Don’t change anything else, click OK and close the registry editor.
Once you’re finished, restart your computer for the registry changes to take effect. The value data “4” tells the process to not run at all, which won’t affect computer’s performance. Certain functions will be disabled, but it’s not likely to be anything that you’ll miss. Windows will try to force this back periodically so you may have to repeat the process.
Isolate the Process
Another solution is to isolate the process entirely. This functionally shuts down the process by rendering it unable to access data within other processes. It’s a simple procedure, follow these steps:
- Run the Command Prompt as an Administrator; do this by typing “cmd” into the Windows search box and select “Run as administrator” for the best matching result.
- Once the Command Prompt is launched, type in this command: sc config cdpusersvc type=own and press Enter.
If the command runs successfully, it will output this line: [SC] ChangeServiceConfig SUCCESS. This will isolate CDPUserSvc and you should stop getting error messages. Please note that you must run the Command Prompt as an administrator, otherwise you won’t be able to make this change.
If You Can’t Beat It, Disable It
Both solutions should be considered temporary fixes. This is a known issue to Microsoft and will probably be corrected in a future update. Until then, these homemade “patches” should do the trick.
The easier solution is to isolate the service through the command prompt. Make sure you’re running it as an administrator and just type in the command to isolate the process. Otherwise, you can disable it entirely through the Registry Editor, just remember to restart your computer when you make any changes to the registry.
Have you had any luck figuring out what causes this error? Microsoft is characteristically tight-lipped so share your experience in the comments to help other users.