The GP has been complaining about Adobe services that start in Services (automatically or on trigger) - as far as I remember, none of those are visual apps, so

The GP has been complaining about Adobe services that start in Services (automatically or on trigger) - as far as I remember, none of those are visual apps, so they indeed behave like daemons. It's like complaining that Gnome Tweak Tool only shows stuff from ${XDG_CONFIG_HOME}/autostart instead of also showing systemd service entries from user or global lists. Use of a persistent background tasks/helpers instead of Task Scheduler (or cron, on Unix-like world) for background updates is a pattern that is unfortunately accepted by now thanks to OS vendors doing exactly the same. "edgeupdate" et co are a great example if we are staying in the Windows world. I don't like how many services/tasks/applications Adobe registers and starts for their CC and DC products, but it should not be a surprise that some are getting registered in other places than HKLM\SOFTWARE\Microsoft\Wndows\CurrentVersion\Run or the Wow6432Node version - it should be considered basic admin knowledge that there are other locations where the process may get started on log in, so it is not reliable to just look in Task Manager or Control Panel "start-up" items.