MuseScore 2 only runs in debug mode
Bit of an odd one. I'm the ICT technician for a school that is looking to run MuseScore in the classroom, but I'm falling at the first hurdle - MuseScore simply won't run. When you double-click the shortcut or .exe, you see the Windows spinning circle for perhaps a few seconds, then nothing. I've trawled the event logs, but there's nothing at all about MuseScore there (and no corresponding events in the same timestamp as the execution). I've ensured the security is correct, and I've run as administrator, and tried both the 32-it and the 64-bit versions. I've also tried it on three different computers.
However... after much reading of the Handbook, I tried running in debug mode using the -d parameter to try and see if it would tell me what's going on - and the program works, exactly as I'd expect it to.
So, my questions are twofold. First, why won't it run without the debug switch, and second, is there any harm in running it in debug mode in a production environment? What's the actual difference between normal and debug (I don't see any actual debug messages anywhere)? If there's no real difference I'm happy to just modify the shortcut that users use and everyone use it!
OS: Windows 10 Education build 1703 64-bit
RAM: 4-8GB (depending on PC I tested it on).
Sound: Realtek High Def audio (I can find a specific chipset name if necessary).
MuseScore version: 2.3.1 (latest at time of typing).
Any other details, just ask. Primarily though, I just want to know if I'm going to hit any problems using it in Debug mode.