Adobe Creative Cloud causing lock ups

[FragglePete]

A problem has developed on all PCs that we have Creative Cloud installed on (device based licenses).

 

Essentially, the PC freezes for about 30 secs and then the screen goes blank and then seems to sort itself out.

 

Initially was happening when users first logged in, and I narrowed it down to the Creative Cloud App that was starting automatically at logon.  I've disabled that initially (as an admin locally, still trying to sort out a reg hack for this) so now that doesn't start, but when a user tries to start Photoshop they are directed to the licensing login page and then the freeze will happen again.  When the PC comes back it all seems useable. 

 

Any thoughts?  This and other stuff going at the moment is the last thing I need right now.

 

Pete

[DavR]

We use GP to delete the login run entry below, to stop Creative Cloud running at first login:

HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run AdobeCreative Cloud   I'm on version 6.10.0.252.41 and am not having that problem, but we are user licensed not device, for whatever difference that might make.

[FragglePete]

Thanks. that's helped that issue stopping that - which makes the machine useable at least.

 

Problem still persists with the Sign In box appearing when starting any Creative Cloud app.

 

Have removed Impero and also remove Sophos to see if it was any of these, but alas it still persists.

 

Pete

 

[DavR]

You've not got any redirected folders or similar that it might be having trouble with, have you? IIRC it mainly uses appdata in the user profile on startup. I don't think it puts anything in My Docs locations but I could be wrong.

 

Have you checked the web filtering logs? Just in case it's hitting something and failing during startup - licensing or update server perhaps.

[psydii]

 

 

Quote

What is Shared Device Licensing

Shared Device Licensing is device-based licensing for shared computers. Rather than associating licenses with individual users, Shared Device Licensing ties them to the machine. Users see a sign-in prompt when they launch an app. A banner indicates the machine uses shared device licensing and reminds users to sign out when finished and to avoid storing files locally.

Shared Device Licensing isn't designed for use on machines used by dedicated users. For dedicated users, we recommend you deploy named-user licenses.

Shared Device Licensing overview | Enterprise

Looks like this is expected behaviour?   [not the freezing bit!]

Edited September 23 by psydii

[FragglePete]

Again, thanks.

 

Only thing redirected these days is My Docs, My Pictures, etc.  User Profile is on the 😄 drive (C:\users\<username>\etc....)

 

Don't believe it's expected behaviour as it locks the whole PC and makes it unuseable for about 60 seconds - if I do it remotely via RDP it kicks me off the session when the freeze occurs.

 

The Shared Device licensing does require them to sign in, as you supposdly get all the Creative Cloud benefits of storing stuff with them, etc but not interested in that.

 

I've got a post going on their community forums but not yielding much help at the moment. 

 

Don't want to go nuclear and do a re-image with a newer version of the creative cloud package but that's my next step. 

 

Pete

 

[psydii]

That sounds like some UAC interaction (or similar) flashing up the "desktop" (in the Win32/NT Object sense) of another user/account session.  If its an older version of the Adobe CC suite that isn't auto updating, it seem like it might be that  CC is now tripping over changes made in the UAC flow (or similar) in a recent Windows Updates? Might even be a new bug in the latest version given how many patches have gone into the last two patch Tuesday releases...
 

[FragglePete]

It's quite a new install for us, introduced this Summer ready for September.

 

Pete

 

[psydii]

966 patches in the September update, so I wouldn't rule it out. Are you sure though that it wasn't doing that from the start during the summer?

[FragglePete]

No, did various testing of my image and deploying the package in July.  All worked no issues.

 

I'm sure others would have had similar issues though.

 

Pete

 

[GK1999]

1 hour ago, FragglePete said:

No, did various testing of my image and deploying the package in July.  All worked no issues.

 

I'm sure others would have had similar issues though.

 

Pete

 

Don't suppose you're running an AMD CPU (Radeon Graphics) or an AMD GPU in these machines, are you? 

[FragglePete]

Could well be yes?  Is there a known issue?

 

Pete