Loading profile via CLI finishes immediately BUT keeps working in parent process!

In Windows 10, if you try to run the command OpenRGB -p myProfile.orp in a batch file, it exits immediately and the profile doesn't load. BUT. If you open a console and enter the same command, it will again execute and exit immediately, but after a while messages will start printing in the CONSOLE's process (parent that spawned OpenRGB). If you keep it open for ~12 more seconds, the profile will load and you can exit the console.

D:\PATH\OpenRGB>OpenRGB.exe -p MYPROFILE.orp

D:\PATH\OpenRGB>echo OpenRGB finished? Okay, let me get back to my busiConnection attempt failed
ADL Status -1
Profile loaded successfully

Above you can see what happens - control is returned to the user (in 0 seconds), the user can write to the console, but there is a background OpenRGB process in the background that still writes to this console.

This looks like OpenRGB is spawning a new thread to load the profile but forgot to wait on it, so the main thread finishes ASAP.

Please fix this obvious and hideous bug with the CLI implementation :)