This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos slow down while printing

Hi,

I have Sophos SBE and our client computers are 64bit WIN7. All of the clients have Sophos Endpoint Security and Control 9.5.

We have a konica Minolta BizHub C250 with latest driver, which also really slow. Yesterday I realized, that while i'am waiting for the printing so much.
While word or outlook is waiting for the printing process, the whole computer freeze, and SavService.exe eat my processor's approx 30-40%.

I disabled on-access scanning and the printing was really fast without waiting.
When i try to modificate anything in the printer properties sophos also slow down!

I would like to make some exclusions, but i have no idea how many dir's to add.

Any comment are welcome.

:9385


This thread was automatically locked due to age.
  • Hello

    I excluded C:\Windows\System32\spool which is the spool folder for printer drivers and for printing.

    Now the printing is fast, but i need to test it on more computers.

    I also think, that this workaround not the best solution, I can't imagine why sophos slowing down the printer drivers.

    :9389
  • Hi Sandy,

    I tested this on many other computers and also I tested other Konica drivers, but the problem not gone away.

    I will open a ticket.

    Thanks,

    :9453
  • HI,

    If you have a test machine I would suggest as a test removing detours (http://www.sophos.com/support/knowledgebase/article/112099.html).

    To do so, open the keys:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs

    and

    HKEY_LOCAL_MACHINE\SOFTWARE\wow6432node\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs

    if running on a 64 bit test machine and remove the entry to load the Sophos detours dll.  Please back up the keys before doing so or copy of the paths to the Sophos DLLs in both places so they can be added back later.

    You would then need to reboot to ensure all processes are no longer hosting detours.

    Once booted back up try prinitng, if it works it puts us in the right area.  I would suggest turning on-access back on.

    If removing detours doesn't help I would suggest:

    1. Download Process Monitor (http://technet.microsoft.com/en-us/sysinternals/bb896645) and start capturing

    2. Emulate the problem.

    3. Stop capturing.

    4. Open the Tools menu in Process Monitor and look at the file summary.  This might show which files are being constantly opened etc.. during the process.  Maybe excluding something in there could be an option.

    Regards,

    Jak

    :9457
  • Hi Jak,

    I tested it on two different computers. The printing processes was faster. It didn't stuck on savservice.exe.

    Is there a chance to get another error because of the removing sophos dll's?

    Do I need to test another task related to this?

    Regards,

    :9475
  • Hi,

    I think if you've now narrowed it down to detoured specifically you might be best calling Support with this information.

    Disabing detiured will disable the functionality of SAV as mentioned in the article I linked, hopefully they will have a plan for you.

    Regards,

    Jak

    :9735
  • I excluded C:\Windows\System32\spool

    Certain malware use this folder to drop files in here, so don't exclude this folder from on-access scanning.

    :9853
  • before infecting the spool directory malware should be read, read scan should prevent this situation

    :9877
  • Hello Davide,

    before infecting the spool directory malware should be read

    not necessarily - as malware often doesn't come as a single executable an as yet unknown component might download directly to any location.

    Christian

    :9887
  • the problem of slowness of the print job is a problem that often occurs, as suggest then to resolve?

    :9889
  • That's right QC.

    0-day malware is the problem. 30 to 40 new malware variants get added to SAV every day. If you exclude the Spool folder you risk the system to be infected. Like I said it's a prefered location for a couple of (well spread) malware variants out there. I've seen it multiple times. It's not rare. Malware authors update their creation constantly which at the same time means (depending on the amount of code changes) it can be 0-day already tommorow and depending on your settings (HIPS enabled?) it will not be detected if you exclude Spool.

    :9893