[1607, au] CDPUserSvc_ has stopped working

[grahamd22]

2017-11 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB4048953)

 

Has become installed across the network with a lovely error message everytime you logon:

 

 

It appears to be a service but fairly unknown as to what it links to apart from mail services, which we don't require as we use 365 either on the internet or use the full version of outlook 2016:

 

 

Does anyone know if there is a patch or how to resolve this. We can only think of disabling/deleting it, what are your thoughts?

[Phylum]

I can confirm the same: I'm currently testing the November Windows 10 patches (1511, 1607 and 1703) and am seeing the same errors only on the 1607 machines.

Removing KB4048953 corrected the issue, no more crashing on startup.

 

I'm investigating this further and will update once I have something appreciable to report.

Edited November 16, 2017 by Phylum

[Phylum]

Microsoft confirmed the CDPUserSVC error is a bug we’re seeing after install of the November 2017 Windows 10 version 1607 Cumulative update. A private hotfix is available, which we will be testing internally to confirm teh issue is addressed, but I don’t want to deploy a private hotfix in the organization to only have to turn around and remove it and install the public hotfix. The only other workaround is to disable the firewall policies and the corresponding service which isn't an option. I have asked Microsoft for an ETA on the release of the public hotfix - will update once I hear more.

[free780]

It's like they want to kill 1607. I've had the C:\windows\ccm\temp filling up on 1607.

[KK20]

Personal theory. It only errors on our 1607 PCs that have certain messaging apps permanently removed, our test machines with no apps permanently removed do not error. We don't use messaging apps or Skype etc. We disabled the service with GPO reg key

HKLM\SYSTEM\CurrentControlSet\services\CDPUserSvc value Start as 4

 

This cured it for us, nothing appears to have stopped working for us (email works, no other apps appear to stop working). simply reversing the Start to 1 gets the service running again.

[grahamd22]

The error seems to have mysteriously dissappeared as quick as it arrived! It maybe a coincidence but Smoothwall have been helping us to get Skype working?

[Phylum]

That's an interesting idea: During OSD we remove plenty of unnecessary UWP apps so potentially every 1607 would have this problem. I don't have a stock machine or a standard build without the UWP apps removed to kick the tires on but that's something to consider. Before I go down that route, I'm going to wait until I hear back from MS since they did confirm it was an issue. Good theory though!

[Phylum]

Microsoft provided a link to the private hotfix, Windows10.0-KB991116--InstallForTestingPurposesOnly.exe, but I can't share it since it requires logging on.If you're in a corporate environment, I would open a case.For non corporate users (home users, small office/home office) check here for support options or simply chat with the Virtual Agent and type something like: "Windows 10 Update broke my computer - can I open a support ticket?"The Virtual Agent will probably try to offer the Windows Update Troubleshooter so click 'no' when asked if it resolved the issue then click the link to speak with a person and choose your preferred option.Microsoft does offer free support for situations like this, but I'm 99.999...% certain they will ask you to upgrade to 1703 or 1709 & see if it persists.

[Phylum]

No movement yet from MS on this but since it is a real issue, it'll be resolved soon enough.

[neb1355]

All of our 1609 machines seem to be affected randomly by this.

 

Looks like I'll need to push updating them to 1709 forward a bit.

[Michael]

Microsoft have stated -

 

After installing KB4041688, KB4052231, or KB4048953, the error "CDPUserSvc_XXXX has stopped working" appears. Additionally, Event ID 1000 is logged in the Application event log. It notes that svchost.exe_CDPUserSvc_XXXX has stopped working and the faulting module name is "cdp.dll".

 

KB4041688 = October Windows Update (2nd version)

KB4052231 = November Windows Update (1st version)

KB4048953 = November Windows Update (2nd version)

 

There is a 3rd version of the November update available KB4051033, but this also is affected, so you'll have to wait until the December fix. Interestingly I'm running KB4048953 and not seeing this error!?