Hi Peter

I had the same painful Problem, either when DF Programs started as a Service or if started via the Windows Scheduler. The only thing that helped was to start one App as Service or via the Scheduler and this exe then starts and controls the additional Apps. By doing it this way you have only one VDFDaemon running, the sub-Processes detects the already running VDFDaemon.

This solution doesn't fix the Problem completely, it can still happen that a VDFDaemon is "lost in space";-) , especially if the main Process or one of the sub-Processes hangs. But i think it is worth giving it a try.