Thanks for the screenshot. It tells us where the failure is, but the part that names the cause is cut off.
What we can see. The trace places the failure in the startup, before the server becomes usable at all. That matches what you are describing: it fails, exits, restarts, and fails in the same place, which reads as continuous cycling.
The UserIds must be non-empty line just below it is not the cause.
What we need. In that same log, immediately above the –[ Stack Trace ]– line, there will be a line naming the exception type and its message. That is the piece that identifies the cause, and it is just off the top of your screenshot. Please send us those few lines.
And one question first, because it may make this moot. Have you reinstalled Roon since posting? The log archive we pulled contains only a clean startup with no crash in it, which suggests something changed. Is it starting normally now?
Guys I reinstalled and I am back. It’s real shame you don’t install to windows properly - Roon Server should be a service running under local system and installed to Program Files so you don’t fall fall of Smart App Control. I could share the the event log for this too but if you sort al this out you wont upset your windows customer base and you’ll be following Microsoft and UK Government best practice. If you want help please let me know I am a retied engineer at Microsoft UK and worked extensively on software deployment and testing for various UK government departments