Photoshop CC 2017 Unusable slow

[sarobar_kasaju]

I upgraded my Photoshop to CC 2017 today and since the upgrade it has been very very slow. When I click on File menu the dropdown menu appears like after 3-4 seconds. When I delete layer it take about 10 second. Zoom in and out are terribly slow. I work on Photoshop everyday hope to get the problem resolve as soon as possible.

Is there a way to downgrade to earlier version?

My computer details:

Windows 10 Pro

Processor: Intel i7-5960X

RAM: 32 GB

Graphic: NVIDIA GeForce GTX 780 Ti

SSD

[Terri Stevens]

I think why they have that policy is to stop casual users just subscribing for short periods when they get a commission in the way you might hire a power tool for a weekend of DIY

[baraa]

So no solution until now ??

we can't move forward with our work !

[sjamgraphics]

I have the same issue, it was right after upgrading to cc2017. everything is painfully slow, fonts load like 15 at a time and i constantly have the spinning wheel. I get the wheel even when clicking on File. I have 32gig of ram and have an i7 processor with a fusion drive 3tb...my machine is only a year old. photoshop 2015 was fast and no problems.

I should not have to downgrade, i sure hope adobe fixes this issue super fast, i can't get any work done.

[Terri Stevens]

I don't know if you realize, but you don't actually downgrade rather you install CC2015.5.2 in parallel with CC2017-this is possible as the old version lives in a different folder to CC2017 -you can therefore apply any fix as it becomes available for CC2017 while still remaining productive with CC2015.5.2

[stephens13880243]

I just updated to Photoshop CC 2017 over the weekend and am very sorry to report that it is very, very slow....it is so slow that it is completely unusable. It won't even open the image I clicked on in Lightroom to edit in PS.  I'm working on a fast 27" Retina iMac running Yosemite with 4 GHz quad-core i7,  3TB hybrid drive and 16GB ram. I can't even use the program; all that happens is the beach ball spins...it's frickin' ridiculous! I'm going to uninstall this version and go back to 2015.5. Running the standalone version of PS CS 6 everything is plenty zippy.

Really, really disappointed, Adobe. Get your act together.  This is as bad as Apple releasing that complete POS operating system known as El Crapitan.

[phhortress]

Terri,

I fully understand that the purpose of the cancellation policy.   I made it within the 14 days so I'm ok.  I'll download it again as soon as they resolve their software issue and I resolve my broken PC issue.

[phhortress]

Installed PS CC 2015 and all is well.  Still a CPU and Memory hog but it's smooth and uses minimal storage space as it works.

[Dave_Cox_2]

I agree, I went back to CC 2015 and all is well for now. There is nothing new in the 2017 release that I really need, so this works fine for me.

[Adam Jerugim]

The good news is we think we've found a system we can reproduce the issue on in-house (after trying for the past 3 weeks). We're currently working to debug the issue, but in the meantime we'd like people to try this:

1.  Go to the Adobe Create Cloud application and click the gear on the right-hand side and select Preferences...

2.  From the Preferences dialog, click the Sign Out button, then quit the Adobe Creative Cloud App (using the same gear dialog)

3.  Reboot your system

4.  Sign back into the Adobe Creative Cloud (either in the ACC app itself or by launching PS)

Does this help with overall performance in CC 2017?

[Mateusz 1234]

Unfortunately, in my case*, nothing changed. PS, DW and MU are still sluggish. The only change was the apps started asking me for a review.

* MacBook Pro (13-inch, early 2015), 2,9GHz Intel Core i5, 16GB RAM. macOS Sierra.

[sonofmrsnak]

In my case, I actually had the Cloud app crash a week ago  or so (rendering all my Adobe programs bricked - thanks for this ) and had to download new app. New install didn't affect PS 2017's sluggishness.

Mac

[lloyd1981]

May be why I haven't noticed any slowdown. The Creative Cloud icon stopped showing in the menu bar a few months ago. Somewhere, I saw a suggestion about deleting Creative Cloud and reinstalling it. Didn't seem like a great idea because the warning appeared, informing that all of the apps and cloud items would be deleted as well. I'm not sure what happened next (the mind begins to bog down and cloud over when you are trying to do work and it takes hours just to print a document-an Acrobat document-or to have a large spreadsheet simply load), but I had been using a version created August 30, 2016; I was alerted to an update so I installed and the icon returned with full functionality to the menu bar and the construct date reads November 3, 2016. I dug no deeper - leave well enough alone since Adobe is exceptionally difficult to communicate with (I look back to my early days of you are signed up and your trial expires soon and over and over again - back in days when I built lots of web pages and about a dozen sites, the Adobe main page was my home page when I booted - sure can't find anyone to email to or call now).

The items for cc that appear in the Apps folder under Adobe are merely aliases. By following to Applications > Utilities > Adobe > Adobe Creative Cloud > ACC and running GetInfo on the real thing, the version that failed to load to the menu bar and was probably the cause for the extreme slowing that I blamed on Microsoft. The old version, from a full backup created before the update, running both El Capitan in one partition and Sierra Beta 1 in another, carries a version number 3.8.0.310.

The version that restored all functions and returned to the menu bar (and I have experienced none of the slow down issues others have reported since I did the full cleaning, examination, replacing the MS office 365 and other treatments) carries version number 3.9.1.335

Thanks for keeping in touch.

Lloyd

edited to make a few corrections

[lloyd1981]

I don't really know who to reply to anymore. Stuff wanders around here like a lost dog, but I will try one more time.

Similar complaints about Illustrator showed up earlier this year and the REAL ACKNOWLEDGED ANSWER was to remove the preferences file (just for AI). The last sentence in the right answer:

reset/delete the AI preferences seems OK for now

In looking around, here are two recent thread excerpts from the opening post: (copied what I could)

InDesign CC 2017 - Very Slow

This question is Not Answered.

Lightroom CC 2015.7 slower than death 😠

This question is Not Answered.

coreym25318515 Sep 21, 2016 7:50 PM

FOR THE LOVE OF GOD PLEASE HELP ME.

The titles should be live links. Anyway, Photoshop users are not alone. Those threads are not nearly as long as this one, but it appears that a common function between programs may be a cause so deep that an airbag recall is in order. Whatever fix is applied to one that brings order to the process might well be the overall solution to the same issue with other programs.

Could it be the individual preferences for each program? Seemed to help AI. One caution: Do not use the "automated" preference remover - go to each product folder and work your way down. May be easier on a Mac. There is a general post giving the exact path as part of an advisory but I lost that tab. I think it had to do with InDesign.

Anyway, Adobe can tell you the path. If you wish to try. But no one here seems to consider working on their SYSTEM as part of the problem (as in cleaning out all the junk and rebuilding your links and permissions and running a couple of re-boots).

Ciao!

[mateuszn47782296]

It is not even poor performance. In my case it is some kind of glitch ore something.

[lloyd1981]

Illustrator problems. See post from Wardid. Also, PS is not alone.

Re: Why illustrator cc 2015 went extremely slow after last upgrade?

Once again, if you are on a Mac, I suggest you try the version of OnyX for your OS (MUST be the matching version) and follow the Maintenance and delete options except for valuable browser history and cookies. Rebuild all preferences. Clean caches, the hundreds of logs that are collected, etc.

Check to make sure you are using the November release of Creative Cloud.

[Edward at overend]

Having the same issue: Type tool very slow on windows 7.
PC system info - Photoshop slow text problem (2017 update) - Pastebin.com

Hope you guys find the problem soon.

Kind regards.

Edward

[greenlillium]

I am having this same problem too, after upgrading to Photoshop 2017 in the last week.  It is totally slow and laggy even after disabling all of the animated features, etc.

I have been angry at Adobe ever since they went to the monthly online system and disabled my old disks from working (they wont recognise the serial numbers and therefore won't allow them to open).  This is nothing but a money grab and I was fine with the old version.  Please stop upgrading it with extra useless features.

[lloyd1981]

How old are your discs, i.e. versions, and what is your operating system?

I installed Photoshop and Bridge CS6 in 2012 and they were never replaced so I never had to use the serial numbers after the first install. And they work well on mirror backups. Earlier versions also remained on the hard drive - as I move up through OS iterations, I don't delete software until it will not work.

Example: I also had the PowerPC Mac versions of Photoshop, Illustrator, GoLive and InDesign installed. When I upgraded from 10.6.x to 10.7.x, Power PC programs no longer work. (I currently run Sierra 10.12.2 Beta 4.) Not an Adobe issue. I also use Acrobat Pro and Acrobat X Pro for quick fixes and they have been running since 2010 and 2013. Since I keep live, bootable partitions with older operating systems, I can reboot to 10.6.8 and use Illustrator, etc., without a problem. But because those versions are PowerPC versions, I cannot use them with later Mac OS. (If you are using Windows, have no idea what to suggest.)

Unless you participated in the process, I know of no way Adobe could remotely modify your hard copy. Even under Creative Cloud, Lightroom 5, Photoshop CS6 and Acrobat X are recognized as older versions but not destroyed. If you are trying a re-install and you have a version that will work on your OS and you are the registered owner of the license(s), have you communicated with Adobe?

Good luck.

[Creative Mind]

Wow.  Finally got Photoshop 2017 working fast like prior versions.

I'm on WIndows 10.

I tried several of the suggestions from a number of posts on here.

1. Running it now as an Adminstrator.

2. Unchecked all the "unchecks" suggested.

3. Decreased Photoshop's CPU Limit from 60% to 40%.   

4. Disabled all the sync options.

Voila!  Happy camper again!  Thank you to all who posted the suggestions!

Kevin

[Terri Stevens]

One more thing you could try Kevin is changing the priority of the photoshop.exe process. What this does is give Photoshop more processor time, so rather than sharing equally with all the other apps on the computer, Photoshop is given preference. For this reason this setting is not recommended when many apps are running in the background. With Task Manager the setting is not 'sticky', that is it needs to be set every time Photoshop is started. There are more advanced process managers that do remember these settings though. In Task Manager simply right click on Photoshop.exe, go to Set Priority and try High or Realtime.

[JacekPuzio]

And voila, you're now happy user of castrated software! Buy Porsche, remove engine and put Fiat 500's one inside... lol.

[Terri Stevens]

Not a very constructive comment Jacek-at least https://forums.adobe.com/people/Creative%20Mind persevered and eventually got somewhere, unlike many on this thread who just cry out 'it doesn't work' and don't stop to think it may be their system and not the software. Photoshop is now cheap but it's not any easier to configure than software costing thousand, to get it to work the hardware needs to be setup properly and everything optimised in the software, to mock someone who has done that and had success is not very professional.

[JacekPuzio]

Just pointing out the absurdity of the situation - disabling all avaliable new features, reducing CPU usage is not a success or "configuration", it's a defeat.

It is December and We haven't got any update solving our problems yet... an update which will let users to use all of these coooool features without any problems...

[Terri Stevens]

I interpreted the reduction in the CPU usage from 60-40% as a  mistake actually meaning a reduction in memory usage from 60-40%. I know how to throttle CPU usage with third party apps but not from within Photoshop itself. If he indeed did mean cutting CPU power then that would be a very major thing to do with major performance implications-in which case I'd agree with you about castrating the software. Perhaps he could clarify?

[gishnetwork]

unlike many on this thread who just cry out 'it doesn't work' and don't stop to think it may be their system and not the software

Reverting back one version fixes all issues. Installing latest version vivifies all issues. I'm no expert, but that tells me something is wrong with the latest version of software.

Terri stated "to get it to work the hardware needs to be setup properly and everything optimised in the software" and she is correct.

You mean I can't store my kitchen sponge and loose pennies on top my Quadro M5000? Gee, I feeeel stuupaad.

So, what you are saying is that Adobe is not going to fix it because there is nothing to fix - there is no problem? The problem is in all of our systems?

Yeah, didn't think so.

2. Unchecked all the "unchecks" suggested.

Wow, that's really helpful, guy. Let me read through all 6 pages and uncheck everything suggested to be unchecked?

How about all the apologists stop growing this post. There is only one fix and that is for Adobe to reissue correct software. There is only one workaround and that is to downgrade one version. Nobody needs the newest incremental version by fubarring all the settings and other features.

All these ACP/STAFF comments are are buying time for Adobe - making the community feel like it is being taken care of. 3 weeks to find an internal system with an issue? Utter hogwash.