I have the same problem here with ScripterMaster 5.3 and FileMaker 18.0.3 on Windows 10 Pro. Starting FileMaker throws the error "Unable to launch plug-in child process JVM". FileMaker starts nonetheless but our custom plug-in is deactivated. After closing and restarting FileMaker it starts normally and the plug-in is activated. The next day the error usually reappears, but not always, sometimes the first startup works for two or three days.
I already followed the instructions linked in the 4th post with no permanent success. 360works also suggested to delete the folder %AppData%\Local\360Works\Plug-ins\pid\ before starting up FileMaker, but that doesn't solve the issue either.
Did anyone found a permanent solution for the problem yet?
