Thank you for sending those over. After reviewing things more closely, we’re seeing a potential issue linked to build mismatches. A database refresh should help in this case. Steps to follow below:
This is an odd issue indeed, and so I very much appreciate your continued patience while we continue to investigate. Unfortunately, re-reviewing your core diagnostics didn’t provide as useful information as we had hoped.
The next thing we’d like for you to test would be removing the second display/monitor that is attached to your Windows 10 core and try launching the production build.
Beyond that, do you have any particular antivirus or third-party security software running on the core device? If so, I would temporarily disable it and test running production.
okay, it’s actually only attached physically to one monitor, the other monitor is virtual because I use a virtual login remote utility software to actually view the computer. I very rarely turn on the TV it’s connected to, only when necessary.
I have told it to output on only one machine although it still senses both.
my software is bitdefender, not sure that’s really an issue, you’re kind of grasping at straws there I think
by the way, I also have a folder called Roonserver & Roongoer in the location where you told me to look for my Roon database folder, is this significant?