Hi Cyprien,
We are aware of this issue. The reason this happens is because we utilize the GPU in our application through the OpenGL library. This is not supported in Windows Remote Desktop unfortunately and is a known limitation. There are a few workarounds.
Some customers report that if they can launch Spike before logging in to remote desktop and it will work, but they cannot launch Spike through remote desktop. You can also use a VNC client/server. There is a free version called TightVNC which we have used with success. This lets you control the PC remotely. If you have the NUC with vPro functionality, there is a way to setup the device to be controlled remotely using vPro. This is more involved but is a very robust solution.
Regards,
A.J.
