In searching for a way to manage Control software start-up behavior, a quick google search was able to efficiently direct me to the original thread: Openbuilds Control Startup In the spirit of OpenBuilds, I attempted to contribute to the knowledge base to provide additional feedback to the development team as well as provide a more beginner friendly alternative to the proposed work-arounds in the thread. While I understand the intentions of the developer for simplicity, usability, beginner friendliness, reduced support load, etc I am also empathetic to the advanced user who want to "control" the Control software installed on their computer regardless of their "reasons" even if it means burying the option deep in a menu tree. It did not seem the conversation had gone terribly off the rails, and feels off to see such a thread locked to further community interaction. For my part, Im posting to give an additional, humble, constructive feedback to the dev team to reconsider both the feature set and the locking of the thread. Id also like to contribute for the next person searching for such information, that the need to go into TaskManager to achieve the desired result is obtuse. Windows 10 natively exposes the behavior at Settings=>Apps=>Startup This is simpler, safer, and more beginner friendly than having users jumping into TaskManager. Regards -
Except this only works until you open the Control software again and it reverts back to the on position