CCMexec stops right after it has been started

I my environment, I suddenly had a lot of inactive clients. I thought that it was strange, so I dived into the issue.
Looking at a client, I found that the ccmexec service wasn't running.
I started the ccmexec service, but it stopped immediately (later I found that, on other client the service stopped after 5 minutes - they would start a repair, and then fail and stop).
Then I looked into the ccmexec.log and found this:
Service settings instance is missing from WMI.

Error loading service settings. Code 0x87d00218 Phase 0 initialization failed (0x87d00218). Service initialization failed (0x87d00218). Shutting down CCMEXEC
x

I tried a repair, but that didn't solve the problem.
Taking a deeper look into the log told me that the client had a problem with the ccm part of wmi.
I then tried to do a client push with the uninstall option checked - and now... Happy client again.

Looking at all my inactive clients - suddenly 10-15% og my environment - it seemed like this issue happened during the upgrade to 1602.

WSUS server broken after a windows update

Came to office this morning to see this in my ConfigMgr console:

Oh... what a MONDAY morning...











A check in the eventlog shows that some updates were installed during the weekend.
So - what now ? remove updates or.... ask google.
Ahh - I was not alone with this problem.

First, I ended up here: https://blogs.technet.microsoft.com/wsus/2016/04/22/what-you-need-to-know-about-kb3148812-part-two/

Well, I didn't install KB3148812, so this could not be my problem, but an update on the page pointed me to this site: https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/
And from here, I was pointed to the page for KB3159706, which I found was installed on my WSUS server:   https://support.microsoft.com/en-us/kb/3159706
As it stated... you needed a manual process to finish this update.

The command: "wsusutil.exe postinstall /servicing" fixed my problem.
After running the command I could start the wsus service again.