@r_gigante , some details of what happened here, that looks like a dependency issue on kernel_app_64bit.exe...
When you just start kernel_app_64bit.exe from External\Maxon\Cinema4D\ProjectTool\cinema4d_r20_project_tool_20180906 on the agent, you get an error "missing libmmd.dll"
And Dependency walker shows that indeed the .exe depends on that dll and it cannot be found
It looks like this dll was installed by someone on the agent, but the 1809 update removed it (Win10 updates are known for removing applications they consider "incompatible")
I opened kernel_app_64bit.exe in a dependency walker on my machine and found that I get that libmmd.dll from some common Intel installation, probably of some drivers
Then I wondered how Maxon expected the tool to run when it depends on a .dll that is not commonly included in Windows, and indeed I found that the dll is placed in resource\libs\win64 under the .exe
But for some reason the .exe won't pick the .dll from that directory, and the fact that it happens to run on some systems is that they already have the dll installed by another app
I now copied libmmd.dll from resource\libs\win64 to the directory of the .exe and it ran fine from Windows Explorer, let see if the TC build will work. The TC build succeeded
I think MAXON should check why kernel_app_64bit.exe doesn't pick the dll from resource\libs\win64
Now we have to move .dll to the directory of the .exe in our Svn repository as well (which is not how it is distributed by Maxon), to make fresh installs work too
