Skip to main content
To Customer Support To Customer Support
Hello,

 

I have been using Photoshop and Webroot for years and this is the first time a problem like this happens. It began with the last update for Photoshop CC that I got from Adobe Creative Cloud (version CC 2014.2). After a couple of minutes using the software, everything slows down to the point where sometimes I think its frozen.

 

I have checked memory/cpu usage and they are within the normal range, so I went to Adobe forums and found some people with the same problem and it was related to the AV (in their case, Kaspersky). Just to make sure, I shut down my Webroot protection and started Photoshop again, and everything was working like a charm, fast just like before.

 

The solution to the Kaspersky problem was a simple update to the AV software that fixed the problem. I have already posted a topic on Adobe forums and they directed me to check with Webroot, since turning off the AV fixes the problem and it was an issue similar to Kaspersky. I'm using Windows 7 and everything is updated. Thanks for any help 🙂
Hello bigbang55, welcome to the Webroot Community!

 

If the Photoshop software indeed does run without problem with WSA disabled, and slows down while WSA is enabled, and thus indicating a problem with WSA and Photoshop, please submit a Trouble Ticket so that Webroot Support can take a look.  There may be a solution they can find, or in the event it does require a change in the WSA software to operate correctly the problem can be documented.

 

I hope this helps!
I'm wondering if this is a Windows 7 specific problem? as I'm using this version of Photoshop on a Windows 8.1 machine and I'm not seeing any slowdowns or problems.
@ wrote:

I'm wondering if this is a Windows 7 specific problem? as I'm using this version of Photoshop on a Windows 8.1 machine and I'm not seeing any slowdowns or problems.
It is possible that it is a WIndows 7 specific problem, though it is far more likely to be something specific to that one individual computer.  There are a lot of environmental variables that can be at play, and there is a good chance that is where the problem is.  Hopefully Webroot Support will be able to isolate the problem 🙂

Reply


Terms & Conditions