https://helpx.adobe.com/creative-cloud/kb/cc-cleaner-tool-in...
Whilst you are there, you might want to look at Process Explorer and never look back at Task manager.
[0] https://docs.microsoft.com/en-us/sysinternals/downloads/auto...
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.
Presumably it's taking up CPU checking every single application I run so in opening Activity Viewer it's visible at the top checking it?
https://community.adobe.com/t5/photoshop/adobe-gc-invoker-ut...
in your launch agents...