The jogging issues should be fixed with the next release. The communications issues I’ve looked for and have never seen on my own hardware, so it’s impossible for me to say why it’s happening.
If you have speakers and your volume up a little, do you hear the Windows USB ‘ding’ when the connection drops? If so, that means Windows thinks the cable was pulled, and if that’s what it is, there’s nothing in LightBurn that I can do about that - it would point to an issue either with the physical connection being spotty, or the Ortur board dropping the connection temporarily.
I have one other possible theory - I believe LaserGRBL defaults to using ‘constant power’ mode (M3), whereas LightBurn uses ‘variable power’ mode (M4). If the Ortur firmware has a bug when using variable power, but not constant power, that could explain why LaserGRBL doesn’t glitch. You could try using the GRBL-M3 device in LightBurn, as that would use the same commands. If that doesn’t drop the connection it would be a good clue for the Ortur folks.