Modkit Link for Vex

I am trying to install Modkit Link for our students in one of our IT suites on Windows, I can run the Modkit link fine as an admin or teacher but it will not open as a student (the program starts then stops as a process), we have restricted access for our students and do not allow direct access to browse c drive etc. I’ve run the Modkit Link in debug mode and this is the output from the text file.

2017-10-13 10:52:43,812 - root - INFO - Starting modkit in C:\Program Files (x86)\Modkit\Modkit Link\python
2017-10-13 10:52:44,496 - tornado.general - DEBUG - sockjs.tornado will use json module
2017-10-13 10:52:44,530 - root - DEBUG - cleanup:: about to get lock…
2017-10-13 10:52:44,532 - root - DEBUG - cleanup:: got lock… about to remove instances
2017-10-13 10:52:49,871 - root - DEBUG - getProcessByDirectory:: match… dirname=C:\Program Files (x86)\Modkit\Modkit Link, exe=Modkit_Link.exe, pid=6276
2017-10-13 10:52:49,878 - root - DEBUG - cleanup:: got processes by dir
2017-10-13 10:52:49,878 - root - DEBUG - found own process:6276 do nothing
2017-10-13 10:52:49,880 - root - DEBUG - cleanup:: got processes by name
2017-10-13 10:52:54,078 - root - DEBUG - found own process:6276 do nothing
2017-10-13 10:52:54,101 - root - DEBUG - cleanup:: about to unlock…
2017-10-13 10:52:54,101 - root - DEBUG - Shutting down Modkit Link

Can anyone point me in the direction of what its trying to access and why its doing this?

Thanks in advance…

Have found that amongst other things, Modkit Link will crash on startup if it can’t create modkit link.lnk in the users start menu\programs\startup folder if it doesn’t already exist.
If your student accounts have, for instance, redirected start menus to a read only location, that’ll cause it to crash.
And it doesn’t mention it in the debug logs.
procmon is ones friend…

Iain.