This issue is disappointing as I am currently a few days into my 14day trail period and this is preventing me from moving forward with a purchase. Not to mention that it makes it imposable for the other members of the family to login without me there which not a nice user experience at all. Hope it can be addressed ASAP.
Do you know if the “bug” is impacting both the 32bit and 64bit versions?
Hello @Roon_User123, and welcome to the community! We are aware of a few similar reports to yours and we have an active investigation into this issue with our QA team. My apologies for the frustration. In a moment, I’m going to send you a PM with another step to try, please take a look!
I will also add your report to our list for the QA team to review, do you have another device you can try as a core in the meantime to see if you get the same result?
Adding an additional core seems to have addressed the issue. That or un Authorizing core 1, and then connecting to it again. I am now able to connect without it asking for sign-in info after a reboot.
I’ll check again tomorrow morning to make sure it is not a session timeout issue.