Phylum

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

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.

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!

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.

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.