Since installing Kaspersky Anti Ransomware User complain of slow smb traffic

  • 28 June 2019
  • 2 replies

We have CAD developers who access projects on a windows server via smb share. When the tool is running it takes on average 10x's+ longer to open a project. Same project without the tool running takes 6 seconds to open. With the tool running it takes a minute and a half. This is for a small project. They have very large projects that normally take 2-3 minutes but with this tool running it is taking 40-50 minutes to open. We would love to be able to have the tool running on the server but at this point we can't. Any suggestions to fix this? BTW we are a MSP that manages 100's of clients and this is just one. Almost all clients that we have installed this tool for are complaining of similar issues.

2 replies

Hello KART Support,

I have the same issue with my File server.
The access yo SMB Shares slowly, The Engineers telling me the DB of Solidworks
Open really SLOW.....

Please tell us how we fix that problems.
Hello @cbell6469 @Sassy36 .

We need some additional info to analyze the problem.
Please collect and send us (e.g. as attachment here) ETW traces:

1.Preparation steps for Windows 7/8/8.1, Server 2008R2/2012(R2):
  • install ADK for Windows 8.1, during install choose Windows Performance Toolkit only
  • or install Windows Performance Toolkit using standalone installers: WPTx86-x86_en-us.msi for 32-bit versions of Windows, WindowsWPTx64-x86_en-us.msi for 64-bit versions of Windows.
  • Windows 10 already has all the necessary components and no additional preparation is required.
2. On Windows 7 x64, Server 2008R2 run as Administrator the following command and then reboot:
  wpr -disablepagingexecutive on

3. Enable tracing. To do that, run as Administrator one of the following commands depending on how stable the problem reproduces:
  • In case of stable reproduction of a problem:
  wpr -start GeneralProfile.Light -filemode -start CPU -filemode -start FileIO.Light -filemode
  • In case of unstable reproduction at arbitrary time:
  wpr -start GeneralProfile.Light -start CPU -start FileIO.Light

4. Reproduce the problem.
5. Disable tracing and save traces to the file:
  wpr -stop trace.etl

6. Wait until traces are saved, and provide the file with traces.

Please try to limit the reproduction time to several minutes in order to avoid huge traces.