Participant

Answered

How to stop Adobe Creative Cloud from launching using regedit or group policy?

Forum|Forum|6 years ago
January 29, 2019
6 replies
65795 views

Hello,

We use Windows 10/ 1803 and have deployed the creative cloud desktop client to some 100 users, we'd like to stop this application from launching on startup as standard, can anyone assist me in doing this?

I've had a long look at related registry keys but I could not find anything.

Thanks,

Adam.

Correct answer Mathias Mahnke

Setting the below registry key worked for us. It basically sets Adobe Creative Cloud to "Disabled" in Task Manager > Startup. I have yet to figure out how to script the checking of that "Launch at Login" box, but this solution works for us.

Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\StartupApproved\Run32

Name: Adobe Creative Cloud

Type: REG_BINARY

Data: 030000009818FB164428D501

[Moderator: for some reason Run32 appeared as Run[SPACE]32, even that it was written correctly in this message. Setting it BOLD resolved the problem. As this is quite important, I decided to edit the message accordingly. Thanks to Lam_Cake for bringing this up]

S

Solomon5CA2

Participant

This app is all you need! https://download.sysinternals.com/files/Autoruns.zip It allows me to remove everything adobe from starting when I start my computer . My lightroomC, Lightroom and Photoshop work fine! Photoshop starts creative cloud but being able to stop all things adobe with the autostart viewer, creative cloud and anything else will not restart when you restart your computer.

R

Ravi Albq

Participant

Thanks! It worked for me

R

rolandp71528119

Participant

I'm running Creative Cloud 4.9.0.515

I couldn't seem to get any registry settings to fix this for me. So I ran "Process Monitor" from the SysInternals Suite (https://docs.microsoft.com/en-us/sysinternals/). This tool helped me track down the file that got modified when I toggled the "Lanuch at login" setting. I noticed that no registry settings were getting modified, but rather a settings file called "com.adobe.acc.default.prefs". So I toggled the setting to not launch at login. I then copied this file to NETLOGON and created a Policy that will copy this file to users's %localappdata% folder.

Source file(s)	\\[DOMAINNAME]\netlogon\Software\Arobat DC 19.0\com.adobe.acc.default.prefs
Destination file	%localappdata%\Adobe\OOBE\com.adobe.acc.default.prefs

The contents of my "com.adobe.acc.defaults.pres" file are:

<prefs><property key="attachWindowToMenuBar">false</property><property key="launchAtLogin">false</property></prefs>

With this group policy in place, I was able to keep Adobe CC from launching at startup. I'm using this in a computer lab environment and the students have no need to update apps or sync files to Adobe CC. If they need to install fonts the teacher will show them how to launch Adobe CC.

Hope this helps someone.

M

MrG

Participant

Hi rolandpenner,

Thanks for this... indeed.... i know a little off topic but intrigued as i cannot see in Process Monitor how you tracked down the file that got modified.... have you got two mins to shre this? Thanks again for the solution that worked! 🙂

R

rolandp71528119

Participant

I'm no expert on using Process Monitor, but this is how I did it.

Launch Process Monitor and stop the capture by clicking the "magnifying lens" icon, there should be a red X over it. Then clear the capture using the "eraser" icon (circled in red below). Then drag the target icon (circled in blue) and drop it on your running Creative Cloud application window.

Now click the "Capture" icon to start the capture. Switch to the Creative Cloud application and toggle the setting. Hit save if required. Switch back to Process Monitor and click the "Capture" icon to stop the capture.

On the Filter menu choose "Filter...". Create a filter with "Operation" "contains" "Write". Click "Add" and click "OK"

Now search through the results to find the file or registry entry that is changed.

I hope this helps.

Mathias MahnkeCorrect answer

Participant

Setting the below registry key worked for us. It basically sets Adobe Creative Cloud to "Disabled" in Task Manager > Startup. I have yet to figure out how to script the checking of that "Launch at Login" box, but this solution works for us.

Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\StartupApproved\Run32

Name: Adobe Creative Cloud

Type: REG_BINARY

Data: 030000009818FB164428D501

[Moderator: for some reason Run32 appeared as Run[SPACE]32, even that it was written correctly in this message. Setting it BOLD resolved the problem. As this is quite important, I decided to edit the message accordingly. Thanks to Lam_Cake for bringing this up]

Lam_Cake

Participant

Thanks so much for this! Worked for me. However, I did have to change it to read "\Run32" rather than "\Run 32".

K

K27099774mrp3

Participant

Hello, Can I ask in as brief reply from you as possible, the actual steps to setting a registry key i got as far as naming the key and then when it came to the 'type' where on right click it shows modify then modify binary data then delete... So to carry through is where i'm at. Also, is it any probby if i just exit Registry with the unfinished key until i can go in and finish with the formula, or that is the registry fix? I want to do this at home computer, at work on network we're sol (there). Also, so interesting reading this whole topic's outcome and kudo to the guy that addressed the issue fully with still yet, not really acceptable Adobe response. Anyway, i'm a little fed up with already slow creeping opening on 'every' single time i power up my PC. I don't yet have the SSD installed, etc...that's more personal comment and not really needed as who wants to read complaints.

But thank you for this what must be workable solution!

Abambo

Community Expert

you do not need to hack the registry...

ABAMBO | Hard- and Software Engineer | Photographer

adamb72960314Author

Participant

That's all well and good for 1 person but I'm afraid you didn't read the question.. this is for ~100 people, in a corporate environment, we need a fix that can be deployed remotely, either registry keys or group policy changes would be effective.

michaelg28770365

Participant

The CC app is an important app and should be launched at login. This said, users should be allowed to opt out at this launch, as the CC app is not needed to run CC programs but only to serve additional features, like CC syncing and font syncing. But as a default, programs should work as intended and wanted by the users. Each organization having CC applications should do what is necessary for an optimal user experience.

(BTW I'm an Adobe customer. Productivity is the key and not the organizations IT policy...which needs to be adapted to what the users need for productivity...)

[abuse removed by moderator]

First, I'm a Sys admin in a K12 School District. Second, that's not true, CC is absolutely required to run any adobe application under their latest licensing model, the user must log into CC before the app can be used to verify licensing. The Adobe suite is installed on all our devices and can be used by any of the users at any time but it is not used everyday as someone would for their job. Being K12 we control the environment and need the option to not launch the CC app on startup via reg edit or group policy. When a user launches one of the Adobe products such as Photoshop it will also launch CC and prompt them to sign in, there is no need to have it launch on startup.