LINYbob
Just tested it at my end, and i get the same behaivor.
Hower this; "But if I go back into MM now and exit it, the service doesn't start up at all this time!! Crazy!"
If you see that this happens, go to task manager. I noticed that after quiting MM the service indeed does not start.
However MM initilized a new exe to act act as a service. But is not.
In task manager you need to exit the last running mediamonkey.exe and then the service does start again.
Windows eventvwr, gives two errors: Event id 7009 and 7000
Its a timeout that it cannot start, and ofcouse, when the mediamonkey.exe is already running in taskmanager, it cannot start the service.
Will try to catch this behaivor in the debugview. (edit; mediamonkey service does not provide info to debugview, so no additional info from there)
For devs;
Could it be the case it the MM script runs "mediamonkey.exe /Service" to start the service. Instead of using the propper command:
"net start MediaMonkey5Service"
Edit:
See service after reboot, and see the 'service' that is started after exiting MM app.
https://imgur.com/1Z193Hy