On this lower level side relating to the INTime Kernel, I am not an expert but... I believe that as this application deals with creating low-level hooks between the THM application and the I/O of the machine components, I understand that it is important that it gets loaded EARLY in the startup process.
It may be that you have something else installed on your control that is loading first and is then interfering with INTime's "I/O hooking/linking" attempts.
Hopefully those more technically inclined in this area at Thermwood will have an answer shortly.
I've had issues with intime before as well.
I modified the startup process to delay THM startup by 30 seconds to give intime a chance to start before THM. Never had issues since.