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

[Morkie]

Terri, that's really not a good suggestion if I may be so bold.

BIOS upgrades can be fraught with problems and could create a much bigger problem for someone hoping to fix these issues.

We (Adobe's paying customers) should not be used as guinea pigs like this. Adobe should be working right now on identifying what is causing the problem and keeping us updated on the progress. Once they find the fix, they should then issue an official bulletin about it and describe why it happened and what needs to be done to fix it.

This is an official Adobe forum isn't it? Why are we not seeing evidence of Adobe taking this seriously? If some users have found a solution to the problem, then Adobe should be working with those users to identify how and why the fix worked,  not suggesting the rest of us give it a try in the hope it might work.

I don't earn my living from Photoshop as I used to a few years ago, but if I did I would be hopping mad by now. Those on here who do must be pulling their hair out at the lack of action.

Can you tell us what Adobe is actually doing about this?

[gishnetwork]

Terri, that's really not a good suggestion if I may be so bold.

I'll be bold - that suggestion terrible because it is specific to only her motherboard and irrelevant to 99.9% of the people here.

We (Adobe's paying customers) should not be used as guinea pigs like this

Yes, this is the problem. We understand there are going to be bugs, but Adobe treating users in this forum like their own software testing interns is ridiculous - because those interns are being CHARGED! Lol.

I bet that type tool exercise is reproducible on most systems running 2017.

Thank you Rob.

The trouble with this forum is folks only tend to post when they have a problem and that can create a very unbalanced impression of the software. Your post shows CC2017 when setup correctly and without interference from other products does work well.

Except he just now reported he also has the type tool issue - which is the same issue I have. Rob likely rarely puts type on his images - he sounds like a retired engineer who now dabbles in photography and not a GA.

[rob_ashcroft]

gishnetwork wrote:

Rob likely rarely puts type on his images - he sounds like a retired engineer who now dabbles in photography and not a GA.

I prefer the term 'amateur photographer'.    And yes, I rarely use type tool. ROBERT ASHCROFT / Floral

[gishnetwork]

I prefer the term 'amateur photographer'

Wow, nothing amateur about those pics!

I just meant it sounds like these tools are not critically part of your livelihood.

[Morkie]

Some nice work there Rob. Not bad for a dabbler

Livelihood shouldn't come into it, though. I don't earn money directly from much of the work I do in Adobe apps any more. but I still rely on it for parts of my business and to help out my partner who is starting a new business.

Maybe I've been relying on Adobe apps too much in recent years and should have investigated others in case something like this were to happen...

[gishnetwork]

Livelihood shouldn't come into it,

It certainly should. B2B compared to B2C has more impact on users. When it is your livelihood, time is money!

This is the problem with the subscription model - adobe is getting paid no matter what. Before, you better believe Adobe would not have put this 2017 out and if they did, it would have already been fixed.

[Terri Stevens]

Nice website Rob. Why do stainless steel kitchen utensils always look great in black and white? and where did you get my dad's rusty Morris Minor from?

[rob_ashcroft]

Terri Stevens wrote:

Nice website Rob. Why do stainless steel kitchen utensils always look great in black and white?

Because they are shot by a poor amateur like me! Seriously, I think it's due to their high contrast nature. BW images always work well when you have good tonal range, high contrast, or both. They also are adaptable to varying compositions, and juxtaposition with other objects. 

Terri Stevens wrote:

... and where did you get my dad's rusty Morris Minor from?

There's a small garage in Pembrokeshire, West Wales, near where I live that for some reason keeps a couple outside their premises. Whenever I go past I stop and take a few shots.

Isn't it nice talking about photography rather than running down Adobe?

[Terri Stevens]

rob_ashcroft wrote:

Terri Stevens wrote:

Nice website Rob. Why do stainless steel kitchen utensils always look great in black and white?

Because they are shot by a poor amateur like me! Seriously, I think it's due to their high contrast nature. BW images always work well when you have good tonal range, high contrast, or both. They also are adaptable to varying compositions, and juxtaposition with other objects.

Terri Stevens wrote:

... and where did you get my dad's rusty Morris Minor from?

There's a small garage in Pembrokeshire, West Wales, near where I live that for some reason keeps a couple outside their premises. Whenever I go past I stop and take a few shots.

Isn't it nice talking about photography rather than running down Adobe?

Running down Adobe seems to have become the theme of this thread now unfortunately. If you defend Adobe you become the enemy. I don't work for Adobe or even have shares in the company so feel impartial. I know plenty of people where I work and on this forum who are happy with the software, the subscription model and like all the new features coming through so quickly. I therefore feel it's only right to state for anyone casually browsing the forum that the situation is nowhere near as bad as is being stated.

Adobe are doing some really innovative things these days. I work in advertising and we just love Character Animator where you can sync speech in real-time to a cartoon character there's a lot of uses for that for us. Also they have Project Felix in development that makes incorporating 2D objects into a 3D environment a breeze and that will be very popular I suspect.   Adobe will solve the sluggish behaviour problem eventually, but it would be so much easier if they could put Visual Studio on someone's machine and run the VS debugger!

[gishnetwork]

I therefore feel it's only right to state for anyone casually browsing the forum that the situation is nowhere near as bad as is being stated.

I don't think anyone is saying the issue is bad. I think they are all saying Adobe's handling of the issue is bad.

Adobe techs asking their customers here to try so many tests to help them out... amazingly unprofessional.

"Service and Support" have an entirely different meaning if it is on something you own, versus something you are renting.

[Morkie]

The issue certainly is very bad. We are paying for software which, for some users, is unusable. Not just a bit slow. Unusable.

[Terri Stevens]

gishnetwork wrote:

Adobe techs asking their customers here to try so many tests to help them out... amazingly unprofessional.

"Service and Support" have an entirely different meaning if it is on something you own, versus something you are renting.

I'm puzzled as to what you expect from a technical support forum? If you come here we will ask you questions to help solve your problem and as we can't manipulate your machine you have to do the actual work yourself. Yes that involves doing tests, but to help you out not them! I think you are losing sight of the fact that it is you that has a configurational problem not the majority of Photoshop users-the issue is far from generic to every Photoshop user. By asking you and others question we move closer to a model of what's going on and that helps everyone.

I think it is unfair to call the service unprofessional-it's the nature of the beast, ask a question and anyone with a solution or suggestion can chime in here. I think you might have to concede that as this is a free resource you can't expect more from us volunteers than you are currently receiving.

[gishnetwork]

I think you are losing sight of the fact that it is you that has a configurational problem not the majority of Photoshop users-the issue is far from generic to every Photoshop user

Take for instance Rob. He was here, not sure why as he claimed to have no issue with 2017, but then when asked to do the text-tool test he also has the problem.

There are ten fold people out there that have simply not ran into the problem yet because they don't or have not used a particular tool in PS yet. You are only claiming that the majority of Photoshop users do not have this because of their absence from actually reporting it. Many may just look at this thread and not chime in. Some - like me, lived with it for a month without reporting it. Many may have not even upgraded yet.

This is to illustrate how you are willing to believe in just your perception of the issue. By the wide variety of machines described here - Mac AND Windows, clean install AND well-working season installs, I can pretty much guarantee that it is more widespread than engineers are reporting.

Also, after the HiDPI issue, Bridge PNG issue, Premiere GTXxxx issue, and many others, many users, myself included, just resign ourselves to downgrading and ignoring issues altogether until Adobe fixes it.

Is that really fair? After all, we are supposedly being forced to rent this software so that we can take advantage of always up to date software and new features. Once again - not in this case.

Yes that involves doing tests, but to help you out not them!

Wow.

[Dave_Cox_2]

I agree. Adobe's handling of this situation is very poor. Adobe's stance seems to be that there is nothing wrong with the software, even though there are many people telling them that there is a problem. Also, if anything, Adobe seems to be annoyed that there are a few of us complaining.

Well, here is a bit of wisdom for you Adobe. When most customer's have a problem, they don't complain, they just go away. It is the customers that tell you that you have a problem that you should listen to you. These are the people that are willing to work with you to fix a problem. And, there is a problem with the 2017 version of the software. For me, on 3 different PCs, the software is totally unusable. I've gone back to 2015 version. Everyone that I've talked to have the same problem, even though they haven't bothered to post it on your site. If fact, they are waiting on me to let them know when there is a fix. Most people have other things to do beside fight this issue.

Please don't tell me that it is an issue with my PC. Version 2015 works just fine, and all of the other software that I run also works just fine. Only CC 2017 is creating a problem. I not buying into the idea that suddenly there is something wrong with my PC, and everyone else's PC that is experiencing a problem with the new release. Please acknowledge that there is a problem, and let us know when it will be fixed.

[Adam Jerugim]

We're very concerned about this issue and have been working non-stop to find a way to reproduce it in-house.  We've found two ways to get our systems into a similar state, but are still unconvinced that what we're seeing here is the same thing as what you're seeing in the field.

I'll expand my offer from before: if you're seriously interested in working directly with the Photoshop team to debug and hopefully resolve this issue you'll contact me directly at:  first name dot last name at adobe dot com

The last time I asked for volunteers I had one person offer to have us visit in WA, however she was just seeing a type tool issue that was mitigated by turning off font previews - what others are reporting here sounds like it affects far more than the type tool.

I'd be willing to remotely log into people machines if you don't want me to physically come to you and your system to work on this, but I'm willing to do that too (especially if you're located anywhere west of the rockies).

Thanks,

Adam

[Dave_Cox_2]

Hi Adam,

I would be happy to help you, but the main computer that I'm using belongs to a corporation. I can't allow you to log into this machine, without first getting permission from my employer. I might be able to let you check my personal laptop, but that would have to be after work on Friday, or over a weekend. I don't know if you are available then. I am usually home by noon on Fridays.

[Terri Stevens]

Thanks for stepping in Adam, this problem is affecting a lot of people now and they are understandably angry-code issues are a bit beyond the kind of thing we on the forum can help with. I notice this thread has been read 12,000 times now which may imply more people are affected than are posting.

You do realise Japan is West of the Rockies?

[gishnetwork]

The last time I asked for volunteers I had one person offer to have us visit in WA, however she was just seeing a type tool issue that was mitigated by turning off font previews - what others are reporting here sounds like it affects far more than the type tool.

The type tool issue is fixed awaiting eventual roll out correct?

[lloyd1981]

Earlier this evening, I had difficulty accessing Creative Cloud after a boot. (Mac Mini 2014 - Running Sierra 10.12.2.Beta 6). A notice "flag" advised there was an update to Photoshop 2017. Could not access through the usual methods so I clicked on the "flag" and Creative Cloud became fully accessible and Photoshop 18.0.1 was installed (updated to...).

Opened from the CC menu and ran at least 80% faster on the first load.

May I assume this is a formal revision due to bug remediation?

[SteadfastRacing]

I am going to email you because this is awful.  Just look at the video I just posted.

YouTube

[sonofmrsnak]

Good post. My feeling is that Adobe is trying hard to build memory-sapping profit-oriented "features" into PS 2017 without causing much of a disturbance, and that many machines cannot handle the rewrites.  2017 is (finally) running okay on my Mac, but not as fast as 2015.5. Not good enough.

What did they change that ruined performance in the first place? They know (and won't be transparent).

Avoid Typekit (easy if you are an established designer and have a good font library) and avoid any of the Adobe cloud-based extensions.

I think these are part of the problem. Important to their corporate goals, but not to you or I.

[Terri Stevens]

You have a very busy desktop there. Try switching off that slide show in the background and go for a flat color instead. There are a few things that stand out here. When running Photoshop you seem to have only 17% of memory in use which promotes the questions how much memory do you have and how much memory have you allocated to Photoshop? What is this antimalware service that's using the best part of 180MB of memory? Have you tried turning off the Main Type manager? At points Chrome is using 40% of the CPU with over 5 instances running-is there a real need to have multiple browsers running at the same time? What is your Windows maximum frequency setting? Have you tried adjusting the processor priority for Photoshop away from normal, otherwise it will share as much processor time as that slide show and the browsers you are running.

[gishnetwork]

This thread is not about workarounds for CC2017.

[Terri Stevens]

gishnetwork wrote:

This thread is not about workarounds for CC2017.

it is fair to tell someone if their system is running sub-optimally. Until the time comes when Photoshop has it's own operating system then Windows and OSX in it's many variants need to be set correctly. You seem to want play and go where the application solves every system problem for you-the computer world is not that simple. Photoshop may be cheap these days but it's still one of the most demanding resource hungry applications on the planet and if you want it to work properly you need to learn how to configure your operating system properly.

[munki-boy]

"it's still one of the most demanding resource hungry applications on the planet"

This is completely untrue unless using its 3D or throwing a lot of hi-res/depth images in all at once. I can think of plenty of examples of much heavier applications.

Any 3D rendering package for a start, any video editing software, video converters, particle systems, games, even Math Studio (if it's still called that) and more that I can't be bothered to type.

Runs fine on any machine I've tried that doesn't have "the 2017 problem" that comes baked into the software.  Then it runs really slowly but still doesn't show high resource usage as many people on the thread have already demonstrated.