Hello @oliver.eppler
Thanks for including that log detail, it is useful. The fact that a very short log is written and then stops, and that neither the client nor the server will start, points at Windows blocking the newly installed Roon files rather than at Roon failing internally. An update writes new files, Windows does not yet recognise them, and execution is blocked before Roon gets going.
Please check three places and tell us what you find.
1. Protection history. Open Windows Security, then Virus and threat protection, then Protection history. Look for any blocked or quarantined items naming Roon, RAATServer or RoonServer. If something is listed there, please send a screenshot.
2. Smart App Control. In Windows Security, open App and browser control and look for Smart App Control. Please tell us whether it says On, Evaluation, or Off. Please do not change it yet, and we will explain why below.
3. The Windows code integrity log. Open Event Viewer, then go to Applications and Services Logs, Microsoft, Windows, CodeIntegrity, Operational. Look for recent entries that mention Roon and tell us what they say.
Also, if you run any antivirus or endpoint security product besides Windows Defender, please check its quarantine and logs for Roon entries too.
One important warning before you change anything. If Smart App Control turns out to be On, please do not switch it off on your own. Microsoft made that a one-way change: once Smart App Control is turned off it cannot be turned back on without reinstalling Windows. If it is the cause, there are other ways to handle it, and we would rather walk you through those than have you give up a security feature permanently.
Lastly, could you please paste the contents of that short Roon_log file here, or upload it? It is small, and seeing the last few lines in full will tell us exactly where it is stopping.