Q: four processes called on schedule, what & why ?

Hello,
since W10 in-place upgrade. I have four processes called on schedule, as a group.
CompatTelRunner.exe, dstokenclean.exe, disksnapshot.exe and dmclient.exe.
I've googled and VT hash. They're system protected files.

Any clue as to what calls them, and why.

Thanks

I wasn't able to find anything on any except dmclient.exe and that was very technical.

Be aware that there is much about Windows 10 or any modern OS that is not officially documented, or in many cases not at all. That is particularly true for a relatively new OS like Windows 10. You may eventually find something in a blog somewhere but that isn't official documentation. It is likely true at the time it was written but subject to change at any time without prior notice. And it may be wrong.

When something is documented developers will take advantage of the information in their products. That make it very difficult to change these things without breaking compatibility with applications that rely on the prior behavior. Even the most trivial changes can have compatibility implications. For that reason many internal details are undocumented.

Well, as Vulnerable Processes they're chatty and finicky. If not allowed, they will try again after awhile.
I can Whitelist or try Blacklist and watch for smoke.

LMiller7 said:

I wasn't able to find anything on any except dmclient.exe and that was very technical.
Be aware that there is much about Windows 10 or any modern OS that is not officially documented, or in many cases not at all. That is particularly true for a relatively new OS like Windows 10. You may eventually find something in a blog somewhere but that isn't official documentation. It is likely true at the time it was written but subject to change at any time without prior notice. And it may be wrong.
When something is documented developers will take advantage of the information in their products. That make it very difficult to change these things without breaking compatibility with applications that rely on the prior behavior. Even the most trivial changes can have compatibility implications. For that reason many internal details are undocumented.

Seems, I've come back to "there is much about Windows 10 or any modern OS that is not officially documented" several times.
e.g., provtool.exe, http://exescan.net/exes/p/provtool-exe-file, which seems to be called with taskhostw.exe, http://exescan.net/search?s=taskhostw.exe&ss=Search, "many internal details are undocumented". Thanks again. Regards