Frequent Account sign-out, inability for CC to handle sessions correctly.

Searched this issue on this forum and there are no solutions. As a tech, I have seen this for years across various clients and I do not know why it has not been resolved. However, as an issue it is insanity how much time and frustration is caused by this when you need to WORK and before you can read a PDF or work in any app you have to sign in... often and also sign out of the same device you're already technically signed into because Adobe doesn't want to bother to deal with how it handles sessions and identify devices.
- I'm finding after installing updates or rebooting my system I'm promted to sign in much to often. If it were once a month I could deal, but it can be multiple times a week.
- Once signed in I'm again prompted with a device activation limit, even though it's the same device that has already been signed in.
I'm going to keep this short. These are professional products, with high monthly subscription fees, that people depend on to work. It's bad enough the code is so bloated that these apps run as slow as a Win98 machine with 1 core and 8GB of ram from the late 90's not a modern 12 core running at 4+ Ghz with 256GB of ram. Having your flow interupted to "sign in" because adobe wants us constantly paying for the same software each month is insult to injury. Seriously, this is not OK. Please Adobe put some urgency and money into this and figure it out.
I would also ask that some additional leeway be added to this device activation limit.
- Limit to actual product run time not device activation. Allow for multiple devices to be registered, but limit apps to being open on two devices at the same time. I get you're trying to prevent multiple end users from taking advantage, but most of us have more than two deevices! You're already sending plenty of telemetry back, a little more isn't going to hurt.
- Increase the device activation count to 3 at least. Even MS has a 5 device limit.
- Share what checks determine a device so end-users can make decisions about changes to their system which might trigger a login or device check.
