@elroy, no compatibility shims at all, just compile and run

i get the same issue running from shell, .bat, .cmd, wscript.run
when the calling program closes then the called program runs, it is already running as a process, but is not active while the caller is still running

i tried a very simple test program and the problem did not occur, so i would believe there must be something in the code to cause this issue
i now have a workaround, unloading the caller and restarting, i would probably prefer a better solution, but as it is only for my own use and can go for many days between needing to shell the program, i guess it will do

i only found there was an issue when i was posting some answer for a thread in the forum, but it did explain some problems i had noticed when using
until i deploy the workaround, i know just to restart the program from the exe or shortcut, which in itself might have been enough to solve the issue