75again,
for restarting MFPro I use a free Windows scripting tool called: AutoIt . google for keyword AutoIt. I detect possible frozen MFPro by looking in the action logfile directory. If there is no change within 30 minutes I assume MFPro is frozen, then my script kills MFPro and does a restart. This solution has several disadvantages, but is the only solution I found to kill frozen MFPro.
First Problem: You need to write a new script for every new MFPro version because AutoIt simulates mouse clicks and keystrokes. You need some programming skills to write the script.
Second Problem: Script assumes MFPro frozen when no actions are done within 30 minutes. Sometimes there are no matching conditions for triggers, so MFpro is re-started even if was not frozen. This can lead to a problem: script re-starts MFPro just when MFPro sends new bets into the market, can lead to incomplete dutching.
Third Problem: You should use this script only if your trigger file does not need any information stored in user variables and does not use auto greenup. This information is lost during restart.
So I use my AutoIt script only for pre inplay back / lay dutching.