cancel
Showing results for 
Search instead for 
Did you mean: 

McAfee Command Line Scanner (VSCL) extrem langsam (very slow)

Jump to solution

Hallo

Ich habe ein PowerShell Script, welches den VSCL (scan.exe) aufruft, mit einem File als Parameter, welches geprüft werden soll.

Der ganze Vorgang für ein 5kb File dauert ca. 35 Sekunden, meiner Meinung sehr lang. Mit 5 bis 10 Sekunden könnte ich leben aber 35 Sekunden oder mehr für ein 5KB FIle ist viel zu lange.

scan.exe c:\test\test_file.mov

Gibt es einen Parameter, welchen ich vergessen oder das Ganze massiv beschleunigen kann?

Liegt es daran das ich eine "EVALUATION COPY" zum Testen eine benutze?

Version:

McAfee VirusScan Command Line for Win32 Version: 6.0.6.653

Copyright (C) 2015 McAfee, Inc.

(408) 988-3832 EVALUATION COPY - Januar 17 2017

AV Engine version: 5800.7501 for Win32.

Dat set version: 8424 created Jan 30 2017

Scanning for 670813 viruses, trojans and variants.

Gruss

Ralf

1 Solution

Accepted Solutions
Highlighted
Reliable Contributor rmetzger
Reliable Contributor
Report Inappropriate Content
Message 5 of 10

Re: McAfee Command Line Scanner (VSCL) extrem langsam (very slow)

Jump to solution

Hi Piranhas,

piranhas wrote: (Google Translated)

Hello

I have a PowerShell script that calls the VSCL (scan.exe) with a file as the parameter to be checked.
The whole process for a 5kb file takes about 35 seconds, in my opinion very long. With 5 to 10 seconds I could live but 35 seconds or more for a 5KB file is way too long.

Scan.exe c:\test\test_file.mov

Is there a parameter that I can forget or speed up the whole thing massively?
Is it because I use an "EVALUATION COPY" for testing one?

Version:
McAfee VirusScan CommandLine for Win32 Version: 6.0.6.653
Copyright (C) 2015 McAfee, Inc.
(408) 988-3832 EVALUATION COPY - January 17 2017

AV Engine version: 5800.7501 for Win32.
Dat set version: 8424 created Jan 30 2017
Scanning for 670813 viruses, trojans and variants.

Greeting
Ralf

Well assuming Google translated this correctly, I Believe your problem is related to the Building of the Run Time Signature Files with each run

Improve Performance by creating Runtime.dat (cache) file.

Scan32.exe, Scan64.exe, and Scan.exe use the signature files (avvscan.dat,

avvclean.dat, and avvnames.dat) to scan files. As part of the process, the scan

engine combines these files (in RAM) to scan the file. Scan32 and Scan64, when

signatures are updated, create the combined file Runtime{date}.dat (cache) to

improve performance, storing the combined file on disk. Scan.exe can do the same

with the /DECOMPRESS switch. This improves performance dramatically between each

scan, as it no longer needs to recombine the signature files.

To create faster scanning:

1) cd to the directory containing Scan.exe and associated files.

2) Delete existing avv*.dat and runtime.dat files:

    avvscan.dat avvclean.dat avvnames.dat runtime.dat

3a) Download todays ????xdat.exe to the directory containing Scan.exe

    Extract the contents (using todays version):

     8426xdat.exe /E

    This will extract todays avv*.dat (avvscan.dat avvclean.dat avvnames.dat)

      or

3b)  copy the latest avv*.dat to the directory containing Scan.exe

4) Construct a new Runtime.dat cache file

    Scan /DECOMPRESS

Now, when running Scan.exe, Scan.exe sees Runtime.dat and simply loads this

instead of rebuilding it each time, in RAM.

Batch code snippet:

@echo off

rem  Please use with caution, add error checking, assume responsibility

rem  for the following code segment. I will assume no responsibility for

rem  any actions or losses that may occur based on your use of this code.

rem  Use at your own risk.

rem 1. Modify this directory of your liking.

    cd McAfee\Scanner

rem 2. Use your preferred method of download to this directory, ????xdat.exe

    for %%F in (avvscan avvclean avvnames runtime) do if exist "%%~F.dat" del "%%~F.dat"

    for %%F in (GSDSuper.dll Sdatpack.lst NaiScrip.nsc) do del "%%~F"

rem 3a. Once downloaded, extract the the contents

    8426xdat.exe /E .

rem 3b. Alternatively, copy current avvscan.dat avvclean.dat avvnames.dat

rem     from the latest updated VSE to this directory

rem if exist "%CommonProgramFiles%\McAfee\Engine\avv*.dat"    copy "%CommonProgramFiles%\McAfee\Engine\avv*.dat"

rem if exist "%CommonProgramFiles(x86)%\McAfee\Engine\avv*.dat"    copy "%CommonProgramFiles(x86)%\McAfee\Engine\avv*.dat"

rem 4. Create runtime.dat, delete existing if it exists.

rem del runtime.dat

    Scan /DECOMPRESS

Now, when running your scan:

>Scan.exe c:\test\test_file.mov

the runtime dat file is already constructed, and is used directly, saving the time building it in RAM with each scan.

Instead of using BATch code, you will need to translate to PowerShell code.

I wrote a mind dump on this topic here:

https://community.mcafee.com/message/357670#357670

Hope this helps.

Ron Metzger

Thanks,
Ron Metzger

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
9 Replies
Reliable Contributor catdaddy
Reliable Contributor
Report Inappropriate Content
Message 2 of 10

Re: McAfee Command Line Scanner (VSCL) extrem langsam (very slow)

Jump to solution

​Hi Gruss

                     Would it be more appropiate to move this discussion to (Virus Scan Enterprise) for better assistance, in your opinion?

I have concluded that you would be better served by your thread being in (VSE). if you think otherwise, please inform.

Cliff
McAfee Volunteer
Reliable Contributor catdaddy
Reliable Contributor
Report Inappropriate Content
Message 3 of 10

Re: McAfee Command Line Scanner (VSCL) extrem langsam (very slow)

Jump to solution

Having said that;

​ or ​  Could you kindly assist this user please?

Thank you,

CD

Cliff
McAfee Volunteer
Reliable Contributor catdaddy
Reliable Contributor
Report Inappropriate Content
Message 4 of 10

Re: McAfee Command Line Scanner (VSCL) extrem langsam (very slow)

Jump to solution

Moved from  Support Forums to VirusScan Enterprise >Discussions

For better exposure and assistance.

Cliff
McAfee Volunteer
Highlighted
Reliable Contributor rmetzger
Reliable Contributor
Report Inappropriate Content
Message 5 of 10

Re: McAfee Command Line Scanner (VSCL) extrem langsam (very slow)

Jump to solution

Hi Piranhas,

piranhas wrote: (Google Translated)

Hello

I have a PowerShell script that calls the VSCL (scan.exe) with a file as the parameter to be checked.
The whole process for a 5kb file takes about 35 seconds, in my opinion very long. With 5 to 10 seconds I could live but 35 seconds or more for a 5KB file is way too long.

Scan.exe c:\test\test_file.mov

Is there a parameter that I can forget or speed up the whole thing massively?
Is it because I use an "EVALUATION COPY" for testing one?

Version:
McAfee VirusScan CommandLine for Win32 Version: 6.0.6.653
Copyright (C) 2015 McAfee, Inc.
(408) 988-3832 EVALUATION COPY - January 17 2017

AV Engine version: 5800.7501 for Win32.
Dat set version: 8424 created Jan 30 2017
Scanning for 670813 viruses, trojans and variants.

Greeting
Ralf

Well assuming Google translated this correctly, I Believe your problem is related to the Building of the Run Time Signature Files with each run

Improve Performance by creating Runtime.dat (cache) file.

Scan32.exe, Scan64.exe, and Scan.exe use the signature files (avvscan.dat,

avvclean.dat, and avvnames.dat) to scan files. As part of the process, the scan

engine combines these files (in RAM) to scan the file. Scan32 and Scan64, when

signatures are updated, create the combined file Runtime{date}.dat (cache) to

improve performance, storing the combined file on disk. Scan.exe can do the same

with the /DECOMPRESS switch. This improves performance dramatically between each

scan, as it no longer needs to recombine the signature files.

To create faster scanning:

1) cd to the directory containing Scan.exe and associated files.

2) Delete existing avv*.dat and runtime.dat files:

    avvscan.dat avvclean.dat avvnames.dat runtime.dat

3a) Download todays ????xdat.exe to the directory containing Scan.exe

    Extract the contents (using todays version):

     8426xdat.exe /E

    This will extract todays avv*.dat (avvscan.dat avvclean.dat avvnames.dat)

      or

3b)  copy the latest avv*.dat to the directory containing Scan.exe

4) Construct a new Runtime.dat cache file

    Scan /DECOMPRESS

Now, when running Scan.exe, Scan.exe sees Runtime.dat and simply loads this

instead of rebuilding it each time, in RAM.

Batch code snippet:

@echo off

rem  Please use with caution, add error checking, assume responsibility

rem  for the following code segment. I will assume no responsibility for

rem  any actions or losses that may occur based on your use of this code.

rem  Use at your own risk.

rem 1. Modify this directory of your liking.

    cd McAfee\Scanner

rem 2. Use your preferred method of download to this directory, ????xdat.exe

    for %%F in (avvscan avvclean avvnames runtime) do if exist "%%~F.dat" del "%%~F.dat"

    for %%F in (GSDSuper.dll Sdatpack.lst NaiScrip.nsc) do del "%%~F"

rem 3a. Once downloaded, extract the the contents

    8426xdat.exe /E .

rem 3b. Alternatively, copy current avvscan.dat avvclean.dat avvnames.dat

rem     from the latest updated VSE to this directory

rem if exist "%CommonProgramFiles%\McAfee\Engine\avv*.dat"    copy "%CommonProgramFiles%\McAfee\Engine\avv*.dat"

rem if exist "%CommonProgramFiles(x86)%\McAfee\Engine\avv*.dat"    copy "%CommonProgramFiles(x86)%\McAfee\Engine\avv*.dat"

rem 4. Create runtime.dat, delete existing if it exists.

rem del runtime.dat

    Scan /DECOMPRESS

Now, when running your scan:

>Scan.exe c:\test\test_file.mov

the runtime dat file is already constructed, and is used directly, saving the time building it in RAM with each scan.

Instead of using BATch code, you will need to translate to PowerShell code.

I wrote a mind dump on this topic here:

https://community.mcafee.com/message/357670#357670

Hope this helps.

Ron Metzger

Thanks,
Ron Metzger

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
Reliable Contributor rmetzger
Reliable Contributor
Report Inappropriate Content
Message 6 of 10

Re: McAfee Command Line Scanner (VSCL) extrem langsam (very slow)

Jump to solution

piranhas wrote:

Hallo

Ich habe ein PowerShell Script, welches den VSCL (scan.exe) aufruft, mit einem File als Parameter, welches geprüft werden soll.

Der ganze Vorgang für ein 5kb File dauert ca. 35 Sekunden, meiner Meinung sehr lang. Mit 5 bis 10 Sekunden könnte ich leben aber 35 Sekunden oder mehr für ein 5KB FIle ist viel zu lange.

scan.exe c:\test\test_file.mov

Gibt es einen Parameter, welchen ich vergessen oder das Ganze massiv beschleunigen kann?

Liegt es daran das ich eine "EVALUATION COPY" zum Testen eine benutze?

Version:

McAfee VirusScan Command Line for Win32 Version: 6.0.6.653

Copyright (C) 2015 McAfee, Inc.

(408) 988-3832 EVALUATION COPY - Januar 17 2017

AV Engine version: 5800.7501 for Win32.

Dat set version: 8424 created Jan 30 2017

Scanning for 670813 viruses, trojans and variants.

Gruss

Ralf

Hi Ralf

Nun vorausgesetzt, Google hat diese korrekt übersetzt, ich glaube, Ihr Problem ist mit dem Bau der Laufzeit Signatur Dateien mit jedem Lauf verbunden

Verbessern Sie die Leistung, indem Sie die Datei Runtime.dat (Cache) erstellen.
Scan32.exe, Scan64.exe und Scan.exe verwenden die Signaturdateien (avvscan.dat,
Avvclean.dat und avvnames.dat), um Dateien zu scannen. Als Teil des Prozesses, der Scan
Engine kombiniert diese Dateien (im RAM), um die Datei zu scannen. Scan32 und Scan64, wann
Signaturen aktualisiert werden, erstellen Sie die kombinierte Datei Runtime {date} .dat (Cache) an
Verbesserung der Leistung, Speichern der kombinierten Datei auf der Festplatte. Scan.exe kann das gleiche tun

Scan.exe /DECOMPRESS.

Dies verbessert die Leistung dramatisch zwischen jedem
Scan, da die Signaturdateien nicht mehr rekombiniert werden müssen.

So erstellen Sie schnelleres Scannen:

1) cd in das Verzeichnis, das Scan.exe und die zugehörigen Dateien enthält.

2) Löschen vorhandener avv * .dat- und runtime.dat-Dateien:
   
Avvscan.dat avvclean.dat avvnames.dat runtime.dat

3a) Laden Sie heute die Datei "xdat.exe" in das Verzeichnis mit der Datei "Scan.exe" herunter
   
Extrahieren Sie den Inhalt (in der heutigen Version):

    
8426xdat.exe / E

   
Das extrahiert heute avv * .dat (avvscan.dat avvclean.dat avvnames.dat)
     
oder

3b) kopieren Sie die neueste avv * .dat in das Verzeichnis, das Scan.exe enthält

4) Konstruieren Sie eine neue Runtime.dat-Cache-Datei

   
Scan.exe /DECOMPRESS

Jetzt, wenn Scan.exe ausgeführt wird, sieht Scan.exe Runtime.dat und lädt dieses einfach
Anstatt es jedes Mal im RAM neu zu erstellen.

Batch-Code-Snippet:

@Echo off

Rem Bitte verwenden Sie mit Vorsicht, fügen Sie Fehlerprüfung, Verantwortung übernehmen
Rem für das folgende Code-Segment. Ich übernehme keine Verantwortung für
Rem Maßnahmen oder Verluste, die aufgrund Ihrer Verwendung dieses Codes auftreten können.
Rem Verwendung auf eigene Gefahr.

Rem 1. Ändern Sie dieses Verzeichnis nach Ihren Wünschen.
    c
d McAfee\Scanner

Rem 2. Verwenden Sie Ihre bevorzugte Methode zum Download in dieses Verzeichnis, ???? xdat.exe
    for %%F in (avvscan avvclean avvnames runtime) do if exist "%%~F.dat" del "%%~F.dat"

    for %%F in (GSDSuper.dll Sdatpack.lst NaiScrip.nsc) do del "%%~F"


Rem 3a. Extrahieren Sie nach dem Herunterladen den Inhalt
   
8426xdat.exe / E.

Rem 3b. Alternativ kopieren Sie die aktuelle avvscan.dat avvclean.dat avvnames.dat
Rem aus dem letzten aktualisierten VSE in dieses Verzeichnis

rem if exist "%CommonProgramFiles%\McAfee\Engine\avv*.dat"    copy "%CommonProgramFiles%\McAfee\Engine\avv*.dat"

rem if exist "%CommonProgramFiles(x86)%\McAfee\Engine\avv*.dat"    copy "%CommonProgramFiles(x86)%\McAfee\Engine\avv*.dat"


Rem 4. Erstellen Sie runtime.dat, löschen Sie vorhanden, wenn es vorhanden ist.

Rem del runtime.dat

   
Scan /DECOMPRESS

Nun, wenn Sie Ihren Scan:

> Scan.exe c:\test\ test_file.mov

Die Laufzeit-dat-Datei ist bereits erstellt, und wird direkt verwendet, speichern die Zeit, die es im RAM mit jedem Scan.

Statt BATCH-Code zu verwenden, müssen Sie in PowerShell-Code übersetzen.

Ich schrieb ein Mind Dump zu diesem Thema hier:
Https://community.mcafee.com/message/357670#357670

Hoffe das hilft.

Ron Metzger

Thanks,
Ron Metzger

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
Reliable Contributor rmetzger
Reliable Contributor
Report Inappropriate Content
Message 7 of 10

Re: McAfee Command Line Scanner (VSCL) extrem langsam (very slow)

Jump to solution

Hi Ralf,

Status?

Additional Questions?

Results?

Comments?

Helpful?

Correct Answer?

Please help everyone visiting these forums with a reply.

Status?
Weitere Fragen?
Ergebnisse?
Bemerkungen?
Hilfreich?
Korrekte Antwort?

Bitte helfen Sie jedem Besuch dieser Foren mit einer Antwort.

Vielen Dank,

Thanks,

Ron Metzger

Thanks,
Ron Metzger

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?

Re: McAfee Command Line Scanner (VSCL) extrem langsam (very slow)

Jump to solution

Hallo

Ich war 4 Wochen abwesend, werde mich in kommenden Tagen darum kümmern.

Gruss

Ralf

Reliable Contributor rmetzger
Reliable Contributor
Report Inappropriate Content
Message 9 of 10

Re: McAfee Command Line Scanner (VSCL) extrem langsam (very slow)

Jump to solution

Hi Ralf,

Status?                                   Status?

Additional Questions?            Weitere Fragen?

Results?                                 Ergebnisse?                                                   

Comments?                            Bemerkungen?

Helpful?                                  Hilfreich?

Correct Answer?                   Korrekte Antwort?

Please help everyone visiting these forums with a reply.

Bitte helfen Sie jedem Besuch dieser Foren mit einer Antwort.

Thanks,                                   Vielen Dank,

Ron Metzger

Thanks,
Ron Metzger

Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
Reliable Contributor catdaddy
Reliable Contributor
Report Inappropriate Content
Message 10 of 10

Re: McAfee Command Line Scanner (VSCL) extrem langsam (very slow)

Jump to solution

I marked Ron's reply as 'Helpful'/'Correct Answer' to benefit others whom may experience the same issue.

Cliff
McAfee Volunteer
More McAfee Tools to Help You
  • Subscription Service Notification (SNS)
  • How-to: Endpoint Removal Tool
  • Support: Endpoint Security
  • eSupport: Policy Orchestrator
  • Community Help Hub

      New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

    • Find Forum FAQs
    • Learn How to Earn Badges
    • Ask for Help
    Go to Community Help

    Join the Community

      Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

    • Get helpful solutions from McAfee experts.
    • Stay connected to product conversations that matter to you.
    • Participate in product groups led by McAfee employees.
    Join the Community
    Join the Community