Hi @Mathieu_Dulong,
No other steps required on your end for the log pull; the diagnostics already went through. Please keep us posted if the reinstall of Roon helps resolve the crash fully. We’ll be continuing our investigation with the latest diagnostics and will provide updates here.
For now, I recommend all affected users attempt to reinstall Roon on their Windows devices. Even if it doesn’t resolve the issue fully, it will streamline our investigation of diagnostics by reducing clutter in Roon logs. We hope to have this issue pinned down and sorted out for the last affected users very soon, and it’s a high priority for us to help developers track down the bug in any system still affected.
As a reminder, you can also perform a more thorough “deep” reinstall of Roon by refreshing the database:
- Create a Backup of your current database
- Exit out of Roon
- Navigate to your Roon Database Location
- Find the folder that says “Roon”
- Rename the “Roon” folder to “Roon_old”
- Reinstall the Roon App from our Downloads Page to generate a new Roon folder
- Verify if the issue persists on a fresh database before restoring the backup